- 13 May, 2019 40 commits
-
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/9e4f690166c1..a19080a956b5 git log 9e4f690166c1..a19080a956b5 --date=short --no-merges --format='%ad %ae %s' 2019-05-13 bclayton@google.com third_party/llvm-7.0/BUILD.gn: Update to CMakeLists.txt's changes 2019-05-13 swiftshader.regress@gmail.com Regres: Update test lists @ 9e4f6901 Created with: gclient setdep -r src/third_party/swiftshader@a19080a956b5 The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG=chromium:961729 TBR=swiftshader-team+autoroll@google.com Change-Id: Iff3d498997e6a9eb665a3c17af52fdd00517020a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1609052Reviewed-by:
chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#659013}
-
Arthur Hemery authored
AbortClientNavigation() seems to always be coupled with a "stop all document loaders". Stopping all document loaders has the effect to cancel the client side navigation for PerMojoNavigationInterface feature on. Therefore it seemed to work to simply make AbortClientNavigation a no-op for the NavigationClient path. A certain race condition could cause the RenderFrameImpl to run AbortClientNavigation() while the NavigationClient interface is not yet held by the DocumentLoader. In this case, the no-op is not sufficient and we need to do a manual reset. This is done in this patch. Bug: 784904 Change-Id: I0a07127f72f9cc222392c64478c743153b63f964 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1608743Reviewed-by:
Camille Lamy <clamy@chromium.org> Commit-Queue: Arthur Hemery <ahemery@chromium.org> Cr-Commit-Position: refs/heads/master@{#659012}
-
Yutaka Hirano authored
The flags have been stable since Sep 2018[1][2]. 1: https://crrev.com/bd8853574964974b80f539f21e887b9932b5ebab 2: https://crrev.com/4b736aaff87186c442a20dc5e6823d0fe087e101 Bug: 794548, 924024 Change-Id: Ifb45d0114a398c410fe6f717247fea25c3c0fbad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1609026Reviewed-by:
Mike West <mkwst@chromium.org> Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#659011}
-
Dominic Battre authored
TBR=nhiroki@chromium.org Bug: 867532 Change-Id: I16e31c68c9a7d59454a4b1cc905f8e607f89d2ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1609818Reviewed-by:
Dominic Battré <battre@chromium.org> Commit-Queue: Dominic Battré <battre@chromium.org> Cr-Commit-Position: refs/heads/master@{#659010}
-
Askar Aitzhan authored
When testing with policy, we've noticed that it also receives user policy with the same name. Which doesn't really makes sense in the context of this policy. Because it updates ChromeOS which is common for all users. Bug: 932465 Change-Id: I50d54ad061ab834303b10d1fa54d11e31ad0743c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1605685Reviewed-by:
Pavol Marko <pmarko@chromium.org> Commit-Queue: Askar Aitzhan <askaraitzhan@google.com> Cr-Commit-Position: refs/heads/master@{#659009}
-
Monica Basta authored
Added a catch to any exceptions produced by benchmarking as it is not critical for the orderfile genaration but for assesing its impact on memory and performance. Also, switched to use histograms to extract Speedometer2.0 results as results-charts.json currently does not contain any results. Bug: 947012 Change-Id: I88d8367b2d70a0e716427088a4a784ee1841eb74 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1609837Reviewed-by:
Matthew Cary <mattcary@chromium.org> Commit-Queue: Monica Basta <msalama@google.com> Cr-Commit-Position: refs/heads/master@{#659008}
-
Rayan Kanso authored
Bug: 962428 Change-Id: Ib79b9509f96677bf5fab03e1d7110139484da785 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1609697 Commit-Queue: Rayan Kanso <rayankans@chromium.org> Commit-Queue: Peter Beverloo <peter@chromium.org> Auto-Submit: Rayan Kanso <rayankans@chromium.org> Reviewed-by:
Peter Beverloo <peter@chromium.org> Reviewed-by:
Richard Knoll <knollr@chromium.org> Cr-Commit-Position: refs/heads/master@{#659007}
-
Maksim Sisov authored
Right now, the surface waits until the frame callback is fired, which results in undesired wait when the display compositor can submit new frame (the AsyncSwapBuffers takes about ~10ms). Instead, notify the client on successfull submission right after the buffer is attached, but as soon as a new frame comes, do not submit it, but rather wait the frame callback. The advantage of this approach is that the browser process does not block the display compositor's scheduler and allows it to operate as fast as possible (the AsyncSwapBuffers takes about ~0.6-1ms). Bug: 943096 Change-Id: I808896350a8cd33b87e956b0cec51d8fa0ff1cdb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1570028 Commit-Queue: Maksim Sisov <msisov@igalia.com> Reviewed-by:
Michael Spang <spang@chromium.org> Cr-Commit-Position: refs/heads/master@{#659006}
-
Rayan Kanso authored
Bug: 952870 Change-Id: Id0c7ce8e30e2750eac4408a7ceaa18bd3192b597 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1605991 Commit-Queue: Rayan Kanso <rayankans@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Cr-Commit-Position: refs/heads/master@{#659005}
-
arthursonzogni authored
When a frame is unloading in one process, it must not be visible from the other processes at some point. Previously, it was done when the frame completed the unload, now it will be done when it starts unloading. To achieve that, the RenderFrameProxyHost are removed when the frame starts unloading. Moreover, no new RenderFrameProxyHosts are created in a frame with an unloading current document. + 2 tests added, originally made by lukasza@chromium.org (Thanks!) Bug: 960006, 950625 Change-Id: I3f6fc405219a08d9d61f5c0ed8772601f9dc8835 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1599182 Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Reviewed-by:
Łukasz Anforowicz <lukasza@chromium.org> Cr-Commit-Position: refs/heads/master@{#659004}
-
Denis Kuznetsov authored
TBR=bartfab@chromium.org TBR=poromov@chromium.org TBR=atwilson@chromium.org Change-Id: I7517942f5315b8a1d06113d70083c9c587bd1a33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1604280 Commit-Queue: Denis Kuznetsov <antrim@chromium.org> Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Cr-Commit-Position: refs/heads/master@{#659003}
-
Michael Lippautz authored
These GCs are already expensive or are executed in idleness or when entering background. Use the opportunity to perform compaction. Bug: 958615, 961231 Change-Id: I19c571e9b1b773fe11516c02b0918019fbffb852 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1588561 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Hannes Payer <hpayer@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#659002}
-
Tanmoy Mollik authored
The goal is to introduce a proper type for CoreAccountInfo's account_id to prevent incorrect uses. Before this CL it was a std::string and sometimes was used as an email or a gaia id which was incorrect but sometimes working. The CL makes the struct CoreAccountId implicitly convertible to/from std::string as using a proper type would make the size of the CL intractible. Multiple followup CLs will fix the code and eventually the conversion will be explicit. Bug: 959158 Change-Id: Ia8295b71fa212118115db5f53b5fe845c7992a83 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1596749Reviewed-by:
Dominick Ng <dominickn@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Mihai Sardarescu <msarda@chromium.org> Commit-Queue: Tanmoy Mollik <triploblastic@google.com> Cr-Commit-Position: refs/heads/master@{#659001}
-
Javier Ernesto Flores Robles authored
Adds a swipe gesture recognizer that dismiss the keyboard when the alert is swipped down. Bug: 960417 Change-Id: I1179a158f9860754278ce73f1ee068ccbbaf2d8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1602642 Commit-Queue: Javier Ernesto Flores Robles <javierrobles@chromium.org> Reviewed-by:
Kurt Horimoto <kkhorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#659000}
-
Robert Ma authored
disabled-service-worker-servicification doesn't exist any more. Change-Id: Ia0527eab67a5a5de911f3f963eb286fc92f0e3ce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1604501 Commit-Queue: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Auto-Submit: Robert Ma <robertma@chromium.org> Cr-Commit-Position: refs/heads/master@{#658999}
-
Javier Ernesto Flores Robles authored
Adds a tap gesture recognizer to the alert's chrome so when tapped the text fields resign first responder, causing the keyboard to dismiss. Bug: 960418 Change-Id: Ib855a66ffaedf6ee14ccac25422bf9b804b5a9c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1602640 Commit-Queue: Javier Ernesto Flores Robles <javierrobles@chromium.org> Reviewed-by:
-
Victor Costan authored
Change-Id: Ie79eca491c80d656c4aa7313336e480d7541b0ec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1608317 Commit-Queue: Victor Costan <pwnall@chromium.org> Reviewed-by:
Staphany Park <staphany@chromium.org> Cr-Commit-Position: refs/heads/master@{#658997}
-
Alex Ilin authored
NOPRESUBMIT=true TBR: bsheedy@chromium.org Bug: 962397 Change-Id: I58422dc0f1356c82220b0b58d3f9f2655c3474ec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1608705 Commit-Queue: Alex Ilin <alexilin@chromium.org> Reviewed-by:
Alex Ilin <alexilin@chromium.org> Cr-Commit-Position: refs/heads/master@{#658996}
-
Alex Ilin authored
arm64 has execute-only memory (XOM) protecting code pages from being read. PosixModule reads executable pages in order to extract module info. This may result in a crash if the module is mapped as XOM. This CL effectively disables ModuleCache on POSIX arm64 platforms. Alternative solution would be to obtain map permissions before accessing module's executable memory by parsing /proc/self/maps. Then, return nullptr iff the mapping has execute-only protection. Bug: 957801 Change-Id: I37b2dfa012a0f723a75579d0aabe4c096762f948 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1599391 Commit-Queue: Alex Ilin <alexilin@chromium.org> Reviewed-by:
Mike Wittman <wittman@chromium.org> Cr-Commit-Position: refs/heads/master@{#658995}
-
Hwanseung Lee authored
there are some functions which node object was passed as a parameter at child_list_mutation_scope.h. and the object is never nullptr. so it can be changed to reference instead of pointer. Bug: 874385 Change-Id: I66f3840c688b50fe622712727e1c3fb0c90bae92 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1604394Reviewed-by:
Hayato Ito <hayato@chromium.org> Commit-Queue: Hwanseung Lee <hs1217.lee@samsung.com> Cr-Commit-Position: refs/heads/master@{#658994}
-
Jérôme Lebel authored
Adding "Manage Your Google Account" in Google services settings. https://drive.google.com/open?id=1rTrTW4W94J_gWjQa5fsTeJqMk0jzVQbY Bug: 961257 Change-Id: I8a6b13f40e4b3b09e3ebcef546dc5d0f9b75e38f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1602510Reviewed-by:
Sergio Collazos <sczs@chromium.org> Reviewed-by:
David Roger <droger@chromium.org> Commit-Queue: Jérôme Lebel <jlebel@chromium.org> Cr-Commit-Position: refs/heads/master@{#658993}
-
Javier Ernesto Flores Robles authored
Uses the center constrains of the view's safe area instead of the view ones. R=kkhorimoto@chromium.org Bug: 951300 Change-Id: If97c99f1d14dc4545833b9316364834f3862bb18 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1594712Reviewed-by:
-
Yi Su authored
This CL removes CRWWebController.referrerFromNavigationAction which is not a very helpful method. The HTTP header constant "Referer" is moved into wk_navigation_util.h/mm for possible reuse. Bug: 956511 Change-Id: I8036c773c2dabde04282e93b34d97e89940ca191 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1599588 Commit-Queue: Yi Su <mrsuyi@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#658991}
-
Dominic Battre authored
TBR=nhiroki@chromium.org Bug: 867532 Change-Id: If70324e4f9d5f7479299efd1cd24cd7c5bbee5fa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1608702Reviewed-by:
-
Hiroki Nakagawa authored
This CL makes WorkerFetchContext::Detach() clear WorkerFetchContext::resource_timing_notifier_ to cut off the cross-thread persistent as soon as possible during worker thread termination. Before this CL, I guess the notifier can outlive worker thread's termination GC in WorkerBackingThread::ShutdownOnBackingThread(), and that causes the failure on the parent thread as the issues say. I tested this using the script in issue 960626, and confirmed the failure doesn't happen with this CL. I also tried the script in issue 959508 but couldn't reproduce it regardless of this CL. It will be tested by the fuzzer instead. Bug: 959508, 960626 Change-Id: I2663e5acddec0d9f88a78842c093c594fb57acb8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1609024 Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by:
Kenichi Ishibashi <bashi@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#658989}
-
Michael Lippautz authored
Garbage collections on page navigations are also initiated by V8 (see v8::Heap::NotifyContextDisposed for non-dependent contexts) using its memory reducer mechanism. Since they cover Blink with with unified heap we do not need to schedule anything else there. Bug: 948807 Change-Id: I17a7d9235fd80b8cfc91fd55cab904873166056f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1605408Reviewed-by:
-
Yi Su authored
CRWWebController.safeBrowsingWarningDetectionTimer is used for updating navigation status when SafeBrowsingWarning is displayed. This CL moves it into CRWWKNavigationHandler to support next step refactor. Bug: 956511 Change-Id: I662605492d461f4f8a5f3ed171705539f9a8eaa9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1598803Reviewed-by:
-
Yoshifumi Inoue authored
This patch changes |NGAbstractInlineTextBox::GetText()| to include a collapsed space when it is collapsed by soft line wrap. This patch fixes unit test failure of DumpAccessibilityTreeTest.AccessibilityInputTypes. Change-Id: Ic17caddde97295adf3dd8c56826dd37c8c194371 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1609003 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#658986}
-
Oleg Davydov authored
Also added myself to owners, so next time histogram-eraser bot will notify me too. Bug: 960060 Change-Id: I67523ed33db6cc803dc95da8b11579681429572a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1605414Reviewed-by:
Sergey Poromov <poromov@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Commit-Queue: Oleg Davydov <burunduk@chromium.org> Cr-Commit-Position: refs/heads/master@{#658985}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/c61db7ff2004..9b48fcfc9759 Created with: gclient setdep -r src-internal@9b48fcfc9759 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=anthonyvd@google.com,alph@google.com,battre@google.com Change-Id: I7e787a2250de8b8b38f2025e7f27e65ca1081d1d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1608838Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#658984}
-
Mitsuru Oshima authored
It's regressed in crrev.com/c/1414170. It's just plain wrong but I don't remeber why I changed this way. Bug: 960121 Test: Covered by unittest Change-Id: I0448648c3d661b9a2a9a3b98104d949c2c5a5573 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1595562Reviewed-by:
Eliot Courtney <edcourtney@chromium.org> Commit-Queue: Mitsuru Oshima (slow - gardening) <oshima@chromium.org> Cr-Commit-Position: refs/heads/master@{#658983}
-
Alex Clarke authored
This is the internal promise representation. It implements the machinery needed to marshal and dispatch promises as they become ready for execution. Care has been taken to try and minimize the size of the AbstractPromise class and to keep down the number of heap allocations. The promise result and the executor are both stored in the base::unique_any since they are never needed at the same time. The size of AbstractPromise on x64 is 96 bytes in builds without DCHECKS. In builds with DCHECKS it's larger because there's additional storage used to diagnose and prevent various usage hazards: * Unhandled rejection * Double move of promise results to callbacks * Mixed move and non-move semantics of promise results to callbacks The base::any_internal type has been adjusted so it can store the SmallUniqueObject<> inline, which is used to store the promise executor. The largest anticipated promise executor base::All is the size of 3x sizeof(void*) to hold a vtable and a std::vector. Design: https://docs.google.com/document/d/1l12PAJgEtlrqTXKiw6mk2cR2jP7FAfCCDr-DGIdiC9w/edit TBR=fdoray@chromium.org, etiennep@chromium.org Bug: 906125 Change-Id: I62cecf23ecc8ea3ef7417d6ad40c0911fac5339c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1607643Reviewed-by:
Alex Clarke <alexclarke@chromium.org> Commit-Queue: Alex Clarke <alexclarke@chromium.org> Cr-Commit-Position: refs/heads/master@{#658982}
-
Jan Krcal authored
This CL adds metrics to help investigate an increased number of address conversions in the USS implementation. Bug: 953693 Change-Id: I4085ce5ca11a8354d686ca7ae37f6e1d2dd7cfc1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1598812 Auto-Submit: Jan Krcal <jkrcal@chromium.org> Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Reviewed-by:
Nik Bhagat <nikunjb@chromium.org> Commit-Queue: Jan Krcal <jkrcal@chromium.org> Cr-Commit-Position: refs/heads/master@{#658981}
-
Mikel Astiz authored
There's no need to keep this code under sync/base after the last refactorings, so we can shrink base libraries, which many build targets depend on. Bug: 922971 Change-Id: Ib033a694c9bdd732a3e4346fb63121f540235e60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1564129Reviewed-by:
Marc Treib <treib@chromium.org> Reviewed-by:
Jeffrey Cohen <jeffreycohen@chromium.org> Reviewed-by:
Satoru Takabayashi <satorux@chromium.org> Commit-Queue: Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#658980}
-
Meredith Lane authored
Due to changes in the API, AccessibleNode will no longer be able to modify the underlying accessibility tree. For more information on the motivations for this, see: https://github.com/WICG/aom/blob/gh-pages/explainer.md#what-happened-to-accessiblenode BUG=746523 https://github.com/WICG/aom/blob/gh-pages/explainer.md Change-Id: Ia8fd5c6994e97e317a7360739a8a9d0d6d246fa6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1573299Reviewed-by:
Alice Boxhall <aboxhall@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Commit-Queue: Meredith Lane <meredithl@chromium.org> Cr-Commit-Position: refs/heads/master@{#658979}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/cd862e37ea29..42db0b42abad git log cd862e37ea29..42db0b42abad --date=short --no-merges --format='%ad %ae %s' 2019-05-13 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). Created with: gclient setdep -r src/third_party/depot_tools@42db0b42abad The AutoRoll server is located here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=agable@chromium.org Change-Id: Id67d8e9fab628829351addd7cc4d3b8c9a636492 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1608695Reviewed-by:
-
Meredith Lane authored
Due to changes in the API, AccessibleNode will no longer be able to modify the underlying accessibility tree. For more information on the motivations for this, see: https://github.com/WICG/aom/blob/gh-pages/explainer.md#what-happened-to-accessiblenode BUG=746523 Change-Id: Ib4da0a078abc72fb348038dd1d78bb333fb25d91 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1591493Reviewed-by:
-
Koji Ishii authored
This patch fixes use-after-free when memory reallocation occurs by adding BoxData for bidi inline fragmentations. Bug: 925247, 961943 Change-Id: I5c2cd26546b45772fbff7d001d9e98e49ab19461 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1607719 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#658976}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/c3ab74371c2a..c61db7ff2004 Created with: gclient setdep -r src-internal@c61db7ff2004 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=anthonyvd@google.com,alph@google.com,aboxhall@google.com,battre@google.com Change-Id: I6c166f97027b8342c976adf204151575c1b255f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1608693Reviewed-by:
-
Satoshi Niwa authored
This means using CrOS file selector as default Android file picker go/arc-file-selector Bug: 64281746 Test: atest android.appsecurity.cts.DocumentsTest Change-Id: Ie6f9e5319830b80da1d7a74e164945ef90ece9d3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1608864Reviewed-by:
Yusuke Sato <yusukes@chromium.org> Commit-Queue: Satoshi Niwa <niwa@chromium.org> Auto-Submit: Satoshi Niwa <niwa@chromium.org> Cr-Commit-Position: refs/heads/master@{#658974}
-
