- 05 Jan, 2021 40 commits
-
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1609821402-aadb54447d521b648e35bdaecfd53290f25cbd03.profdata to chrome-win64-master-1609837154-ace0713e1aa3951abed358afe7726a9f9d3a73a1.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win64-chromium Please CC pgo-profile-sheriffs@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:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I92ee2c4f37327c54f853fa89f0eaa31695f6f902 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2606001Reviewed-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@{#840137}
-
Mihai Sardarescu authored
UrlKeyedAnonymizedDataCollectionEnabled is enabled by the sync consent UI when the user opts in to sync. The tests rules should mirror this behavior and only enable sync when the sync is enabled (and not when sign-in is enabled). This CL removes enabling URL-keyed anonymized data collection on sign-in. Bug: None. Change-Id: I7cf437874d97359d033e71d17122daf8d927c59b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2598903 Commit-Queue: Mihai Sardarescu <msarda@chromium.org> Reviewed-by:
Alice Wang <aliceywang@chromium.org> Reviewed-by:
Boris Sazonov <bsazonov@chromium.org> Cr-Commit-Position: refs/heads/master@{#840136}
-
Clemens Arbesser authored
Bug: b/173104767 Change-Id: Id500736a6c130a6f81368080980d1dffe9a1bf93 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2610096 Auto-Submit: Clemens Arbesser <arbesser@google.com> Commit-Queue: Mathias Carlen <mcarlen@chromium.org> Reviewed-by:
Mathias Carlen <mcarlen@chromium.org> Cr-Commit-Position: refs/heads/master@{#840135}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/bc804095bcad..ee8ca5255488 2021-01-05 primiano@google.com Merge "Update CHANGELOG for v11.0" 2021-01-05 treehugger-gerrit@google.com Merge "Minimal edits to heap_profile.h comments" 2021-01-05 fmayer@google.com Merge "Enable new clang-tidy checks & resolve for src/profiling." 2021-01-05 fmayer@google.com Merge changes I174d77b5,I114d9aa1 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: None Tbr: perfetto-bugs@google.com Change-Id: Ia68950e961fa95d0944e44cc852cd3686857ced7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2609876Reviewed-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@{#840134}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/53386e30..3abec731 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,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I65faeedf3db0b60791cf2aba807f1f4310f3cee3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2610470Reviewed-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@{#840133}
-
arthursonzogni authored
Make sure sandbox flags are properly inherited when the initiator of the navigation isn't the parent. This checks both sandbox flags defined by the frame and by the HTTP response. Bug: 1041376 Change-Id: I3c0b808ef9ec3ebefde40ec7609a36a1f5edaf6c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2607790Reviewed-by:
Camille Lamy <clamy@chromium.org> Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#840132}
-
dpapad authored
This is necessary so that up/down arrow keys trigger scrolling of the PDF document after exiting Presentation mode. Bug: 1148478 Change-Id: Ie64d1e3deb5763a43ef4dc7f094065992b5eb4c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2597770 Commit-Queue: dpapad <dpapad@chromium.org> Auto-Submit: dpapad <dpapad@chromium.org> Reviewed-by:
Daniel Hosseinian <dhoss@chromium.org> Cr-Commit-Position: refs/heads/master@{#840131}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/a46fbf8fc541..90b6613019de 2021-01-05 jacktfranklin@chromium.org Reland "Add header context menu to data grid" 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/+doc/master/autoroll/README.md Bug: chromium:1150793 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Ia2900946e70b59db31b33a14691368911cb41a16 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2606002Reviewed-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@{#840130}
-
Ben Mason authored
TBR=govind@chromium.org Change-Id: I925d2ffca8985c2f0177f9d0af63466c48cab0db Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2610686Reviewed-by:
Ben Mason <benmason@chromium.org> Commit-Queue: Ben Mason <benmason@chromium.org> Cr-Commit-Position: refs/heads/master@{#840129}
-
Mihai Sardarescu authored
It is not totally clear why the IdentityManager needs to update the account info for the primary account (the CoreAccountInfo is not expected to be updated when new user info is fetched by the AccountFetcherService). Nonetheless, it does not make much sense to only update this information for the sync account (the account info of the non sync account is fetched using the same logic the one for the sync account). This CL updates this information for the non-sync primary account as well. Bug: None Change-Id: Id67845cf4ee3cd3c5cd577f2d82341989d5d320e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2602417 Commit-Queue: Mihai Sardarescu <msarda@chromium.org> Reviewed-by:
Tanmoy Mollik <triploblastic@chromium.org> Cr-Commit-Position: refs/heads/master@{#840128}
-
Jan Krcal authored
This CL adds another bucket in the histogram for signed-in profile creation flow (and renames the local bucket accordingly). The CL also updates naming for other buckets to be up to date with the current terminology. Bug: 1126913 Change-Id: I6423a6a64a601869e04da4f42c55a577a534113f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2610598 Commit-Queue: Jan Krcal <jkrcal@chromium.org> Auto-Submit: Jan Krcal <jkrcal@chromium.org> Reviewed-by:
David Roger <droger@chromium.org> Cr-Commit-Position: refs/heads/master@{#840127}
-
Ramin Halavati authored
When ephemeral Guest profiles are enabled and a Guest browser is not opened, adds an option to sign-in intercept to open the new profile in a Guest browser. Screenshot: https://screenshot.googleplex.com/58aNLULBpJzdBa7.png Bug: 1157764 Change-Id: Ifdf5ec9f7050051e73b7989973790e96e0c03af5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587062 Commit-Queue: Ramin Halavati <rhalavati@chromium.org> Reviewed-by:
David Roger <droger@chromium.org> Cr-Commit-Position: refs/heads/master@{#840126}
-
Antonio Gomes authored
The way the logic is currently implemented prevents the delegate from being notified of state changes most of the time. This CL relaxes the sanity checks in WaylandToplevelWindow::HandleSurfaceConfigure(), causing DesktopWTHPlatform::OnWindowStateChanged() to get called more frequently, but holding now the correct state. This will allow DesktopWTHPlatform to react on state changes more reliably (eg lacros' immersive fullscreen behavior). Last, this CL changes the logic that sets and unsets fullscreen. Previously, UnSetFullscreen() was being called for all operations different than "enter fullscreen". This is needless and might mess compositors up. TEST=ozone_unittests adapted accordingly. BUG=1113900 R=msisov@igalia.com, nickdiego@igalia.com Change-Id: Iddffaf5d4f0e20898db0016320935904b9816e45 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2601219 Auto-Submit: Antonio Gomes <tonikitoo@igalia.com> Reviewed-by:
Maksim Sisov <msisov@igalia.com> Reviewed-by:
Nick Yamane <nickdiego@igalia.com> Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Cr-Commit-Position: refs/heads/master@{#840125}
-
Viktor Semeniuk authored
This features allows obtaining Change Password URLs from the Affiliation Service. Also UseOfHashAffiliationFetcher enables usage of Affiliation Service for non-synced uses. Bug: 1154587 Change-Id: Ieab7624bf99ab645d33096b691b191b87e6fb71f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567391 Commit-Queue: Viktor Semeniuk <vsemeniuk@google.com> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#840124}
-
chromium-autoroll authored
Roll Chrome Win32 PGO profile from chrome-win32-master-1609735837-0def2c604407494fb27ba623dbaed3c908ff2f3e.profdata to chrome-win32-master-1609821402-6004c61fe423c51f3b6973d79ebe11baae0b7161.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win32-chromium Please CC pgo-profile-sheriffs@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:win-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I3e57816d260ea45c394c4bf150a1a9627606c45e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2609874Reviewed-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@{#840123}
-
Vidhan Jain authored
This CL adds an input field for the honorific prefixes above the "Full Name" field, accessible from the Autofill Settings View. The field is visible only when the kAutofillEnableUIForHonorificPrefixesInSettings feature is enabled. The entered value will not be saved, because honorifics are temporarily disabled (crbug/1113617). Screenshot: https://storage.cloud.google.com/chromium-translation-screenshots/aa5e881149c5eb8c425711c2f3cabad33a45c35e?authuser=0 Bug: 1141884 Change-Id: I353d3b65b96e3960bbf950455da049e0292477a0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2594749Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Reviewed-by:
Viktor Semeniuk <vsemeniuk@google.com> Reviewed-by:
Olivier Robin <olivierrobin@chromium.org> Commit-Queue: Vidhan Jain <vidhanj@google.com> Cr-Commit-Position: refs/heads/master@{#840122}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/fc1733482433..84cad4eea312 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-mac-chromium 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 Tbr: perfetto-bugs@google.com Change-Id: I7ef126e8468aafb94e2ab87d7fd60270170dab9c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2610246Reviewed-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@{#840121}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/026a067c38ef..07dea8371353 2021-01-05 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Chromium from 094b96f7 to b5dfde1f (71 revisions) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC ianelliott@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: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-asan;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: ianelliott@google.com Change-Id: I445458201fa0b9fb0621a31ac8074ca3b9308b09 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2609872Reviewed-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@{#840120}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/84cad4eea312..bc804095bcad 2021-01-05 fmayer@google.com Merge "Move deobfuscate.h out of include." 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: None Tbr: perfetto-bugs@google.com Change-Id: Ib84ae7010a3226a03f031c84795b371687456b0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2606000Reviewed-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@{#840119}
-
Robbie Gibson authored
Bug: 1094335 Change-Id: I81d6af8ae338f1ca2ee792dd9cdc7aa153228a76 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2610094Reviewed-by:
Mark Cogan <marq@chromium.org> Commit-Queue: Robbie Gibson <rkgibson@google.com> Cr-Commit-Position: refs/heads/master@{#840118}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/fc1733482433..84cad4eea312 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-win-chromium 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 Tbr: perfetto-bugs@google.com Change-Id: I71363083228b6c60a80facdd61f7b630f84eb6ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2608641Reviewed-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@{#840117}
-
Rushan Suleymanov authored
Bug: 948661 Change-Id: Iee4c52a1523df9dfa36e4ef50cf3fa5dfd7ec4e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2607304Reviewed-by:
Victor Vianna (OOO 21/12-05/01) <victorvianna@google.com> Commit-Queue: Rushan Suleymanov <rushans@google.com> Cr-Commit-Position: refs/heads/master@{#840116}
-
Stepan Khapugin authored
On a device with a biometric sensor which is disabled, LAContext's biometryType will be set to the type of the sensor, even if it's not set up. Check the error instead to see when a fallback to Passcode is required. Fixed: 1161175 Change-Id: I3db27208e46cd6aa11cf802e90086c1c040dc330 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2601356 Commit-Queue: Stepan Khapugin <stkhapugin@chromium.org> Commit-Queue: Robbie Gibson <rkgibson@google.com> Auto-Submit: Stepan Khapugin <stkhapugin@chromium.org> Reviewed-by:
Robbie Gibson <rkgibson@google.com> Cr-Commit-Position: refs/heads/master@{#840115}
-
Findit authored
This reverts commit 29ff7965. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 840082 as the culprit for failures in the build cycles as shown on: https://analysis.chromium.org/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtLzI5ZmY3OTY1MmQ0YTRmMDIxNzc5ZjBlNGIyNDdkNTNiMjgxMDQzZGYM Sample Failed Build: https://ci.chromium.org/b/8858949956473740752 Sample Failed Step: ui_base_unittests Original change's description: > ime: Handle InsertTextCursorBehavior in InputMethodChromeOS. > > TextInputClients now support moving the cursor after committing some > text. This patch adds support for input engines to call the new API. > > There is a slight complication with multiple CommitText calls during > key event handling. Previously, when handling a key event, any calls > to CommitText will be coalesced together and executed once the key > event is handled. However, this coalescing logic doesn't handle > cursor movement. > > Add logic to handle cursor movement when coalescing commits by observing that > any sequence of CommitTexts with cursor movement can be implemented with two > separate CommitTexts. Note that this is a no-op change if the IME never uses > the new cursor movement parameter. > > Bug: 1155331 > Change-Id: I6c89ec1cde5624eca7bf0d5c803085f7d7803c71 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576067 > Reviewed-by: Keith Lee <keithlee@chromium.org> > Reviewed-by: Alice Boxhall <aboxhall@chromium.org> > Commit-Queue: Darren Shen <shend@chromium.org> > Cr-Commit-Position: refs/heads/master@{#840082} Change-Id: If06b84f85826520e8a65ebf908eba18ff7bd2428 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1155331 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2607068 Cr-Commit-Position: refs/heads/master@{#840114}
-
Tanmoy Mollik authored
This cl imports PrimaryAccountChangeEvent from c++ code to java code. Following cls will refactor IdentityManager.Observer.(onPrimaryAccountSet /Cleared) methods to onPrimaryAccountChanged method. That way signin code will be more consistent across all platforms. Bug: 1158855 Change-Id: I2c65e81a369540a9eadf85a9d1ba4c0c716853a0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2603747 Commit-Queue: Tanmoy Mollik <triploblastic@chromium.org> Reviewed-by:
Alice Wang <aliceywang@chromium.org> Reviewed-by:
Mihai Sardarescu <msarda@chromium.org> Cr-Commit-Position: refs/heads/master@{#840113}
-
Stepan Khapugin authored
Fixes the bug which was caused by a mistake in a refactoring. Add a test to prevent regression. Fixed: 1151035 Change-Id: I9f3d00cfdd13321dd289a9944e155c76bc8b6524 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2600821 Commit-Queue: Robbie Gibson <rkgibson@google.com> Reviewed-by:
Robbie Gibson <rkgibson@google.com> Auto-Submit: Stepan Khapugin <stkhapugin@chromium.org> Cr-Commit-Position: refs/heads/master@{#840112}
-
Alice Wang authored
This CL adds a set of JUnit tests for the class ProfileDownloader. Bug: 1161437 Change-Id: Iead7068b730b5ca6c62b7edb8bf893aa7457e60e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2607108 Commit-Queue: Alice Wang <aliceywang@chromium.org> Reviewed-by:
Tanmoy Mollik <triploblastic@chromium.org> Cr-Commit-Position: refs/heads/master@{#840111}
-
Stefan Zager authored
Instead, set contents_opaque directly on the cc::Layer. This makes it more straightforward to migrate the logic to PaintArtifactCompositor. Bug: 1069546 Change-Id: Ifa338b89bb2636b257b34e67e51c7a300c9e5754 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2607668 Commit-Queue: Stefan Zager <szager@chromium.org> Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#840110}
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1609735837-54f15795beeae1e22004c8135cf818a537813adc.profdata to chrome-win64-master-1609821402-aadb54447d521b648e35bdaecfd53290f25cbd03.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win64-chromium Please CC pgo-profile-sheriffs@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:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: Ibcbe9d799408b988b991977b25cca9783c1e591f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2608787Reviewed-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@{#840109}
-
Nancy Wang authored
Modify GetSessionIdForRestoreFromWebContents to return session id for all browsers, because we need to save the window stack (z-order) for all browser windows. Modify web apps, and extension apps publishers to save app launch information for system web apps, and platform apps, because the browser session restore can't restore them. For all other apps, no matter opened in tab, or window, the browser session restore can restore them, so we don't need to save the app launch information, we only save the browser session id as the window id, to restore the browser windows, including window stack (z-order), snap, etc. The app ids for apps opened with browsers are saved as the chrome browser's app id, because there could be multiple apps opened as tabs in one browser, and we only need to save one browser window for them. There will be separate CL to handle the chrome browser saving and restoration. BUG=1146900 Change-Id: I9f6d6675a7f7a39bd361f911d1c5cd22e898817e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2602038 Commit-Queue: Nancy Wang <nancylingwang@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#840108}
-
Alice Wang authored
This CL adds two render tests for account management view in child account mode when the sign-out option should be hidden. Bug: 1045525 Change-Id: I9e53396fe642c78eaa37dd04457cfcf72730109e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2597553Reviewed-by:
Tanmoy Mollik <triploblastic@chromium.org> Reviewed-by:
Victor Vianna (OOO 21/12-05/01) <victorvianna@google.com> Commit-Queue: Alice Wang <aliceywang@chromium.org> Cr-Commit-Position: refs/heads/master@{#840107}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/2949c359547c..e17fd0f0e9bd 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 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: Change-Id: Idbf727e2cf4e2a023b076ed72f8f8eb393e2ad80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2610631Reviewed-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@{#840106}
-
Alex Ilin authored
The profile customization bubble at the end of the sign-in flow allows the user to customize profile name and color. We show the bubble only if the user doesn't already have a synced theme color. We reuse the logic from ProfileCustomizationBubbleSyncController that is used for non-force sign-in profile creation flow. Bug: 1156096 Change-Id: Iae9d84e7f4ca5ca415058023e0b23b1260d96542 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2603297Reviewed-by:
David Roger <droger@chromium.org> Commit-Queue: Alex Ilin <alexilin@chromium.org> Cr-Commit-Position: refs/heads/master@{#840105}
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC chrome-fuchsia-gardener@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-deterministic-dbg;luci.chromium.try:fuchsia-x64-cast Tbr: chrome-fuchsia-gardener@grotations.appspotmail.com Change-Id: Id04cf297760f30a961d72c30be40bf92c32c6cfc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2610617Reviewed-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@{#840104}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/d00a5cd12448..a46fbf8fc541 2021-01-05 patrick.brosset@microsoft.com Set expander icon size in pixels 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/+doc/master/autoroll/README.md Bug: chromium:1161662 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Iebb8acaa6bf34df7c72cd6f4e919d207f4c07db2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2609873Reviewed-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@{#840103}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/76bebd29..53386e30 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,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: Idc64c5434ca885a4bf09b38acf97c0c5f2096839 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2608639Reviewed-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@{#840102}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/fc1733482433..84cad4eea312 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-linux-chromium 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 Tbr: perfetto-bugs@google.com Change-Id: I2b97965af15e150026283b1ae66a2126472c28f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2608640Reviewed-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@{#840101}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/92d8ee9b37c0..b54debc350a1 2021-01-05 webrtc-version-updater@webrtc-ci.iam.gserviceaccount.com Update WebRTC code version (2021-01-05T04:04:14). 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: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I6ba5351b03aa612adb6daf13bd135a77a8b90575 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2610616Reviewed-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@{#840100}
-
Peter Marshall authored
Bug: 1046784 Change-Id: Ic0cb2266159d5f6395130555a736fdff1846c26c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2610597 Commit-Queue: Peter Marshall <petermarshall@chromium.org> Commit-Queue: Mathias Bynens <mathias@chromium.org> Auto-Submit: Peter Marshall <petermarshall@chromium.org> Reviewed-by:
Mathias Bynens <mathias@chromium.org> Cr-Commit-Position: refs/heads/master@{#840099}
-
Alex Ilin authored
With the profile picker experiment, the user might get a color theme even if they never interacted with the color picker. This CL adds a new "ChromeColors.ColorApplied" histogram that shows how often users interact with the color picker. Bug: 1063856 Change-Id: I2973199fddf57bedf283bb70f69597ea836d24b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2593126Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Monica Basta <msalama@chromium.org> Reviewed-by:
Tibor Goldschwendt <tiborg@chromium.org> Reviewed-by:
Jan Krcal <jkrcal@chromium.org> Commit-Queue: Alex Ilin <alexilin@chromium.org> Cr-Commit-Position: refs/heads/master@{#840098}
-