- 12 Dec, 2020 40 commits
-
-
chromium-autoroll authored
Roll Chrome Linux PGO profile from chrome-linux-master-1607731149-f9d7b6048f47267213c698b8417226050a69f328.profdata to chrome-linux-master-1607751393-88c173fab32a5214599c68d68d23f85ae6956316.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-linux-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:linux-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I1b00c4faff4f89f086b1f05759ecedd229d5a238 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2588035Reviewed-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@{#836419}
-
Xianzhu Wang authored
Previously we only invalidated the view scrollbars on document color theme change, missing scroll corners, and scrollbars for inner scrollers. Now invalidate overflow controls when ComputedStyle::UsedColorScheme() changes for scrollable areas. Bug: 929098 Change-Id: I2e2574bd49058b4c6261acbecad889af22c3f30d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2586017 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#836418}
-
Rakina Zata Amni authored
Currently it's possible for an error page and a non-error page to have the same document sequence number in their FrameNavigationEntries, if the error page is a result of loading an entry that was previously added by the history API. When we are doing a history navigation from an error page to another entry with the same DSN, we should treat the navigation as a cross-document navigation, to trigger load of a new document instead of staying in the same error page and possibly removing FNEs incorrectly. See linked bug for more details. Bug: 1155478 Change-Id: I2bd7df075d8bdd6c65506a66b45ee2a17c8ba52f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2581659 Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Reviewed-by:
danakj <danakj@chromium.org> Reviewed-by:
Charlie Reis <creis@chromium.org> Cr-Commit-Position: refs/heads/master@{#836417}
-
Chris Harrelson authored
Previously, a negative delta was added to additional_offset_to_layout_shift_root_delta to account for a paint offset translation transform on an object from the prior frame, which is meant to be added to the new paint offset translation and result in a delta. However, this negative delta was added to the containing block context, which is incorrect in cases when the current object is not a containing block for some descendants, such as nested fixed-position elements (there are other cases as well). Instead, store off the negative delta and apply it to the fragment context once it has been updated for the current object. Bug: 1141739 Change-Id: Ic667aff457be0a192de7f92a424996bcded47b10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2586969Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#836416}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/62801b737bc0..9f79ef51ecc2 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: Ifd9406d62dd1803720bfe7dbeecab42779a86a0b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2588029Reviewed-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@{#836415}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/dc599083..e7e9e702 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: I14d69e9faced29417b205ee95f7d6e3cb3fab82c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587956Reviewed-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@{#836414}
-
Domenic Denicola authored
This CL renames the Origin-Isolation header to Origin-Agent-Cluster, and the window.originIsolated getter to window.originAgentCluster, following https://github.com/whatwg/html/pull/6214. See Intent to Ship update at https://groups.google.com/a/chromium.org/g/blink-dev/c/WW4fGjvroWI/m/bwxj0iiYAgAJ This only does the minimal renames necessary to update web-facing semantics, and then the minimal modifications to the tests to get them passing again. Future CLs on top of this one should: * Update all code references (e.g. function and member names) to stop saying "origin isolation". * Update all test titles, comments, etc. * Move the tests to a new directory. Bug: 1157917 Change-Id: I1f95eb3d5298a6dfae3d3bda4a79343e8287d4f6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587369 Commit-Queue: Domenic Denicola <domenic@chromium.org> Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#836413}
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1607698715-e13d73f1fde8c8ea06b6de4bb97b90c11d1836bd.profdata to chrome-win64-master-1607720385-e19ad0a61b8b448bc3fbfd6deeb23cbce38e7b44.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: Ie8979356554baba8657beaa467c62177429b3072 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587830Reviewed-by:
-
Gyuyoung Kim authored
This CL migrates AwViewMsg_SmoothScroll to LocalMainFrame interface. Bug: 1157126 Change-Id: I6f179fa63bb0effffb3518b4bf2ed731cd763cf3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583591 Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com> Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#836411}
-
Chromium WPT Sync authored
Using wpt-import in Chromium d3db5e45. With Chromium commits locally applied on WPT: ced49c96 "[AspectRatio] Correctly handle abspos replaced elements with aspect-ratio" Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md NOAUTOREVERT=true TBR=lpz@google.com No-Export: true Cq-Include-Trybots: luci.chromium.try:linux-wpt-identity-fyi-rel,linux-wpt-input-fyi-rel Change-Id: I051e05114ec288342d491108006d39b855941e88 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2586855Reviewed-by:
WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#836410}
-
Gyuyoung Kim authored
This CL migrates AwViewMsg_SetInitialPageScale to LocalMainFrame interface. Bug: 1157124 Change-Id: I2750606e2dfa56d2b0fa2e710510d23333f17304 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583668 Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com> Reviewed-by:
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/74ccf7b62fc6..778b2c216924 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: Ia9e2dd4ecba570b517a7955c4e1c05cf9e0cfa2f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587969Reviewed-by:
-
Jeffrey Kardatzke authored
This enables HEVC as a supported media format if the ENABLE_PLATFORM_HEVC flag is on and we have enabled clear HEVC for testing. This also enables the bitstream conversion in the Chrome OS decoder pipeline. Another CL enables HEVC for the encrypted path. BUG=b:153111783,chromium:1141237 TEST=Clear HEVC playback works w/ cmd line flag Change-Id: I27892296cec353d442178dc8e43f975921e8c036 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568210Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Chrome Cunningham <chcunningham@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Jeffrey Kardatzke <jkardatzke@google.com> Cr-Commit-Position: refs/heads/master@{#836407}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/8093cb08ef89..62801b737bc0 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: I9d7ee243c939a1a5e44cb16edba47383d399b122 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587767Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/8326b26a790f..4fb29e83e02c 2020-12-11 jdarpinian@chromium.org Ignore mac .DS_Store files 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 syoussefi@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: syoussefi@google.com Change-Id: I9d64025d5d2e40806305ca9b3d8443c4e52549b2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587765Reviewed-by:
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/346dd53ac087..1aa1f5fcbac6 2020-12-11 bsalomon@google.com whole-word replace renderTargetContext with surfaceDrawContext If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC jmbetancourt@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-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Cq-Do-Not-Cancel-Tryjobs: true Bug: None Tbr: jmbetancourt@google.com Change-Id: Ic8d40e1f113a5ae982021d481606d888591a081d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587970Reviewed-by:
-
yiyix authored
In the initial implementation, if createImageData(ImageData) is called, image will be convert to image data using the image setting of the canvas. I updated the default behavior to use the original color setting from the imageData. Bug:1118182 Change-Id: I8ed5932faa1678969825a958852b309492b52c1c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2582891Reviewed-by:
ccameron <ccameron@chromium.org> Commit-Queue: Yi Xu <yiyix@chromium.org> Cr-Commit-Position: refs/heads/master@{#836403}
-
Toni Barzic authored
HoldingSpaceImage's image source has a pointer to the HoldingSpaceImage, so it can notify it that new image representation has been loaded. Image source is owned by the image itself, and may outlive the associated HoldingSpaceItem, which owns HoldingSpaceImage. If the thumbnail generation for the item finishes after the item has been destroyed, the holding space image source may attempt to access the HoldingSpaceImage object after destruction. To fix this, pass a weak pointer to HoldingSpaceImage source, so it can verify the HoldingSpaceImage is still around before notifying it that the image has changed. HoldingSpcareTrayIconPreview contents image had a similar issue where it was getting the item image from the item ptr. This was done in GetImageForScale, which may get called as long as the associated image skia is around, which doesn't guarantee that the item has not already been deleted - instead, have the contents image use the image skia directly. BUG=1156776 Change-Id: I6e6c6d14ed5a25739e8b4366225f29dfa8706c8e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587655Reviewed-by:
David Black <dmblack@google.com> Commit-Queue: Toni Baržić <tbarzic@chromium.org> Cr-Commit-Position: refs/heads/master@{#836402}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/ed883bc1d977..9c52c2997c81 2020-12-12 bajones@chromium.org Updating BindGroupLayoutEntry interface to match latest spec 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 rharrison@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: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: rharrison@google.com Change-Id: I48b50f5e48c699edd8cd8fc66659b1349e21b7ed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587827Reviewed-by:
-
David Black authored
When deleting holding space item views (such as occurs when unpinning) the ink drop layers for the view can attempt to be reordered on the parent which causes a crash. This is most easily reproducible by trying to unpin the last pinned file in the pinned files section. Note that the solution reparents ink drop layers to be within the holding space item view hierarchy which also addresses an issue where ink drop layers did not animate in/out with the layer for animating holding space item view. Bug: 1157280 Change-Id: I4d7daf831e46d3bdd7bf049b49e15b53319cc2c0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587519 Commit-Queue: David Black <dmblack@google.com> Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Cr-Commit-Position: refs/heads/master@{#836400}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=lakpamarthy@chromium.org Change-Id: Icb12e5ec1139faa46d3f0140db1e8757f8e71766 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587009Reviewed-by:
Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#836399}
-
Brian Sheedy authored
Adds the .textpb for running an Android emulator with SDK 27/Android O. Bug: 1145728 Change-Id: I0cff8181bff2dc5174b8efcf11c82c2babd137d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587609 Auto-Submit: Brian Sheedy <bsheedy@chromium.org> Commit-Queue: Haiyang Pan <hypan@google.com> Reviewed-by:
Haiyang Pan <hypan@google.com> Cr-Commit-Position: refs/heads/master@{#836398}
-
Yuheng Huang authored
Create this story to track scroll performance when loading. Also fix change measure frame time by using benchmark_value. Bug: 1099917 Change-Id: Ic7b53226fdf189171ffb001db5a45ff05501582d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2586517Reviewed-by:
John Chen <johnchen@chromium.org> Reviewed-by:
Thomas Lukaszewicz <tluk@chromium.org> Commit-Queue: Yuheng Huang <yuhengh@chromium.org> Cr-Commit-Position: refs/heads/master@{#836397}
-
Khushal authored
R=bsalomon@google.com Change-Id: I72615b36891e9e5ee568a8332bf0b6344b8188da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2545684 Commit-Queue: Khushal <khushalsagar@chromium.org> Reviewed-by:
Brian Salomon <bsalomon@google.com> Cr-Commit-Position: refs/heads/master@{#836396}
-
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-aemu-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 Tbr: chrome-fuchsia-gardener@grotations.appspotmail.com Change-Id: I45540b59015197932e32719f58284f3153470d52 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587585Reviewed-by:
-
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: I6db944ffd01e9008b0c56eace8831a166511a357 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587589Reviewed-by:
-
Julie Jeongeun Kim authored
Previously RendererStartupHelper::GetRenderer() returns mojom::Renderer* having DCHECK that makes sure the map includes it. But, GetRenderer() would be accessed before the map is updated. This CL returns nullptr from RendererStartupHelper::GetRenderer() when |process_mojo_map_| doesn't have the information corresponding to the process. Bug: 1157200 Change-Id: Ifacc4cfcd9457716d7eca700b7df4be8576f68b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583663 Commit-Queue: Julie Kim <jkim@igalia.com> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#836393}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/da7e8b6d..dc599083 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: I4afc136c2ff5f3fd63c8b1b7854d44aec923d887 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587702Reviewed-by:
-
Gyuyoung Kim authored
This CL migrates AwViewMsg_ResetScrollAndScaleState to LocalMainFrame interface. Bug: 1157122 Change-Id: I353739146052f471d2f45bbfd7b0d579cd2f0772 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583588 Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com> Reviewed-by:
-
Mitsuru Oshima authored
Bug: 1157664 Test: Coverd by unittests Change-Id: Id2c676779101f10e046ad4b8d168317316fd9db8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587610 Commit-Queue: Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#836390}
-
Mario Sanchez Prada authored
This reverts commit a1caa660. Reason for revert: It seems that the migration of RequestPause is causing some crashes, along with some flakiness in quite a few tests (see bugs 1157572, 1157779, 1157263, 1157241 and 1157239), so let's revert this patch for now. Original change's description: > Migrate MediaPlayerDelegateMsg_Request{Play,Pause} to mojo > > This migrates these legacy IPC messages to the media.mojom.MediaPlayer > mojo interface, now implemented by HTMLMediaElement inside of Blink, > and updates its callers in the browser process. > > Relevant design document: > https://docs.google.com/document/d/1OLMNxLvGkRO6ju_WfHbRMrgaVnW7bsMnW7XlJQI0A2E > > Bug: 1039252 > Change-Id: Ia4c873402179fb3eb918a3bc077b19842026ce21 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2543025 > Commit-Queue: Mario Sanchez Prada <mario@igalia.com> > Reviewed-by: Chrome Cunningham <chcunningham@chromium.org> > Reviewed-by: Mounir Lamouri <mlamouri@chromium.org> > Reviewed-by: Becca Hughes <beccahughes@chromium.org> > Reviewed-by: Kentaro Hara <haraken@chromium.org> > Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> > Cr-Commit-Position: refs/heads/master@{#835304} TBR=kinuko@chromium.org,haraken@chromium.org,mlamouri@chromium.org,chcunningham@chromium.org,beccahughes@chromium.org,mario@igalia.com,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1039252 Change-Id: I2fe99c76d5d35be344d9578d489292d2cf4ab9a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2586350Reviewed-by:
Mario Sanchez Prada <mario@igalia.com> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Commit-Queue: Mario Sanchez Prada <mario@igalia.com> Cr-Commit-Position: refs/heads/master@{#836389}
-
Yi Gu authored
[CodeHealth] Convert chrome/browser/supervised_user/ from base::Bind and base::Callback to Once/Repeating Bug: 1152281 Change-Id: I51b6bf363ac5cbbefa1e602a1a6b1245350d1d7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587349Reviewed-by:
Dan S <danan@chromium.org> Commit-Queue: Yi Gu <yigu@chromium.org> Cr-Commit-Position: refs/heads/master@{#836388}
-
Erik Chen authored
Previously, protocol errors would result in graceful termination of this browser. This would visibly appear like a crash to users but no crash report would be generated. Bug: 1151480 Change-Id: I76209bd5b57471f6fc8e435027f1be286894c991 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2586194 Commit-Queue: Erik Chen <erikchen@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#836387}
-
Alex Moshchuk authored
This reverts commit 7ffd10d3. Reason for revert: [Sheriff] Suspected to be causing widespread accessibility test failures on MSAN bots due to use of uninitialized value in code that was added to CreateOrUpdateLayer in this CL (line 73, presumably for `stack_at_top`) Build: https://ci.chromium.org/p/chromium/builders/ci/Linux%20ChromiumOS%20MSan%20Tests/21677 Sample failure: [ RUN ] AccessibilityFocusRingControllerTest.FocusRingWorksOnMultipleDisplays 2020-12-11T22:10:55.266324Z 8322331852 ERROR ash_unittests[24691:24691]: [cras_audio_handler.cc(1611)] Failed to retrieve WBS mic deprioritized flag ==24691==WARNING: MemorySanitizer: use-of-uninitialized-value #0 0x5653d294dffa in ash::AccessibilityLayer::CreateOrUpdateLayer(aura::Window*, char const*, gfx::Rect const&, bool) ./../../ash/accessibility/accessibility_layer.cc:73:7 #1 0x5653d294788e in ash::AccessibilityFocusRingLayer::Set(ash::AccessibilityFocusRing const&) ./../../ash/accessibility/accessibility_focus_ring_layer.cc:116:3 #2 0x5653d29383cb in ash::AccessibilityFocusRingGroup::UpdateFocusRingsFromInfo(ash::AccessibilityLayerDelegate*) ./../../ash/accessibility/accessibility_focus_ring_group.cc:82:25 #3 0x5653d293baa9 in ash::AccessibilityFocusRingGroup::UpdateFocusRing(std::__1::unique_ptr<ash::AccessibilityFocusRingInfo, std::__1::default_delete<ash::AccessibilityFocusRingInfo> >, ash::AccessibilityLayerDelegate*) ./../../ash/accessibility/accessibility_focus_ring_group.cc:152:3 #4 0x5653d2932f04 in ash::AccessibilityFocusRingControllerImpl::SetFocusRing(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::unique_ptr<ash::AccessibilityFocusRingInfo, std::__1::default_delete<ash::AccessibilityFocusRingInfo> >) ./../../ash/accessibility/accessibility_focus_ring_controller_impl.cc:67:25 #5 0x5653cda0dbe2 in ash::AccessibilityFocusRingControllerTest_FocusRingWorksOnMultipleDisplays_Test::TestBody() ./../../ash/accessibility/accessibility_focus_ring_controller_unittest.cc:106:15 #6 0x5653d24cc4a7 in HandleExceptionsInMethodIfSupported<testing::Test, void> ./../../third_party/googletest/src/googletest/src/gtest.cc:0:0 #7 0x5653d24cc4a7 in testing::Test::Run() ./../../third_party/googletest/src/googletest/src/gtest.cc:2689:5 #8 0x5653d24ceb57 in testing::TestInfo::Run() ./../../third_party/googletest/src/googletest/src/gtest.cc:2866:11 #9 0x5653d24d0e64 in testing::TestSuite::Run() ./../../third_party/googletest/src/googletest/src/gtest.cc:3020:28 #10 0x5653d24fb28a in testing::internal::UnitTestImpl::RunAllTests() ./../../third_party/googletest/src/googletest/src/gtest.cc:5730:44 #11 0x5653d24fa26c in HandleExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool> ./../../third_party/googletest/src/googletest/src/gtest-internal-inl.h:0:10 #12 0x5653d24fa26c in testing::UnitTest::Run() ./../../third_party/googletest/src/googletest/src/gtest.cc:5313:10 #13 0x5653d3c13224 in RUN_ALL_TESTS ./../../third_party/googletest/src/googletest/include/gtest/gtest.h:2485:46 #14 0x5653d3c13224 in base::TestSuite::Run() ./../../base/test/test_suite.cc:480:16 #15 0x5653d3c1addf in Run ./../../base/callback.h:101:12 #16 0x5653d3c1addf in base::(anonymous namespace)::LaunchUnitTestsInternal(base::OnceCallback<int ()>, unsigned long, int, unsigned long, bool, base::OnceCallback<void ()>) ./../../base/test/launcher/unit_test_launcher.cc:179:38 #17 0x5653d3c1a853 in base::LaunchUnitTests(int, char**, base::OnceCallback<int ()>, unsigned long) ./../../base/test/launcher/unit_test_launcher.cc:249:10 #18 0x5653cf8bc976 in main ./../../ash/test/ash_unittests.cc:25:10 #19 0x7fe4936dd83f in __libc_start_main ??:0:0 #20 0x5653cd7f7409 in _start ??:0:0 Uninitialized value was created by a heap allocation #0 0x5653cd86a7c9 in operator new(unsigned long) /b/s/w/ir/cache/builder/src/third_party/llvm/compiler-rt/lib/msan/msan_new_delete.cpp:45:35 #1 0x5653d2938051 in make_unique<ash::AccessibilityFocusRingLayer, ash::AccessibilityLayerDelegate *&> ./../../buildtools/third_party/libc++/trunk/include/memory:3043:28 #2 0x5653d2938051 in ash::AccessibilityFocusRingGroup::UpdateFocusRingsFromInfo(ash::AccessibilityLayerDelegate*) ./../../ash/accessibility/accessibility_focus_ring_group.cc:69:11 #3 0x5653d293baa9 in ash::AccessibilityFocusRingGroup::UpdateFocusRing(std::__1::unique_ptr<ash::AccessibilityFocusRingInfo, std::__1::default_delete<ash::AccessibilityFocusRingInfo> >, ash::AccessibilityLayerDelegate*) ./../../ash/accessibility/accessibility_focus_ring_group.cc:152:3 #4 0x5653d2932f04 in ash::AccessibilityFocusRingControllerImpl::SetFocusRing(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::unique_ptr<ash::AccessibilityFocusRingInfo, std::__1::default_delete<ash::AccessibilityFocusRingInfo> >) ./../../ash/accessibility/accessibility_focus_ring_controller_impl.cc:67:25 #5 0x5653cda0dbe2 in ash::AccessibilityFocusRingControllerTest_FocusRingWorksOnMultipleDisplays_Test::TestBody() ./../../ash/accessibility/accessibility_focus_ring_controller_unittest.cc:106:15 #6 0x5653d24cc4a7 in HandleExceptionsInMethodIfSupported<testing::Test, void> ./../../third_party/googletest/src/googletest/src/gtest.cc:0:0 #7 0x5653d24cc4a7 in testing::Test::Run() ./../../third_party/googletest/src/googletest/src/gtest.cc:2689:5 #8 0x5653d24ceb57 in testing::TestInfo::Run() ./../../third_party/googletest/src/googletest/src/gtest.cc:2866:11 #9 0x5653d24d0e64 in testing::TestSuite::Run() ./../../third_party/googletest/src/googletest/src/gtest.cc:3020:28 #10 0x5653d24fb28a in testing::internal::UnitTestImpl::RunAllTests() ./../../third_party/googletest/src/googletest/src/gtest.cc:5730:44 #11 0x5653d24fa26c in HandleExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool> ./../../third_party/googletest/src/googletest/src/gtest-internal-inl.h:0:10 #12 0x5653d24fa26c in testing::UnitTest::Run() ./../../third_party/googletest/src/googletest/src/gtest.cc:5313:10 #13 0x5653d3c13224 in RUN_ALL_TESTS ./../../third_party/googletest/src/googletest/include/gtest/gtest.h:2485:46 #14 0x5653d3c13224 in base::TestSuite::Run() ./../../base/test/test_suite.cc:480:16 #15 0x5653d3c1addf in Run ./../../base/callback.h:101:12 #16 0x5653d3c1addf in base::(anonymous namespace)::LaunchUnitTestsInternal(base::OnceCallback<int ()>, unsigned long, int, unsigned long, bool, base::OnceCallback<void ()>) ./../../base/test/launcher/unit_test_launcher.cc:179:38 #17 0x5653d3c1a853 in base::LaunchUnitTests(int, char**, base::OnceCallback<int ()>, unsigned long) ./../../base/test/launcher/unit_test_launcher.cc:249:10 #18 0x5653cf8bc976 in main ./../../ash/test/ash_unittests.cc:25:10 #19 0x7fe4936dd83f in __libc_start_main ??:0:0 SUMMARY: MemorySanitizer: use-of-uninitialized-value (/b/s/w/ir/out/Release/ash_unittests+0x65feffa) Original change's description: > Re-land: Move focus rings and highlight layers under accessibility bubbles. > > Original patch: http://crrev.com/c/2568547 > Revert: http://crrev.com/c/2583106 > > Fix for issue where focus ring appears below switch access panel. Now clients can specify if they want their focus ring to appear above or below accessibility bubble panels. STS will specify they appear below, though other clients will (by default) specify they appear above all panels. This fixes an issue with the switch access focus ring didn't appear above the switch access panel. > > Original description: > > Move focus rings and highlight layers under accessibility bubbles. > > Will allow Select-to-speak panel UI to appear above focus ring and highlight layers. This also avoids the need to create more window containers. > > Bug: 1157261, 1143814 > Change-Id: Ibd8dd577ecd4fb5767b628c2eff679a2f6931b9c > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2582997 > Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org> > Reviewed-by: Xiyuan Xia <xiyuan@chromium.org> > Commit-Queue: Joel Riley <joelriley@google.com> > Cr-Commit-Position: refs/heads/master@{#836222} TBR=xiyuan@chromium.org,dmazzoni@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com,shannc@google.com,joelriley@google.com Change-Id: I08b819849d13fb5d01f67c5bbd3083ed0e445e7e No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1157261 Bug: 1143814 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587604Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Commit-Queue: Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#836386}
-
Daniel Cheng authored
Followup CLs will change how speculative RFH is cleaned up by relying on the fact that provisional frames are now owned by the frame they will replace in the renderer. Add tests to ensure nothing breaks in those followups. Bug: 838348 Change-Id: I66d34aa8ce1d5b2d65468c63c6629e58243080c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2586525 Commit-Queue: Charlie Reis <creis@chromium.org> Auto-Submit: Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Aaron Colwell <acolwell@chromium.org> Cr-Commit-Position: refs/heads/master@{#836385}
-
Alex Moshchuk authored
Bug: 626703 Change-Id: I9c165aeae54f54cc6a1c1d1a97e43f7ef5f02531 Notry: true Tbr: robertma@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587973Reviewed-by:
-
Kyle Horimoto authored
This CL fixes an issue which re-shows notifications which have already been shown to the user after the user has (1) suspended their device, (2) locked their device, or (3) turned Bluetooth off. When these situations occur, we silently add the notification to the notification shade but do not pop it up. This fixes an issue which caused notifications to appear spammy when we'd show them multiple times. Bug: 1157523, 1106937 Change-Id: I58efe0d96f226a75e07a137e22081637ebb524a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587700Reviewed-by:
Jimmy Gong <jimmyxgong@chromium.org> Commit-Queue: Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#836383}
-
Kyle Horimoto authored
Before this CL, we would show the "connecting" UI when we were waiting for a pending host to be set. This was misleading, since we were not actually connecting at all. Even worse, we'd show this UI when the user had accidentally picked the wrong device in the drop-down menu, perhaps due to crbug/923594. This CL updates Phone Hub so that it does not show any UI when we're in this state. Once the phone is actually set up, then we show the "connecting" UI. Bug: 1157971, 1106937 Change-Id: I3cc896335b436849e05a8bc2d6b0adbbdc8edfb2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587563Reviewed-by:
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1607709601-c889cff9228ed2a408f7c416b610f665b13ded19.profdata to chrome-mac-master-1607731149-2a55b7cdbe080700f7cc337cacf74a6b6e2cffc4.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-mac-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:mac-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I76059014b42d07a9dc9cd6672ca6c633c17d9afc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587762Reviewed-by:
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/82e0d524143f..346dd53ac087 2020-12-11 ethannicholas@google.com Reland "Reland "Reland "Revert "Initial land of SkSL DSL."""" 2020-12-11 kjlubick@google.com [canvaskit] Remove filterquality on paint. 2020-12-11 bsalomon@google.com Revert "Add new SkCanvas methods for Android Framework WebView queries." 2020-12-11 brianosman@google.com SkSLSlide: Add shadertoy iResolution & iMouse 2020-12-11 egdaniel@google.com Store command buffer usages to GrSurface's on GrVkCommandBuffer. 2020-12-11 jvanverth@google.com Increase QuadEdge precision on all platforms 2020-12-11 brianosman@google.com SkSLSlide: Add geometry options If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC jmbetancourt@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-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Cq-Do-Not-Cancel-Tryjobs: true Bug: None Tbr: jmbetancourt@google.com Change-Id: I9af1bfab027e2fe37776ea7680f665060e8945ac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587595Reviewed-by:
-
