- 05 Mar, 2020 40 commits
-
-
Nina Satragno authored
crrev.com/c/2084725 moved the timeout adjustment logic to the browser side while keeping the old behaviour to make internal android source happy. This removes the old behaviour. Fixed: 976428 Change-Id: I2c6acb06f3efc6c4efbfc917b06a06603b81e7e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2090091 Commit-Queue: Nina Satragno <nsatragno@chromium.org> Commit-Queue: Ken Buchanan <kenrb@chromium.org> Auto-Submit: Nina Satragno <nsatragno@chromium.org> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Cr-Commit-Position: refs/heads/master@{#747346}
-
Peter Kasting authored
* Simplify AshTestHelper::SetUp() API use by making InitParams arg optional * Rename AshTest*::CurrentContext() to GetContext() to match Views helper class API names * Minor cleanups to ChromeViewsTestBase * NULL -> nullptr to silence presubmit Bug: none Change-Id: If55b08d31a3d244852d3e7aab73e4270e94cde5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2088734Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#747345}
-
Travis Skare authored
BUG: 1046814 Change-Id: I704099fce2d703f964d16be46f8a7c4c0be07e78 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1954671Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Reviewed-by:
Kristi Park <kristipark@chromium.org> Commit-Queue: Travis Skare <skare@chromium.org> Cr-Commit-Position: refs/heads/master@{#747344}
-
Ben Joyce authored
Change-Id: Ib82dc3a17382d8f20d0ccf0d840ff7f6bc4b606c Bug: 1052460 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2088404 Commit-Queue: benjamin joyce <bjoyce@google.com> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Cr-Commit-Position: refs/heads/master@{#747343}
-
Wez authored
Bug: 1050703 Change-Id: I09b9c20f631a6dda0a424790ac7f55ada0f144d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2056947 Commit-Queue: Wez <wez@chromium.org> Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Cr-Commit-Position: refs/heads/master@{#747342}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/7c0409aa3814..f365c53a18b1 git log 7c0409aa3814..f365c53a18b1 --date=short --first-parent --format='%ad %ae %s' 2020-03-05 taylori@google.com Merge "perfetto-ui: Fix counter quantization" Created with: gclient setdep -r src/third_party/perfetto@f365c53a18b1 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/+/master/autoroll/README.md Bug: None Tbr: perfetto-bugs@google.com Change-Id: I9f1496de8f76cf68115b362d70f759719d2ea452 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2090074Reviewed-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@{#747341}
-
Mark Cogan authored
Plumbs a Browser into BookmarkHomeViewController and BookmarkInteractionController. This removes explicit passing of BrowserState, WebStateList and Dispatcher into these classes. Unit tests are also updated, including fixing incorrectly named members in the Bookmarks test superclass. Bug: 1057116, 1057121 Change-Id: Ifdf674c76dc3d449f49ef22d48a4bdc4c8ffceec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2087921 Commit-Queue: Mark Cogan <marq@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#747340}
-
Maksim Ivanov authored
This moves the error label a bit down in the SAML smart card PIN dialog, in conformance to the UI feedback. As was clarified by the designers, the padding should be 4px to the upper bound of the text box, not to the upmost pixel of the font. Conceptually, the error message should look centered between the input field and the keypad below. This CL moves the error label by 3 pixels downwards, in accordance to this corrected understanding of the requirements. Bug: 1024251 Test: start SAML login via a smart card, proceed to PIN dialog, take a screenshot, verify the distance Change-Id: I3e2aa96151254595424010e4db33673f5ddd0d31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2089757Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Commit-Queue: Maksim Ivanov <emaxx@chromium.org> Cr-Commit-Position: refs/heads/master@{#747339}
-
Liquan (Max) Gu authored
Before Change: View depends on ChromeActivity, ActivityWindowAndroid, ContentView. After Change: View no longer depends on them. Change: Move the dependencies into Coordinator. Bug: 1058844 Change-Id: Ifb8653855111d4d2fcf7ece0436fa466543f4ca0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2089972 Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org> Reviewed-by:
Rouslan Solomakhin <rouslan@chromium.org> Cr-Commit-Position: refs/heads/master@{#747338}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/2de34c1791f3..56f1678437ba git log 2de34c1791f3..56f1678437ba --date=short --first-parent --format='%ad %ae %s' 2020-03-05 david.turner.dev@gmail.com Vulkan: Enforce fixed subgroup size for compute shaders. 2020-03-05 david.turner.dev@gmail.com Vulkan: Report and enable subgroup size control device extension. Created with: gclient setdep -r src/third_party/dawn@56f1678437ba If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/dawn-chromium-autoroll Please CC cwallez@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel Bug: None Tbr: cwallez@google.com Change-Id: I9f48a7973e626b96d1088b0b916745f02c70769b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2090072Reviewed-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@{#747337}
-
sandromaggi authored
Bug: 1058599 Change-Id: I80f0396a7d43ad2e5c2ffcf93165544391c4c801 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2089671 Commit-Queue: Sandro Maggi <sandromaggi@google.com> Reviewed-by:
Clemens Arbesser <arbesser@google.com> Cr-Commit-Position: refs/heads/master@{#747336}
-
Sammie Quon authored
It uses solid color layer and full size texture for the border right now. Since there is texture for the border, just paint the background so that when we do layer opacity, there is no render pass. ui.OverviewDragPerf.drag_to_snap 53.5ms -> 52ms ui.DragWindowFromShelfPerf (WIP) 52ms -> 51ms So not that much gains, but code is also simpler. Test: manual Bug: 1024679 Change-Id: Id5554c25cd69e42e31f97c8426b2ceec78f3fd2f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2087349 Commit-Queue: Sammie Quon <sammiequon@chromium.org> Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Cr-Commit-Position: refs/heads/master@{#747335}
-
Rob Schonberger authored
Bug: 911427 Change-Id: Ib3ffd449c8772ac7993b861255c5ecc6ebcb55e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2087499 Auto-Submit: Rob Schonberger <robsc@chromium.org> Commit-Queue: Jenny Zhang <jennyz@chromium.org> Reviewed-by:
Jenny Zhang <jennyz@chromium.org> Cr-Commit-Position: refs/heads/master@{#747334}
-
George Steel authored
Sync on style before evaluating a pseudo-element selector other than null. Remove manual style syncs from pseudo-element animation wpt tests. Bug: 1057101 Change-Id: I8a1184221f40c7546ac5179615f0d6541e8729e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2083715Reviewed-by:
Majid Valipour <majidvp@chromium.org> Commit-Queue: George Steel <gtsteel@chromium.org> Cr-Commit-Position: refs/heads/master@{#747333}
-
Siddharth Sharma authored
Issue: In case a new_profile is mergeable with one of the existing_profiles, AutofillProfileComparator::MergeProfile inadvertently ends up modifying the existing profile directly as part of the merge by calling AutofillProfile::SaveAdditionalInfo on them. These modified profiles are then added to merged_profiles which is the out parameter. So at this point there is no diff between the merged_profiles and the existing_profiles that we passed. Later when we compare the two (in PersonalDataManager::SetProfiles), since there is no diff, we end up not writing the updates to the DB. Fix: We instead pass a const ref to AutofillProfileComparator::MergeProfile so that we don't end up modifying the original set of profiles and work on a copy of them. This ensures that we capture the updates in case of a merge and write it to the web DB. R=battre@chromium.org Bug: 1057041 Change-Id: Idcabbd9549dc2f8a3dfec582194fd316818c654d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2087297Reviewed-by:
Dominic Battré <battre@chromium.org> Commit-Queue: Siddharth Sharma <siddhash@microsoft.com> Cr-Commit-Position: refs/heads/master@{#747332}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/3c91b31162b8..b05ca4b6168c git log 3c91b31162b8..b05ca4b6168c --date=short --first-parent --format='%ad %ae %s' 2020-03-05 orphis@webrtc.org Implement new specification for degradation preference Created with: gclient setdep -r src/third_party/webrtc@b05ca4b6168c 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/+/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: Ice79f35e77f79b0225b738a4395ca58f75597e59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2090071Reviewed-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@{#747331}
-
Milica Selakovic authored
Credential leak dialog is component in development and it is forked so experimental code with password change can be introduced without affecting component. When password change from leaked warning prototype finished it will be merged with main component. Bug: 1053522 Change-Id: If105bdd40e46e2a92a2a2f9589b377679299141b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080233 Commit-Queue: Milica Selakovic <selakovic@google.com> Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Reviewed-by:
Ioana Pandele <ioanap@chromium.org> Cr-Commit-Position: refs/heads/master@{#747330}
-
Joshua Pawlicki authored
Bug: 1048653 Change-Id: Ia3c19908bb49194c4f4bda98b8316176b29a5e9d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2090231 Auto-Submit: Joshua Pawlicki <waffles@chromium.org> Reviewed-by:
Sorin Jianu <sorin@chromium.org> Commit-Queue: Joshua Pawlicki <waffles@chromium.org> Cr-Commit-Position: refs/heads/master@{#747329}
-
Chris Lu authored
This TabHelper will observe WebStateObserver and record page sessions while its WebState is the active WebState (i.e. it is visible on the screen). When a new page is navigated to, the app backgrounds, or if the WebState is destroyed, the recording will stop and a UKM will be logged for the page session duration.A new IOS.PageNavigation UKM will be logged for every navigation completion. Bug: 1006357 Change-Id: I9c7184a1cc3d8f9ff1a39f34f3363a388738e82a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068244 Commit-Queue: Chris Lu <thegreenfrog@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Reviewed-by:
Annie Sullivan <sullivan@chromium.org> Cr-Commit-Position: refs/heads/master@{#747328}
-
Dominik Röttsches authored
In unit tests, it turns out that the AtomicFlag may still be stuck to its previous sequence. Detach it in UnsafeResetForTesting to avoid that. Change-Id: I34b2e4953424c5aebd6ec55c8b13086617a16098 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2089759Reviewed-by:
Gabriel Charette <gab@chromium.org> Commit-Queue: Dominik Röttsches <drott@chromium.org> Cr-Commit-Position: refs/heads/master@{#747327}
-
Maksim Ivanov authored
Non-functional changes: * Add browser test boilerplate for testing the <security-token-pin> Polymer element. * Add a test that an 8-character PIN fits into the input field (which tests the functionality initially added in https://crrev.com/c/2069324); * Add a test that the letter-spacing attribute doesn't fall back to the default value (which tests the regression that was fixed in https://crrev.com/c/2082378); Functional changes: * Reduce the interval between the dots by one pixel, so that 8 dots actually fit into the input field (the interval used before this CL turned out to be exceeding the input width by 1 pixel). Bug: 1051859 Change-Id: If93757b19806067e29718e00c64f4ce5549931a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2081420Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Commit-Queue: Maksim Ivanov <emaxx@chromium.org> Cr-Commit-Position: refs/heads/master@{#747326}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/4b1eadeb..fbadeeaf Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: Iec9ca3c5afbacda564fa9f48919b31667be03f1b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2089399Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#747325}
-
Charlie Hu authored
Renames media_element_parser_helpers::ReportUnsizedMediaViolation to media_element_parser_helpers::CheckUnsizedMediaViolation Combines logic of LayoutVideo::UpdateAfterLayout with LayoutImage::UpdateAfterLayout because LayoutVideo is a subclass of LayoutImage. Calls Document::IsFeatureEnabled with ReportOption::kReportOnFailure instead of Document::CountPotentialFeaturePolicyViolation and Document::ReportFeaturePolicyViolation which are lower level APIs. This CL is also the prework for migration of UnsizedMedia from feature policy to document policy. Bug: 993790 Change-Id: I77eb2be3b5fe9d79d276800e12f4a0218fdb6e51 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2082480Reviewed-by:
Ian Clelland <iclelland@chromium.org> Reviewed-by:
Philip Jägenstedt <foolip@chromium.org> Commit-Queue: Charlie Hu <chenleihu@google.com> Cr-Commit-Position: refs/heads/master@{#747324}
-
Hesen Zhang authored
- Added a feature flag for the migration. - Added and hid new code path in OfflineNotificationBackgroundTask. - Created JNI bridge for gluing prefetch notification service in native. Bug: 1047037 Change-Id: If7b728609f86665cfe6b4c61f521f7362000b292 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2082087Reviewed-by:
David Trainor <dtrainor@chromium.org> Reviewed-by:
Xing Liu <xingliu@chromium.org> Commit-Queue: Hesen Zhang <hesen@chromium.org> Cr-Commit-Position: refs/heads/master@{#747323}
-
Arthur Hemery authored
The Cross-Origin-Opener-Policy header should not be taken into consideration when doing subframe navigations. This is enforced by this patch. Bug: 1018655 Change-Id: Icd2846c5992fb795b955101dec91950e5e7008cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2087716 Commit-Queue: Arthur Hemery <ahemery@chromium.org> Reviewed-by:
Camille Lamy <clamy@chromium.org> Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#747322}
-
Christopher Cameron authored
Remove ExtensionAppShimHandlerMac::Delegate:: MaybeGetAppExtension. That's the goal of this patch. Removing it means no longer playing with extensions:: Extensions directly in ExtensionAppShimHandlerMac. To accomplish what we were doing by those queries, add the following new Delegate functions - AppIsInstalled - AppCanCreateHost (rename of AllowShimToConnect) - AppUsesRemoteCocoa - AppIsMultiProfile Also rename GetHostForBrowser to GetHostForRemoteCocoaBrowser, to clarify that it is only for use with PWAs. After this, we'll get rid of the ExtensionAppShimHandlerMac static functions MaybeGetAppExtension and MaybeGetAppForBrowser, and move ExtensionAppShimHandlerMac to a separate place where it can select between extension and app functions based on id. R=loyso TBR=ellyjones (chrome/browser/ui/views) Bug: 1057195 Change-Id: Ia29810633ec91b7e74a156902fa7f4c952c16eb5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2088711 Commit-Queue: ccameron <ccameron@chromium.org> Reviewed-by:
Alexey Baskakov <loyso@chromium.org> Cr-Commit-Position: refs/heads/master@{#747321}
-
Stefano Sanfilippo authored
Also, tidy up enforcement headers in WPTs, update one. Bug: 1058437 Change-Id: Ic24b0297af04230562b104fd6664387cba5b169b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2089772Reviewed-by:
Mike West <mkwst@chromium.org> Reviewed-by:
Daniel Vogelheim <vogelheim@chromium.org> Commit-Queue: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#747320}
-
Josh Nohle authored
The chrome://proximity-auth debug page converts the next enrollment/sync attempt times to milliseconds and stores them as double base::Values. If no future attempt is scheduled, base::TimeDelta::Max() is sent. However, the conversion to a double base::Value is not allowed unless std::isfinite() is true. Bug: 899080, 951969 Change-Id: I56c7633283f9cc85ff59e2f34fab98e64ac9c146 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2081011 Auto-Submit: Josh Nohle <nohle@chromium.org> Reviewed-by:
James Vecore <vecore@google.com> Commit-Queue: Josh Nohle <nohle@chromium.org> Cr-Commit-Position: refs/heads/master@{#747319}
-
Carlos IL authored
When the mixed content autoupgrade feature is enabled, content that would have been autoupgraded but is already HTTPS does not get the UpgradeIfInsecure flag set, which means if it is eventually redirected to HTTP, that mixed content is not upgraded. This CL fixes that and adds a regression test. Bug: 1058077 Change-Id: I359d720ea5caf0833fabd810de7876e32f17b099 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2086258 Auto-Submit: Carlos IL <carlosil@chromium.org> Commit-Queue: Mike West <mkwst@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Reviewed-by:
Daniel Vogelheim <vogelheim@chromium.org> Cr-Commit-Position: refs/heads/master@{#747318}
-
Luum Habtemariam authored
Design prop: go/cups-printers-manager-refactor This change removes EnterprisePrintersProvider from SyncedPrintersManager and sources enterprise printers to CupsPrintersManager directly. SyncedPrintersManager is now solely responsible for saved printers. Bug: chromium:1030127 Test: updated tests pass Change-Id: I0fd78f2414f03b00858c107d0efacff406687658 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2072669 Commit-Queue: Scott Violet <sky@chromium.org> Auto-Submit: Luum Habtemariam <luum@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Sean Kau <skau@chromium.org> Reviewed-by:
Piotr Pawliczek <pawliczek@chromium.org> Cr-Commit-Position: refs/heads/master@{#747317}
-
Omer Katz authored
Bug: 986235 Change-Id: I4145597523c378f84c9db9cd98822751de7c5e7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2089773 Commit-Queue: Omer Katz <omerkatz@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Auto-Submit: Omer Katz <omerkatz@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#747316}
-
Ben Pastene authored
Bug: 812428 Change-Id: If15779eebc64714a2a8f27f45379317edbc513f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2088498Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#747315}
-
Adam Whiteside authored
Per device-id volume limits mean the content type exception is no longer needed. (https://chromium-review.googlesource.com/c/chromium/src/+/2071483) Instead, the new focus type can be used to ensure the correct ducking behavior: (https://chromium-review.googlesource.com/c/chromium/src/+/2080583) Bug: internal 144181483 Change-Id: I2ff83d18d142763f39ae6ea5ff0142b47142c9f1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2088836Reviewed-by:
Kenneth MacKay <kmackay@chromium.org> Commit-Queue: Kenneth MacKay <kmackay@chromium.org> Auto-Submit: Adam Whiteside <awhiteside@google.com> Cr-Commit-Position: refs/heads/master@{#747314}
-
Anna Malova authored
Bug: 1007815 Change-Id: I14f5647a693f63d63ffa457190e02dac0727ef00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2089756 Commit-Queue: Matt Menke <mmenke@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#747313}
-
Renato Silva authored
Bug: 1023370 Change-Id: I6c6ffe4ac5616b884edc7137178ee6bebfefc020 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2089874Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Commit-Queue: Denis Kuznetsov [CET] <antrim@chromium.org> Cr-Commit-Position: refs/heads/master@{#747312}
-
Anna Malova authored
Bug: 1007815 Change-Id: I69d56f2ef9967764f1ab1f964d87f621bcf84685 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2089836 Commit-Queue: Matt Menke <mmenke@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#747311}
-
Chris Thompson authored
This makes the (i) icon on the Legacy TLS interstitial page match the Lookalike interstitial page for dark mode (otherwise it is too dark). Bug: 1058610 Change-Id: I840b54012236e52fe5968afcc8f34bbcf5ed45da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2088676 Auto-Submit: Christopher Thompson <cthomp@chromium.org> Reviewed-by:
Emily Stark <estark@chromium.org> Commit-Queue: Christopher Thompson <cthomp@chromium.org> Cr-Commit-Position: refs/heads/master@{#747310}
-
Akihiro Ota authored
Bug: 1058472 Change-Id: I66f4c77f02f2486fe151bfbd4142015798a9b2d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2087493Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: Akihiro Ota <akihiroota@chromium.org> Cr-Commit-Position: refs/heads/master@{#747309}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/b0d65f1b3c40..daac106699e1 git log b0d65f1b3c40..daac106699e1 --date=short --first-parent --format='%ad %ae %s' 2020-03-05 aerotwist@chromium.org [global] Remaps self.SDK.targetManager Created with: gclient setdep -r src/third_party/devtools-frontend/src@daac106699e1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.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/+/master/autoroll/README.md Bug: chromium:1058320 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I8ea08e1dbc07f45e4479ee9a1b70e5452d12ae38 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2089587Reviewed-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@{#747308}
-
Roman Sorokin authored
* Show overlay for the 3rd-party SAML page. * Hide bottom buttons for the 3rd-party SAML page. Unfortunately my refactoring CL:2046174 is still in-flight. So I followed the model from CL:2000938 in the meantime. As this is needed for M82. Fixed: 1001281 Change-Id: Ia8f2d8cbabb2f44e387ad5f76b6a83997654ae9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2089734Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Commit-Queue: Roman Sorokin [CET] <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#747307}
-