- 06 Nov, 2020 40 commits
-
-
Fredrik Söderqvist authored
Also make sure dynamic changes are reflected earlier by calling AnimationAttributeChanged() when the parsed attribute value changes. Previously it would only refresh when moving to the next value range, or otherwise invalidating animation state. Fixed: 1145548 Change-Id: I8ff82c02e6bf8e3cb82ef4d21e2381cbc99bcd3e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2520783 Commit-Queue: Fredrik Söderquist <fs@opera.com> Reviewed-by:
Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#824818}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/e9554189c71b..eb8e1e991bc9 2020-11-06 petermueller@chromium.org Increase contrast of pseudo-element syntax color 2020-11-06 szuend@chromium.org [markdown] Remove MarkdownView bridge 2020-11-06 wolfi@chromium.org Fix event propagation for link from FrameDetails to Network request 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:1145525 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I3b806aa24c74374b8934a0e8dcdf6d2a6dc51ad0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521205Reviewed-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@{#824817}
-
Irem Uğuz authored
This CL moves CertProvisioningSchedulerUserServiceFactory to chromeos::EnsureBrowserContextKeyedServiceFactoriesBuilt() which is meant to initialize browser context keyed service factories for chrome on chromeos. Bug: 1142449 Change-Id: I494ec23d1f3357912ae1b43a0c76ee3fa4eb06b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2517560Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
David Roger <droger@chromium.org> Reviewed-by:
Omar Morsi <omorsi@google.com> Commit-Queue: Irem Uğuz <iremuguz@google.com> Cr-Commit-Position: refs/heads/master@{#824816}
-
Sylvain Defresne authored
When building for the "catalyst" environment, the selector -viewController is overloaded and the compiler is confused about the type of the value that is returned (as it can be either `UIViewController` or `NSViewController`). Add an explicitly checked cast to fix the compiler error about incompatible value type being stored in the array. Bug: 1138425 Change-Id: Ib5381993520bd1c2723439c6ad04c04d4d07f8e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521732 Commit-Queue: Sylvain Defresne <sdefresne@chromium.org> Commit-Queue: Gauthier Ambard <gambard@chromium.org> Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#824815}
-
Henrik Boström authored
Pixel buffers originating from a CVPixelBufferPool are recycled when no longer in use, previously only tested by releasing the last pixel buffer reference and not touching the IOSurface. This CL tests what happens when we are retaining not references to the pixel buffer, but references to a pixel buffer's IOSurface or incrementing its use count. Outcome: - Retaining references (base::ScopedCFTypeRef<IOSurfaceRef>) to an IOSurface does NOT prevent recycling. - Retaining use count (IOSurfaceIncrementUseCount) to an IOSurface DOES prevent recycling. This behavior is now documented in pixel_buffer_pool_mac.h. Bug: chromium:1132299 Change-Id: Ibdcd3752a4467bc495eba4b543ecd73da1b2f41f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2520829 Commit-Queue: Markus Handell <handellm@google.com> Reviewed-by:
Markus Handell <handellm@google.com> Cr-Commit-Position: refs/heads/master@{#824814}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/3dfaeeb00271..dc515d41bba9 2020-11-06 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Chromium from 3c7580ad to 52d33a46 (441 revisions) 2020-11-06 lexa.knyazev@gmail.com Metal: Fix typo in TextureMtl::bindToShader 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 courtneygo@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: courtneygo@google.com Change-Id: I30ef867a463bd59f13045a42a197b0833d2d7334 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522620Reviewed-by:
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/2b6b0f45ff05..973d145df865 2020-11-06 cwallez@chromium.org Make dawn_platform a component. 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/+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: cwallez@google.com Change-Id: I2c1e7bcf2cf22a34f7d3fa8b24d25b180995803b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523091Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/b8b4d61dd32f..a61d347b99c9 2020-11-06 landrey@webrtc.org Add logging about inserting diagnostics If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/catapult-autoroll Please CC skyostil@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:chromeos-kevin-rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: chromium:1146040 Tbr: skyostil@google.com Change-Id: Ic0cd8321c1f630fa86c61ec33612481a3e3fec7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523021Reviewed-by:
-
Renjie Tang authored
All the code under this directory has been converted to using modern callbacks. Bug: 1007792 Change-Id: Ide911f55b785201c3327658a0b2c191392b6e649 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521970 Auto-Submit: Renjie Tang <renjietang@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#824810}
-
Devlin Cronin authored
It's only used in a single method. Just make it a function-local. Bug: None Change-Id: I0ebcc1f9a6ff8d724490e2e41aa7c4fe35096f86 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2518196 Auto-Submit: Devlin <rdevlin.cronin@chromium.org> Commit-Queue: Karan Bhatia <karandeepb@chromium.org> Reviewed-by:
Karan Bhatia <karandeepb@chromium.org> Cr-Commit-Position: refs/heads/master@{#824809}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/abc1b79a1564..41bb19c60930 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: Ife96b3fd197f0dda10db78ad40757f5c96b0d618 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523014Reviewed-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@{#824808}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/8b665312ca15..0891c367b8b2 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: I3268aab08638f3aafe9bd93734c83d7d4c95e281 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522884Reviewed-by:
-
Mathias Carlen authored
Add a TabHelper feature to the list Autofill Assistant features. This feature is about restructuring ownership lifecycle relationships in the Autofill Assistant stack. Bug: b/169389571 Change-Id: Ic59d239adf25cad574b075d4f6aba616af4ae972 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521146Reviewed-by:
Sandro Maggi <sandromaggi@google.com> Commit-Queue: Mathias Carlen <mcarlen@chromium.org> Cr-Commit-Position: refs/heads/master@{#824806}
-
Gauthier Ambard authored
This CL makes sure that the WebView is no longer in the view hierarchy when the quicklook screen for AR is presented. When the WKWebView is added/removed from the view hierarchy, the visibilitychange event is fired. Bug: 1132085 Change-Id: I4043a4d3e5e24dc52aa467a82c7a62e78dd8a492 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2463567Reviewed-by:
Ali Juma <ajuma@chromium.org> Reviewed-by:
Justin Cohen <justincohen@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Commit-Queue: Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#824805}
-
Javier Fernandez authored
As per Unicode UAX#9 L1.4, line trailing whitespaces should always have the direction of the paragraph no matter the direction they had before line breaking. To accomplish that, in inline layout algorithm CreateLine, when an NGInlineItemResult is only trailing spaces, we ignore the bidi level coming from the NGInlineItem, and just use the base direction of the line. This should fix the case of an LTR line with trailing space and pre-wrap in an RTL line that would end up putting the trailing space to the right of the last LTR line instead of to the left of the line. This fixes css/css-text/white-space/eol-spaces-bidi-002.html with width of 7 characters. It is still not fixing the case for 8 characters. Bug: 316409, 1142926 Change-Id: Iab220f79ba0b2526fd51d5341363cc8e9087e133 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505486 Commit-Queue: José Dapena Paz <jdapena@igalia.com> Reviewed-by:
Javier Fernandez <jfernandez@igalia.com> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#824804}
-
Egor Pasko authored
The useSharedRelros() was renamed into provideSharedRelros(). Update stale comments to match the new name. No functional changes. Bug: None Change-Id: I278f1eccc650a24957a28825ffe4b107bda74577 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521176Reviewed-by:
Benoit L <lizeb@chromium.org> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#824803}
-
Side Yilmaz authored
This CL removes deprecated GetLastUsedProfileKey function, while replacing last occurrence of the function with GetLastUsedRegularProfileKey method. Since both regular and off-the-record profile use the same offline content aggregator, it is safe to use regular profile in the factory class. Note: This CL does not change any code behaviour. Bug: 1041781, 1075562 Change-Id: Ida23b329e1f4da6ad37abefea7a49e6c4575420e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2519454Reviewed-by:
David Trainor <dtrainor@chromium.org> Reviewed-by:
Ramin Halavati <rhalavati@chromium.org> Commit-Queue: Side YILMAZ <sideyilmaz@chromium.org> Cr-Commit-Position: refs/heads/master@{#824802}
-
Stanislav Pikulik authored
Unlike CLang in GCC with libstdc++ the expression std::max(alignof(T), sizeof(size_t))) is not recognized as an constant expression, which leads to the following error: requested alignment is not an integer constant. Bug: 819294 Change-Id: Ia1cad4d4b29b22960a7a824216f3d32d228f69cd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521116Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: José Dapena Paz <jdapena@igalia.com> Cr-Commit-Position: refs/heads/master@{#824801}
-
Yunke Zhou authored
Bug: 1134567 Change-Id: I8b278acaa2fab943ce136d7d7de578da7a63e992 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2520778Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Commit-Queue: Yunke Zhou <yunkez@google.com> Cr-Commit-Position: refs/heads/master@{#824800}
-
Findit authored
This reverts commit 37c7a793. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 824767 as the culprit for failures in the build cycles as shown on: https://analysis.chromium.org/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtLzM3YzdhNzkzMTA0NjU2ODAyYjRhNjkxNWYwYWI0YTRlZGQwNTY2YzkM Sample Failed Build: https://ci.chromium.org/b/8864392849428929040 Sample Failed Step: browser_tests Original change's description: > Put logic to disable Lite video on seek behind finch > > This CL moves the logic to disable lite videos on seek > behind experiment parameter, and also disables that by default. > > The param can be enabled again once we are reasonably confident > that it's not too aggressive and we can run an experiment to > verify that. > > Change-Id: I950b6d42750f11156ba0f0afad5989ac19832a7b > Bug: 1145646 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2519719 > Commit-Queue: Tarun Bansal <tbansal@chromium.org> > Reviewed-by: Michael Crouse <mcrouse@chromium.org> > Reviewed-by: rajendrant <rajendrant@chromium.org> > Cr-Commit-Position: refs/heads/master@{#824767} Change-Id: Ia1e4c0a2239fe64b3073ad3ebd5806cc41cfb51f No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1145646 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522621 Cr-Commit-Position: refs/heads/master@{#824799}
-
Peter Marshall authored
This CL plumbs in everything needed for a new HaTS Next survey that DevTools trigger. The survey config doesn't exist yet so this CL won't cause surveys to be shown yet. Bug: 1112738 Change-Id: I2ccd087ad510f849616bf567a14a96aa8f0f439b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2517719Reviewed-by:
Theodore Olsauskas-Warren <sauski@google.com> Commit-Queue: Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#824798}
-
Mikel Astiz authored
By enabling this feature by default, it will cause that small fraction of users redownload all their sync bookmarks, in order to determine their authoritative/final GUIDs. With this, the migration phase is considered complete and bookmarks are guaranteed to use the same GUID across syncing devices for all users. Metric Sync.BookmarkModelMetadataClientTagState suggests the majority of sync clients have knowledge of all authoritative bookmark GUIDs, first introduced in M81 and gradually being populated in the commit path with https://crrev.com/c/1981610. For the remaining few clients, it may take very long to receive the authoritative bookmark GUIDs, presumably due to inactive users or users that have just upgraded from old versions of the browser. To resolve this faster, the alternative is to redownload all bookmarks from the server (including their authoritative GUIDs). This is precisely achieved with the feature toggle enabled by default in this patch. The actual impact of this change will be measured using metric Sync.BookmarksModelMetadataCorruptionReason bucket MISSING_CLIENT_TAG_HASH, which prior to this patch was dominated by the soft counterpart of this logic, already enabled by default (feature toggle InvalidateBookmarkSyncMetadataIfClientTagMissingWhileInSync). Change-Id: Id9957b420e78f5f8d4f1dbd6a5853cf14c31d560 Bug: 1032052 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424290 Commit-Queue: Mikel Astiz <mastiz@chromium.org> Reviewed-by:
Rushan Suleymanov <rushans@google.com> Cr-Commit-Position: refs/heads/master@{#824797}
-
chromium-autoroll authored
Roll Chrome Win32 PGO profile from chrome-win32-master-1604609790-b9d65003227996f3e38071970a83664b74f65abb.profdata to chrome-win32-master-1604629242-25a4011689f36cdb7c5ac3ab0a40a3994e18267e.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: I7a2604b855566115216172bbd36688e3fc2ed035 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522952Reviewed-by:
-
Mugdha Lakhani authored
Bug: 1144282 Change-Id: I06463b63fdcf1da40816a5c8fba014ff67bdd2c7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521148 Auto-Submit: Mugdha Lakhani <nator@chromium.org> Commit-Queue: Colin Blundell <blundell@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#824795}
-
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: I8a4f3a027e7dcf494777cf80b52eab2a90b55c56 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522690Reviewed-by:
-
Clemens Arbesser authored
This also refactors some of the calling methods to use GURL in favor of plain strings. Unfortunately, the browse_domains_allowlist is currently specified in an incompatible format without the http spec, so those are still plain strings. Bug: b/171776026 Change-Id: I4774209f71eef1b2ec6e5e8580d173e06bcd9ec2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2517447 Auto-Submit: Clemens Arbesser <arbesser@google.com> Reviewed-by:
Marian Fechete <marianfe@google.com> Commit-Queue: Clemens Arbesser <arbesser@google.com> Cr-Commit-Position: refs/heads/master@{#824793}
-
Alexander Cooper authored
Adds UseCounters and the necessary flag integration to conduct an origin trial for WebXRLightEstimation. The Origin Trial itself will not be enabled until after the I2E and the launch bug have been approved. I2E: https://groups.google.com/a/chromium.org/g/blink-dev/c/zt3gLmrhTHc/m/9jxodKr5CAAJ Bug: 1070819 Change-Id: I40f7de94cda4189445bce6996928619fc15f1d15 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522123 Auto-Submit: Alexander Cooper <alcooper@chromium.org> Commit-Queue: Yoav Weiss <yoavweiss@chromium.org> Reviewed-by:
Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/master@{#824792}
-
Chromium WPT Sync authored
Using wpt-import in Chromium 52d33a46. With Chromium commits locally applied on WPT: 9a749c24 "[scroll-animations] Handle implicit 'auto' offsets correctly" 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=robertma@google.com No-Export: true Cq-Include-Trybots: luci.chromium.try:linux-wpt-identity-fyi-rel,linux-wpt-payments-fyi-rel Change-Id: Ifa4ef2138c9d62a2c360f46a8fc2a98ce94fa3cd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522231Reviewed-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@{#824791}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/c2b2b5788575..a61d07a72763 2020-11-05 46493288+sfricke-samsung@users.noreply.github.com spirv-val: Fix SPV_KHR_fragment_shading_rate VUID label (#4014) 2020-11-05 46493288+sfricke-samsung@users.noreply.github.com spirv-val: Label Layer and ViewportIndex VUIDs (#4013) 2020-11-05 alanbaker@google.com Add dead function elimination to -O (#4015) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/spirv-tools-chromium-autoroll Please CC radial-bots+chrome-roll@google.com,courtneygo@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_angle_vk32_deqp_rel_ng;luci.chromium.try:android_angle_vk32_rel_ng;luci.chromium.try:android_angle_vk64_deqp_rel_ng;luci.chromium.try:android_angle_vk64_rel_ng;luci.chromium.try:linux_angle_deqp_rel_ng;luci.chromium.try:linux-angle-rel;luci.chromium.try:win-angle-rel-32;luci.chromium.try:win-angle-rel-64;luci.chromium.try:win-angle-deqp-rel-32;luci.chromium.try:win-angle-deqp-rel-64 Tbr: radial-bots+chrome-roll@google.com,courtneygo@google.com Change-Id: Ic15c1ac4475321f5f2becc834cf77370ed9a5d0e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523015Reviewed-by:
-
Jordan Demeulenaere authored
This CL refactors ElementFinder so that the elements it matches have the same order than in the document. This is done with 2 changes: 1) Elements matched by the css_selector filter are now added in the same order than the parent element that was used to query the selector. 2) The results of the background tasks are now added in current_matches_ in the same order than the parent element that was used as the root of the background task. I will add relevant browser tests once we can easily check multiple matching elements (i.e. either via a new pick_at filter or getting the outerHTML of multiple elements). Change-Id: If1f7098d3467461a39a3b34773f1e02db0a73069 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2517577 Commit-Queue: Jordan Demeulenaere <jdemeulenaere@chromium.org> Reviewed-by:
Stephane Zermatten <szermatt@chromium.org> Cr-Commit-Position: refs/heads/master@{#824789}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/0f76c73eff05..e9554189c71b 2020-11-06 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools Chromium DEPS. 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: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: If1f35bdd0ecc548c4f9a0dd451576f60d3f2095b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522687Reviewed-by:
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/e97171d2..24c7b2d7 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: I954658d06f15af89b4381cabbb78390d6ea439bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522163Reviewed-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@{#824787}
-
Rakina Zata Amni authored
This allows us to experiment with having multiple bfcached pages in one tab. Bug: 1136658 Change-Id: I3bffb186cad637dbac6e05595e9e8eeb56ec70af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2518313 Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Reviewed-by:
Alexander Timin <altimin@chromium.org> Cr-Commit-Position: refs/heads/master@{#824786}
-
David Roger authored
This CL uses overflow-wrap: break-word; to avoid breaking the bubble layout. This should happen very rarely. Screenshot without the fix: https://drive.google.com/file/d/1SLsl065XjOnZGNt9Y8f3ymjdKUvTcMhK/view With the fix: https://drive.google.com/file/d/1SsJ5OnBA9cpHRCESRfbETA7fGfupdiLX/view Bug: None Change-Id: Icaf3e99abf1c6119b0c8e3f47b8ad263d6d58d8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2520905 Auto-Submit: David Roger <droger@chromium.org> Commit-Queue: Monica Basta <msalama@chromium.org> Reviewed-by:
Monica Basta <msalama@chromium.org> Cr-Commit-Position: refs/heads/master@{#824785}
-
chromium-autoroll authored
Roll Chrome Linux PGO profile from chrome-linux-master-1604620781-8baad16a8ee2321f3de713350b41c3a35b5f14db.profdata to chrome-linux-master-1604642156-a25919d317c2bef6f3d61358a8f8892267c9f548.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: I2cd1529be77794c6f1a0a18dfd4d4e80a8c51407 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523013Reviewed-by:
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/e3fee63a19d6..8b665312ca15 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: I0cad7d7744c26698270c300eb2473208b8d48f99 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522161Reviewed-by:
-
Kenichi Ishibashi authored
This CL moves MakeSelfOwneReceiver() for resource reader/writer from ServiceWorkerStorageControlImpl to ServiceWorkerStorage. This move allows us to call LazyInitialize() if the internal storage hasn't been initialized yet. This behavior simplifies service worker storage service recovery steps because it would eliminate a need for force initialization after restart. As a side effect we need to update helper functions in service_worker_storage_unittest.cc Bug: 1133143 Change-Id: I43057adfbbc91d94dd5aedc22c684cb862ab26d8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2519345Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Cr-Commit-Position: refs/heads/master@{#824782}
-
Sigurd Schneider authored
This CL allows the WorkerDevToolsAgentHost to get to the DedicatedWorkerHost of the associated dedicated worker, which was previously not possible. This is accomplished by re-using the dedicated worker token as devtools token, and by adding a lookup mechanism on the DedicatedWorkerServiceImpl which allows looking up the DedicatedWorkerHost based on said token. The CL then uses this mechanism to allow look-up of the COEP status on dedicated workers. Bug: chromium:1051466, chromium:1145158 Change-Id: Id038006e6437d3c622ca74979ac1ab4493bcd240 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2494861Reviewed-by:
Patrick Monette <pmonette@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by:
Andrey Kosyakov <caseq@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#824781}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/8b665312ca15..0891c367b8b2 2020-11-06 chinglinyu@google.com Merge "traced: provide options to set socket permissions." 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: I06d7478c34a985fac544646a8bcc1ab59169da48 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522599Reviewed-by:
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1604620781-6e005798045dacc8d1de821cf745cddceb8035b4.profdata to chrome-mac-master-1604642156-6de658d746d924ba0793cdd79cc80ba08c1ee69e.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: I45082c033d3775c4995ef0fb7ca5351913264713 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522688Reviewed-by:
-
