- 11 Aug, 2020 40 commits
-
-
Kevin Ellis authored
Per spec (https://drafts.csswg.org/css-transitions-2/#event-dispatch) a transitioncancel should be fired on the following phase change not idle and not after --> idle Previously we were only test for not idle --> idle, meaning that a finished transition could erroneously trip a transitioncancel. Bug: 979556 Change-Id: Iecd6c8d2a7ca4564925910f092fca4c78b6d79da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2348416 Commit-Queue: Kevin Ellis <kevers@chromium.org> Reviewed-by:
Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#796973}
-
Choongwoo Han authored
This fixes build failure of `autoninja all` Bug: 1076336 Change-Id: I7c073acb2fb98a4b608768e8a862246721acbb98 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346649Reviewed-by:
Ken Rockot <rockot@google.com> Commit-Queue: Choongwoo Han <choongwoo.han@microsoft.com> Cr-Commit-Position: refs/heads/master@{#796972}
-
Ben Mason authored
TBR=govind@chromium.org Change-Id: Idc48b0654294a1bd044bbfe204b9d70e5aea6f4c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2349470Reviewed-by:
Ben Mason <benmason@chromium.org> Reviewed-by:
Krishna Govind <govind@chromium.org> Commit-Queue: Ben Mason <benmason@chromium.org> Cr-Commit-Position: refs/heads/master@{#796971}
-
David Bokan authored
This CL begins the process of splitting input handling out of LayerTreeHostImpl. To keep things simple and easy to review, this CL is a mostly mechanical disentangling of input code into a new class, ThreadedInputHandler. The class still lives in layer_tree_host_impl.cc and is still tightly coupled with it. Future CLs will move this into a separate file and put up proper interfaces between compositing and input. For now there is no behavioral changes, the two classes delegate calls to each other as appropriate. The ThreadedInputHandler has methods shadowing the InputHandler interface, and LayerTreeHostImpl now delegates to it, but ThreadedInputHandler doesn't yet implement the interface. A future CL will make it implement InputHandler and pass it around instead of LTHI. The end state is to have ThreadedInputHandler be a standalone object used by InputHandlerProxy to affect input-related changes. This split deliberately leaves anything graphics or animation related in LTHI. Bug: 915926 Change-Id: Iabc08c03fb618b1f7e9406b5ab7fa7ab64d60913 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2347371Reviewed-by:
-
Becca Hughes authored
Adds empty Chrome Kaleidoscope NTP module as a placeholder. BUG=1114862 Change-Id: Iee00259b9848394ead7d6b80cb1d311f07a5abcd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2347909 Commit-Queue: Becca Hughes <beccahughes@chromium.org> Reviewed-by:
Tibor Goldschwendt <tiborg@chromium.org> Cr-Commit-Position: refs/heads/master@{#796969}
-
Jesse McKenna authored
This change makes the "Open" option in the downloads bar act like "Show in Folder" for files without file extensions on Windows. This fixes an issue where Chrome could unexpectedly open the wrong file when attempting to open an extensionless file while an executable of the same name was present in the Downloads folder. For example, downloading and opening "somefile" while "somefile.exe" was already present in Downloads would result in "somefile.exe" being run. This behavior is due to Windows' shell open functionality, which appears to have special logic to interpret extensionless commands as potential executables. Prior to this change, if an extensionless file was opened without an executable of the same name present (the more common scenario), Windows would display error "No application is associated with the specified file for this operation", so this change does not remove any functionality apart from the ability to trigger this error popup. Showing the extensionless file in folder sets the user up nicely to open the file however they want from Windows Explorer via right-click > Open With. Bug: 1092518 Change-Id: I1a3bb519867548c916070cbfebd64d0017f5937b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2321528 Commit-Queue: Jesse McKenna <jessemckenna@google.com> Reviewed-by:
Shakti Sahu <shaktisahu@chromium.org> Cr-Commit-Position: refs/heads/master@{#796968}
-
Ryan Hansberry authored
Change-Id: I06270079771302e8d9542e012078e0f844d32896 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2349287 Commit-Queue: Alex Chau <alexchau@chromium.org> Reviewed-by:
Alex Chau <alexchau@chromium.org> Cr-Commit-Position: refs/heads/master@{#796967}
-
Dan Sanders authored
Previously we set the limit to zero, meaning no limit, but FFmpeg 4.3 will not allocate at all with that setting. Changed to std::numeric_limits<size_t>::max(). Bug: 1095962 Change-Id: I96820c21f794f2814e955ee75ff22dfd31804c29 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2349405Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Dan Sanders <sandersd@chromium.org> Cr-Commit-Position: refs/heads/master@{#796966}
-
Victor Costan authored
Bug: 1068710 Change-Id: Id150b86cb4532ab0d51e4a314573641d8ba2fef9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2348334 Auto-Submit: Victor Costan <pwnall@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Commit-Queue: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#796965}
-
Sebastien Lalancette authored
Fixes the bad behavior in three components: - History - Reading List - Bookmarks Bug: 1093302 Change-Id: Ia81bfd270e898c3061eb7ad061cc5aea338dc947 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2349270Reviewed-by:
Sergio Collazos <sczs@chromium.org> Commit-Queue: Sebastien Lalancette <seblalancette@chromium.org> Cr-Commit-Position: refs/heads/master@{#796964}
-
Liviu Tinta authored
On Mac, tiltY is positive when the pen is tilted away from the user. Based on Pointer Event spec, tiltY should be positive when the pen is tilted towards the user. On Mac, by default Y increases going up, while in Chromium Y increases going down. NSView has isFlipped property which controls if Y increases going up (false) or going down (true). In order to fix the bug, we check NSView's isFlipped flag and if it is false we reverse the sign of tiltY to accommodate the difference in the direction of Y. Bug: 1111347 Change-Id: I108ba496adc6f951277e1c9ddb7eaf6483e522f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2348544Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Commit-Queue: Liviu Tinta <liviutinta@chromium.org> Cr-Commit-Position: refs/heads/master@{#796963}
-
Lukasz Anforowicz authored
This CL adds a DCHECK to RenderFrameHostManager::GetFrameHostForNavigation to make sure that the |dest_site_instance| computed earlier is in the same BrowsingInstance as the frame's parent: DCHECK(!parent || dest_site_instance->IsRelatedSiteInstance( parent->GetSiteInstance())); Bug: 1107269 Change-Id: I89b79e93e8435f12a51bf3e49472a44ce7ddb47e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2347074 Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Reviewed-by:Charlie Reis <creis@chromium.org> Cr-Commit-Position: refs/heads/master@{#796962}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/0376edf14e58..f07b5182eeda 2020-08-11 hjd@google.com Merge "Add cpuhp ftrace events" 2020-08-11 simonmacm@google.com We're in a for loop so don't return. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:linux-perfetto-rel Bug: chromium:163530191 Tbr: perfetto-bugs@google.com Change-Id: I490535d91bf44e7e31681c4dddcd9083e3def10a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2349404Reviewed-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@{#796961}
-
James Cook authored
Also move it and AshChromeServiceImpl into namespace crosapi. This is consistent with our plan for interface names from go/lacros-main-dd. Bug: none Change-Id: Ice369bd8da4ebdc9de4de2a69ce7a457ed13968a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2349888 Commit-Queue: James Cook <jamescook@chromium.org> Commit-Queue: Erik Chen <erikchen@chromium.org> Auto-Submit: James Cook <jamescook@chromium.org> Reviewed-by:
Erik Chen <erikchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#796960}
-
Gary Tong authored
Bug: 1106950 Change-Id: I69a3a8df07f40d0cc24de3f85212e51d5945bd46 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2350149 Auto-Submit: Gary Tong <gatong@chromium.org> Reviewed-by:
Erik Staab <estaab@chromium.org> Commit-Queue: Erik Staab <estaab@chromium.org> Cr-Commit-Position: refs/heads/master@{#796959}
-
Yusuke Sato authored
Previously, the code had 10 boilerplate code for starting/stopping Upstart jobs for ARCVM. This CL reduce the amount of such code by allowing the adapter to pass a list of jobs to start/stop to the helper function. BUG=None TEST=try Change-Id: I3f95dcd1b482a7ae3204ed00d9644bd89f508c21 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2343376 Commit-Queue: Yusuke Sato <yusukes@chromium.org> Reviewed-by:
Hidehiko Abe <hidehiko@chromium.org> Cr-Commit-Position: refs/heads/master@{#796958}
-
Chong Gu authored
Remove the need for --device arg on our FYI and CI bots. Change-Id: I8115f2d2246b1385d8695926a84a8df51c833214 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2277422Reviewed-by:
Robert Ma <robertma@chromium.org> Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
Brian Sheedy <bsheedy@chromium.org> Commit-Queue: Chong Gu <chonggu@google.com> Cr-Commit-Position: refs/heads/master@{#796957}
-
Piotr Bialecki authored
(potential) Fix for flakiness has already landed, but the test got disabled before that happened. This CL will reenable the test. In case the fix is not sufficient to get rid of flakiness, the test logic will have to be rewritten. Bug: 1112773 Change-Id: Ifeb07c6b9cf30e587d7804f0b3af9e345e550c5d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346923 Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Auto-Submit: Piotr Bialecki <bialpio@chromium.org> Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/0b969adbdff1..ae8f8fdcda03 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC slightlyoff@google.com,ellyjones@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: slightlyoff@google.com,ellyjones@google.com Change-Id: I1b1e147930d54898ef08cced93496a30b1608132 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2349393Reviewed-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@{#796955}
-
Rouslan Solomakhin authored
This is a reland of b772a8f1 Original patch: https://crrev.com/c/2341163 Revert: https://crrev.com/c/2348532 Reason for revert: New WPT test revealed a memory issue in //third_party/blink/renderer/modules/payments/payments_validators.cc when serializing data larger than than 1MB into JSON. Reason for reland: Split out the large data serialization tests into a separate patches for fixing the JSON serialization issue separately: 1) https://crrev.com/c/2348411 2) https://crrev.com/c/2348540 3) https://crrev.com/c/2346973 Original change's description: > [Web Payment] Secure payment confirmation Blink parameters. > > Before this patch, requesting "secure-payment-confirmation" method in > PaymentRequest API would not validate the parameters. > > This patch adds the "secure-payment-confirmation" parameters to > PaymentRequest API and validates them, if the > "SecurePaymentConfirmation" feature is enabled. > > After this patch, PaymentRequest API validates the secure payment > confirmation parameters. > > Explainer: https://github.com/rsolomakhin/secure-payment-confirmation > Feature status: https://chromestatus.com/feature/5702310124584960 > Intent to prototype: > https://groups.google.com/a/chromium.org/g/blink-dev/c/myUR5gyd5Js/m/iELL67NQAgAJ > > Bug: 1110324 > Change-Id: I7a4b6f9da1b3e1d7604bcd9e4733dc789f77ec4b > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2341163 > Reviewed-by: Nick Burris <nburris@chromium.org> > Reviewed-by: Kouhei Ueno <kouhei@chromium.org> > Auto-Submit: Rouslan Solomakhin <rouslan@chromium.org> > Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#796792} TBR=ellyjones, nburris, kouhei Bug: 1110324, 1115091 Change-Id: I05ebdbfe234d3bee8ceb2016dafc5679a9a28ef9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2348410 Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org> Reviewed-by:
Rouslan Solomakhin <rouslan@chromium.org> Reviewed-by:
Nick Burris <nburris@chromium.org> Cr-Commit-Position: refs/heads/master@{#796954}
-
ckitagawa authored
This is an alternative/complimentary change to http://crrev.com/c/2346905 Using First Meaningful Paint has two benefits. 1. It waits for key content to paint. 2. It doesn't wait for total loading to stop just down to a couple network requests. This is good in that we stop showing the preview earlier (which is desirable if the page is actually painted sooner). I think both this and LoadingProgress are feasible. This one is more promising in the sense that it takes a guess as to when the painting is mostly done whereas the PageLoadProgress variant is mostly about network requests being done. One option might be to combine the two and take the later of the signals? With these changes it might be worth making the removal delay 0 ms or at least smaller. Bug: 1110360 Change-Id: I6c4400166d0bfef57160424de2238bcbe238949a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346863Reviewed-by:
Mehran Mahmoudi <mahmoudi@chromium.org> Commit-Queue: Calder Kitagawa <ckitagawa@chromium.org> Cr-Commit-Position: refs/heads/master@{#796953}
-
Liviu Tinta authored
Intent to Ship link: https://groups.google.com/a/chromium.org/forum/?utm_medium=email&utm_source=footer#!msg/blink-dev/ZRI-7X_4GwM/Sp1ZMIw5AgAJ Bug: 1069500 Change-Id: I01630006c2eebb1fdb0b09a08af59cf230ed33f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2343385Reviewed-by:
Mustaq Ahmed <mustaq@chromium.org> Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Liviu Tinta <liviutinta@chromium.org> Cr-Commit-Position: refs/heads/master@{#796952}
-
Dave Tapuska authored
AutoResize only worked for the top level widget. Move the handling from RenderWidget into WebViewFrameWidget. BUG=1097816 Change-Id: I66f18640531676c688fe3ee149ed253d4f01c0a0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317807Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Cr-Commit-Position: refs/heads/master@{#796951}
-
Gang Wu authored
This CL enable copy image by default before enable copy image experiment to 100%. Bug: 1043329 Change-Id: Iad07f1bf496449f8e02e24f3a3d9de8f3a8dec57 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2298180Reviewed-by:
Tomasz Wiszkowski <ender@google.com> Reviewed-by:
-
Zhongyi Shi authored
Bug: 1114590, 1090532 Change-Id: Ic149aa63ee65fe2f78c4bb8f28497677ec4ac4c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2347325 Commit-Queue: Zhongyi Shi <zhongyi@chromium.org> Reviewed-by:
-
Devlin Cronin authored
Content scripts can specify if they should be injected in about:-scheme frames or use the effective origin as a fallback in the case of e.g. opaque frames. Currently, these are stored in two separate booleans on the user script. Instead, use a single enum to track this behavior, with three settings: match, don't match, or match and climb the frame tree for about: frames (the latter is necessary for the current behavior of about:blank). Update UserScript and references appropriately, and add additional unit test coverage for match_about_blank and use_origin_as_fallback. This CL does not change behavior for match_about_blank. match_origin_as_fallback now matches both data: and about: schemes. Bug: 55084 Change-Id: I3a52a244a8a6b0b3535608d8a6551aa94057aa22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2343312 Commit-Queue: Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Karan Bhatia <karandeepb@chromium.org> Cr-Commit-Position: refs/heads/master@{#796948}
-
John Lee authored
Bug: 973674 Change-Id: I88427bb8259bda94af6550228e7925212df791a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2341178Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Commit-Queue: John Lee <johntlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#796947}
-
Elly Fong-Jones authored
It is flaky on Linux. Bug: 1115201 Change-Id: I6fc6b61d511decb288d2d311f9a412bd8bc98e6e Tbr: cduvall@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2349669Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#796946}
-
James Long authored
This change brings in the vue-material package and updates the UI to use its Material design components. All the graph controls are now in a sidebar, and the graph canvas is responsive to fit the size of the page. Bug: 1102546 Change-Id: If47d8319337a9700bd921ba3938d3fe3da7b67b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2347407Reviewed-by:
Mohamed Heikal <mheikal@chromium.org> Reviewed-by:
Samuel Huang <huangs@chromium.org> Commit-Queue: James Long <yjlong@google.com> Cr-Commit-Position: refs/heads/master@{#796945}
-
Weilun Shi authored
Add extract_histograms_test to metrics_python_tests so that extract_histograms_test will be run by trybot. Bug: 1114894 Change-Id: Ieae44071631a018e705dd11baa60fe0ab7cd9d7f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2347891 Commit-Queue: Steven Holte <holte@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Auto-Submit: Weilun Shi <sweilun@chromium.org> Cr-Commit-Position: refs/heads/master@{#796944}
-
Liviu Tinta authored
Different browsers fire different number of events for this test. Stop the test when the done button is clicked instead of when a certain number of events are fired. There are significant differences in how browsers fire pointer events and compatible mouse events when an element is removed from the DOM. There is a discussion here: https://github.com/w3c/pointerevents/issues/285 about the order of pointerenter events and compatible mouseenter events when an element is removed from the DOM. Once the discussion is finalized and there is consensus this test might have to be adjusted. Change-Id: I5202eb7a1fcc557985279a978596c9446105f417 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2348530 Commit-Queue: Liviu Tinta <liviutinta@chromium.org> Reviewed-by:
-
Olesia Marukhno authored
Add accessibility support for pedals and dedicated row. Updated announcements for normal state to include information about available actions (pedals, search, switch to tab). If there are multiple actions available, they aren't read individually but suggestion to iterate over them is read. Added announcements for pedal buttons and search button when they are focused. Message for focused pedals doesn't include information about suggestion because the suggestion information doesn't contain any additional information about pedal. Bug: 1104264 Change-Id: I740afef8c8bc39cadd4ca5f5d5d263f4481d32af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339626Reviewed-by:
Aaron Leventhal <aleventhal@chromium.org> Reviewed-by:
Tommy Li <tommycli@chromium.org> Reviewed-by:
Bret Sepulveda <bsep@chromium.org> Commit-Queue: Olesia Marukhno <olesiamarukhno@google.com> Cr-Commit-Position: refs/heads/master@{#796942}
-
Mikhail Khokhlov authored
A benchmark to measure the power effect of downloading one big vs several small files. Bug: b/161112814 Change-Id: Ia27528bcf3aac9acd3e0602cc11df5561f47b83f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2329304Reviewed-by:
Wenbin Zhang <wenbinzhang@google.com> Reviewed-by:
Eric Seckler <eseckler@chromium.org> Commit-Queue: Mikhail Khokhlov <khokhlov@google.com> Cr-Commit-Position: refs/heads/master@{#796941}
-
Takumi Fujimoto authored
This fixes a regression relative to the extension MRP where we were establishing a presentation connection only if a client ID is set. If mirroring is initiated by a site with cast:0F5096E8 there is no client ID but we still need a presentation connection. Bug: 1114891, b/163366468 Change-Id: Ib66768c52851bb87aba307775d917b81bf669572 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2347890 Commit-Queue: Takumi Fujimoto <takumif@chromium.org> Reviewed-by:
mark a. foltz <mfoltz@chromium.org> Cr-Commit-Position: refs/heads/master@{#796940}
-
Collin Baker authored
This enables mocking in tests. It also is a step towards exposing the interface in chrome/browser/ui. Bug: 1106523 Change-Id: If909e252e982857975aacf348a90d9ef0269dee4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2343321Reviewed-by:
Dana Fried <dfried@chromium.org> Commit-Queue: Collin Baker <collinbaker@chromium.org> Cr-Commit-Position: refs/heads/master@{#796939}
-
Adrienne Walker authored
Once AppCache has been removed from Chrome, sites will have no way of cleaning up user data in local profiles. To fix this, when a storage partition is accessed when AppCache has been disabled, we will delete the AppCache directory from that profile directory. Bug: 1081897 Change-Id: Iea404f7c83595ba1397fab4a5d3f97d1e3280916 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2343588 Commit-Queue: enne <enne@chromium.org> Reviewed-by:
Marijn Kruisselbrink <mek@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#796938}
-
zhaoyangli authored
WebRTC test configs were fixed in crrev/c/2321333. The workaround is no longer needed and removed in this CL. Bug: 1110375 Change-Id: I57acb3f10de89eb810c79f46baf811111c35d8e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2347973Reviewed-by:
Justin Cohen <justincohen@chromium.org> Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org> Cr-Commit-Position: refs/heads/master@{#796937}
-
Thiabaud Engelbrecht authored
As detailed in this CL: https://chromium-review.googlesource.com/c/chromium/src/+/2314832 These should have been "Small", they currently don't show up in the UMA. Bug: 1106364 Change-Id: I7c7b040d5cbfab25c579668951e2e0a16cf3a76a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2348704Reviewed-by:
Benoit L <lizeb@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Commit-Queue: Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#796936}
-
Marijn Kruisselbrink authored
Bug: 1114898 Change-Id: I0b527a8fdc2dd4d5fcb5b9eb7140fa8ac4faa069 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2347921 Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#796935}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/f867ba8b5d48..5401bad7015d 2020-08-11 nisse@webrtc.org Prepare for deleting VideoCodec::plType 2020-08-11 dharmesh.r.chauhan@gmail.com Disable switch camera and route change buttons when processing 2020-08-11 titovartem@webrtc.org Move initialization of GoogleMock and flags to main from test_main_lib 2020-08-11 philipp.hancke@googlemail.com video_replay: wrap main thread 2020-08-11 hta@webrtc.org Reland "Implement transceiver.stop()" If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: chromium:980879 Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I0f20716350e06947f7d98ebcf9908ccec75a7ec0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2349390Reviewed-by:
-
