- 14 Jan, 2021 40 commits
-
-
Caitlin Fischer authored
Bug: 1144792 Change-Id: I9563b56493a68dc6f7598c2b08248612575f552a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623195Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Cr-Commit-Position: refs/heads/master@{#843327}
-
Christoph Schwering authored
The experiment is not active. Bug: 1007974, 949783 Change-Id: I0ccebe9f54ae927bab0d7a0ca6c53d1e7467bfb6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623287Reviewed-by:
Dominic Battré <battre@chromium.org> Reviewed-by:
Matthias Körber <koerber@google.com> Commit-Queue: Christoph Schwering <schwering@google.com> Cr-Commit-Position: refs/heads/master@{#843326}
-
Dominic Mazzoni authored
Background images are normally hidden in forced-colors mode, but the Google logo should still be visible. It'd be worth considering making it an <img> instead, but in the meantime, forced-color-adjust: none is a simpler, safer, targeted fix. Bug: 1166383 Change-Id: Ie29b351020c652a6fe381bcdce6ef4a9a1e03d66 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627966 Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Reviewed-by:
Tibor Goldschwendt <tiborg@chromium.org> Cr-Commit-Position: refs/heads/master@{#843325}
-
Adam Langley authored
Fixed: 1166254 Change-Id: I4bfd0c178757d7b24959180b9db083d545607b68 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628046 Auto-Submit: Adam Langley <agl@chromium.org> Commit-Queue: Martin Kreichgauer <martinkr@google.com> Reviewed-by:
Martin Kreichgauer <martinkr@google.com> Cr-Commit-Position: refs/heads/master@{#843324}
-
Weblayer Skew Tests Version Updates authored
This CL will add skew tests for version 87.0.4280.150. R=rmhasan@google.com Bug: 1041619 Change-Id: I66c0e53f43b30a8da9fa94755081e91bdbcf9b52 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627999 Commit-Queue: chrome-weblayer-builder <chrome-weblayer-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: Rakib Hasan <rmhasan@google.com> Reviewed-by:
Rakib Hasan <rmhasan@google.com> Cr-Commit-Position: refs/heads/master@{#843323}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/3549479dc4cc..c4a1bd4553ff 2021-01-13 amaiorano@google.com Implement VK_EXT_headless_surface 2021-01-13 natsu@google.com Update AHB default YUV dataspace to YCBCR_601 2021-01-13 capn@google.com VulkanBenchmarks: refactor into Image class 2021-01-13 capn@google.com Fix back-face culling for vertices near w=0 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Please CC swiftshader-team+autoroll@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_chromium_msan_rel_ng;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;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: swiftshader-team+autoroll@google.com Change-Id: I38c6d95c313d6374711f804af228977cd6a7a57c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627814Reviewed-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@{#843322}
-
David Grogan authored
Because we shouldn't create a fragment with a -1 block size. Change-Id: I787c09024d3dbdc478a6fe0b8a201ea5596390d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2611570Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: David Grogan <dgrogan@chromium.org> Cr-Commit-Position: refs/heads/master@{#843321}
-
Caitlin Fischer authored
Bug: 776416, 1126640 Change-Id: Icea9823e21112a79dbd2b93469a77df5c2820fc3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627713Reviewed-by:
Alexander Timin <altimin@chromium.org> Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Cr-Commit-Position: refs/heads/master@{#843320}
-
Austin Sullivan authored
Currently takes a raw ptr. The reasoning for such is not strong: "This doesn't take std::unique_ptr<> just to save extra base::WrapUnique" Bug: N/A Change-Id: I5144706466787d7ee23210d61c2f855065e391ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627132Reviewed-by:
Victor Costan <pwnall@chromium.org> Reviewed-by:
Austin Tankiang <austinct@chromium.org> Commit-Queue: Austin Sullivan <asully@chromium.org> Cr-Commit-Position: refs/heads/master@{#843319}
-
Brian Sheedy authored
Adds a script to find cases where the tags known to the tests and the tags generated when tests are run on the bots are different. This is a necessary tool for making the generation of unknown tags fatal in the future, as we need to know what tags we need to ignore or otherwise address before turning on that functionality. Also updates a couple of ignored tags that were pointed out by the script. Bug: 1011107 Change-Id: I9022fc779de718b53ea3469d6048dd0fcd7b8c73 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628043 Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Auto-Submit: Brian Sheedy <bsheedy@chromium.org> Reviewed-by:
Yuly Novikov <ynovikov@chromium.org> Cr-Commit-Position: refs/heads/master@{#843318}
-
Dan Harrington authored
Without internal src, there's no way to render the content. So just don't request the content if there's no renderer. Change-Id: I76304b3de576b9bf9662ecbbbe7317f91aa28580 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627981 Commit-Queue: Dan H <harringtond@chromium.org> Reviewed-by:
Cathy Li <chili@chromium.org> Reviewed-by:
Justin DeWitt <dewittj@chromium.org> Cr-Commit-Position: refs/heads/master@{#843317}
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1610560659-e96e8917fec116ef2a139db8416bd66f9188db27.profdata to chrome-win64-master-1610571527-cb84a3d10a676e72fe097e5f2fde0ba90e629978.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: Ia8fb00004a7591a0bdb41b98bc3b2afbd6288a37 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628341Reviewed-by:
-
Joel Riley authored
AX-Relnotes: Select-to-speed reading speed selector now will multiple the default rate rather than override, so if default rate is 2.0x and 2.0x is selected in STS, then effective rate is 4x. Bug: 1166252 Change-Id: I9004b1af56cad3374cadeb5c4ae2ce00892b8c61 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627937 Commit-Queue: Joel Riley <joelriley@google.com> Reviewed-by:
Katie Dektar <katie@chromium.org> Cr-Commit-Position: refs/heads/master@{#843315}
-
Sophie Chang authored
Reland "Reenable PredictionManager and HintsFetcher browser tests that were disabled on desktop platforms" This is a reland of 3bd04812 No changes since this one was reverted incorrectly Original change's description: > Reenable PredictionManager and HintsFetcher browser tests that were > disabled on desktop platforms > > Change-Id: I173ac1025760f908042e64c7c8839fb90e41fc78 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626918 > Reviewed-by: Michael Crouse <mcrouse@chromium.org> > Commit-Queue: Sophie Chang <sophiechang@chromium.org> > Cr-Commit-Position: refs/heads/master@{#843180} Change-Id: I2bc3449abe44516f018c828c0d91a51101186439 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2625959 Commit-Queue: Sophie Chang <sophiechang@chromium.org> Commit-Queue: Michael Crouse <mcrouse@chromium.org> Auto-Submit: Sophie Chang <sophiechang@chromium.org> Reviewed-by:
Michael Crouse <mcrouse@chromium.org> Cr-Commit-Position: refs/heads/master@{#843314}
-
Solomon Kinard authored
This should make it easier to for casual readers to see which wildcards are allowed. Reference: https://developer.chrome.com/docs/extensions/mv2/match_patterns/ Bug: 1133624 Change-Id: Ifd5b26e7b052f07c62dc0846cff4dfe922d52134 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2613512 Commit-Queue: Solomon Kinard <solomonkinard@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/master@{#843313}
-
Cammie Smith Barnes authored
Removes '^chrome/test/chromedriver/server/http_handler.cc' from the _NOT_CONVERTED_TO_MODERN_BIND_AND_CALLBACK list in src/PRESUBMIT.py, as the chrome/test directory has now been fully converted. Bug: 1007643 Change-Id: Ib57bcb674ac8c26c7ad5553267194cecd590591d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626176Reviewed-by:
Charlie Reis <creis@chromium.org> Commit-Queue: Cammie Smith Barnes <cammie@chromium.org> Cr-Commit-Position: refs/heads/master@{#843312}
-
Yao Xiao authored
Explainer: https://github.com/WICG/floc#opting-out-of-computation This feature controls the access to the interest cohort (https://github.com/WICG/floc) as well as the eligibility for the navigation history entry to be included in the interest cohort computation. Let the feature availability be controlled by a chrome feature to allow some flexibility while finalizing on the decision. In reality, we will probably want to enable the chrome feature before it goes to OT. Use browsertest for testing as opposed to using webtest, as the functions rely on the chrome layer. Bug: 1158851 Change-Id: I2a81f9547c9180bf3c6ac65974eb0b1666a41812 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2593688 Commit-Queue: Yao Xiao <yaoxia@chromium.org> Reviewed-by:
Charlie Harrison <csharrison@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#843311}
-
Michael Montvelishsky authored
Bug: none Test: none Change-Id: I19e2731087799e7f58dfd43c66d65d0ff5e5cfb8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627873 Auto-Submit: Michael Montvelishsky <mont@chromium.org> Commit-Queue: Kenneth MacKay <kmackay@chromium.org> Reviewed-by:
Kenneth MacKay <kmackay@chromium.org> Cr-Commit-Position: refs/heads/master@{#843310}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/9b5dd7ab8a98..64d94deaa6a4 2021-01-14 ehmaldonado@google.com presubmit: Use new API to check for owners approval If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Please CC sokcevic@google.com,ajp@google.com,apolito@google.com,ehmaldonado@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: sokcevic@google.com,ajp@google.com,apolito@google.com,ehmaldonado@google.com Change-Id: Id46502da345918835c0e3df5ee1643a7f5156cbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628346Reviewed-by:
-
Trevor Perrier authored
This CL moves the expiry on the detailed-language-settings flag from M89 to M91. Bug: 1127531 Change-Id: I23d2df7e3a2b87a45bc8c87baafb45589dee4b4a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626977Reviewed-by:
Megan Jablonski <megjablon@chromium.org> Commit-Queue: Trevor Perrier <perrier@chromium.org> Cr-Commit-Position: refs/heads/master@{#843308}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/20d3823787dd..3f6d4980860b 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 yutak@google.com,mpearson@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: chromium:1164243 Tbr: yutak@google.com,mpearson@google.com Change-Id: I98b55b506d69b9fe546f2a6ee06c706bec917775 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628342Reviewed-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@{#843307}
-
Austin Sullivan authored
Refactor content/public/browser and chrome/browser All changes are find-and-replace unless called out in a comment. Bug: 1110509 Change-Id: Ib46ed353865321413e49a56477a4a07b47034e93 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2602222 Commit-Queue: Austin Sullivan <asully@chromium.org> Reviewed-by:
Daniel Rubery <drubery@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Emily Stark <estark@chromium.org> Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Reviewed-by:
David Roger <droger@chromium.org> Reviewed-by:
Marijn Kruisselbrink <mek@chromium.org> Cr-Commit-Position: refs/heads/master@{#843306}
-
Yuta Hijikata authored
The patch removes is_lacros, is_ash, IS_LACROS and IS_ASH which were aliases for is_chromeos_lacros, is_chromeos_ash, IS_CHROMEOS_ASH and IS_CHROMEOS_LACROS. The names were changed to make it clearer that the variables are related to CrOS. Bug: 1052397 Change-Id: Id5b9b1b2ca3d34a9773ae73e4cc9408b9633e0ca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627529Reviewed-by:
Nico Weber <thakis@chromium.org> Reviewed-by:
Hidehiko Abe <hidehiko@chromium.org> Commit-Queue: Yuta Hijikata <ythjkt@chromium.org> Cr-Commit-Position: refs/heads/master@{#843305}
-
Xianzhu Wang authored
It will be called to map a cull rect from parent space to local space in cull rect update during PrePaint. The purpose is to mark PaintLayers needing repaint on cull rect changes before paint, instead of checking interest rect / cull rect changes during paint, to avoid setting PaintLayer needing repaint unnecessarily, especially for CAP during composited scrolling. Besides the original features of CullRect::ApplyTransforms() which is used in cull rect mapping for CompositeAfterPaint, it also implements the following features to be on par with CompositedLayerMapping:: ReComputeInterestRect(): - Considering clips in additional to scroll clips, - Clipping expanded cull rect by scrolling contents rect for composited scroll translations, - Clamping extreme geometry values, - Adaptive expansion distance for composited transforms. The next steps are: 1. Add CullRectUpdater which updates cull rects during PrePaint when runtime feature CullRectUpdate is enabled. 2. Use the updated cull rect to replace interest rect in pre-CAP and cull rect in CAP and pre-CAP, still behind the runtime feature. 3. Enable CullRectUpdate for CAP 4. Enable CullRectUpdate for pre-CAP. 5. Remove old interest rect / cull rect code. Bug: 1046544 Change-Id: I6e7e9f85bc0b4640e67de1732744e647b6f7e230 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2620090Reviewed-by:
Philip Rogers <pdr@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#843304}
-
Max Curran authored
Initial implementation of the background task to measure how often user are offline and what they do while offline. Full Design Doc: https://docs.google.com/document/d/1Vv6fdaRWjLpxeuVR89C6y5cGcAiCu6f4YBRwMjpN_T0/edit?usp=sharing Bug: 1131600 Change-Id: I89f67a6bbdaf71b550518b40c06788e3dfaccf11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2459946 Commit-Queue: Max Curran <curranmax@chromium.org> Reviewed-by:
Filip Gorski <fgorski@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Reviewed-by:
Robert Ogden <robertogden@chromium.org> Cr-Commit-Position: refs/heads/master@{#843303}
-
Azeem Arshad authored
This CL changes eid_popup component so that it fetches eid qr code image data from mojo service and renders it on a canvas. Screenshot: http://screen/bVoRYtfvfMMyMb4.png Bug: 1093185 Change-Id: Iae2f248c5524495aa13e85b25ea6add02c382d88 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2613945 Commit-Queue: Azeem Arshad <azeemarshad@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#843302}
-
Joel Riley authored
When navigation controls are not present, STS was not going into inactive state after TTS completed. This CL fixes this issue, as calling updatePauseStatusFromTtsEvent_ was setting STS back into SPEAKING state. Also, if STS is activated without nodes, do not show panel. AX-Relnotes: Bug fix when activating STS without navigation controls, STS did not go back into inactive state. Bug: 1165847 Change-Id: I88b44e84de525d2dbc190b97fa02b691394cb294 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2625268 Commit-Queue: Joel Riley <joelriley@google.com> Reviewed-by:
-
John Delaney authored
What: Replace usage of ShellAddedObserver + TestNavigationObserver with TestNavigationObserver::StartWatchingNewWebContents(). Why: Tests are flaking from calls to TestNavigationObserver::Wait() hanging. The existing solution assumes that the test will setup the TestNavigationObserver before the newly opened WebContents starts the navigation. However this isn't necessarily true, as we aren't registering the TestNavigationObserver in the same callstack in which the web contents is created. Bug: 1166341 Change-Id: Id2b5f36158f86377b3881e54d793c27af718cb1e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627757Reviewed-by:
-
Caitlin Fischer authored
Bug: 1126640 Change-Id: Ic81197c9b576e8f6045365196ec0f3637509c0c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628109Reviewed-by:
Dominic Farolino <dom@chromium.org> Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Cr-Commit-Position: refs/heads/master@{#843299}
-
Eric Willigers authored
In guest mode, shared files in the .WebShare/ directory are deleted when the user logs off (if they are not deleted earlier). In incognito mode, we continue to prevent file sharing. Bug: 1161373 Change-Id: I0542d4ba92381c7ab2f07bbab896242bcc643057 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626991 Commit-Queue: Glen Robertson <glenrob@chromium.org> Reviewed-by:
Glen Robertson <glenrob@chromium.org> Auto-Submit: Eric Willigers <ericwilligers@chromium.org> Cr-Commit-Position: refs/heads/master@{#843298}
-
Roman Arora authored
Relevant pinpoint benchmark results: https://pinpoint-dot-chromeperf.appspot.com/job/12d352aad20000 https://pinpoint-dot-chromeperf.appspot.com/job/1011ee42d20000 https://pinpoint-dot-chromeperf.appspot.com/job/11aa1592d20000 Bug: 1149400 Change-Id: Ibe3afd85eaeaa8b6f13902c282cc3f5bb45ca3e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623159Reviewed-by:
Thomas Lukaszewicz <tluk@chromium.org> Reviewed-by:
Yuheng Huang <yuhengh@chromium.org> Commit-Queue: Roman Arora <romanarora@chromium.org> Cr-Commit-Position: refs/heads/master@{#843297}
-
Nancy Wang authored
UI review deck: go/cros-full-restore PRD: go/cros-full-restore-prd Design doc: go/chrome-os-full-restore-dd When the full restore feature is enabled, whether to launch the browser is controlled by the full restore process: 1. If the full restore setting is not restore, don't launch the browser. 2. If the user selects restore or set always restore, launch the browser. This CL modified the current launching browser process during the startup phase. 1. If the full restore feature is disabled, the current process is not changed. 2. If the full restore feature is enabled, postpone the browser launching. Only when the restore data has been fetched, and the user selects restore or set always restore, launch the browser by the full restore process. BUG=1146900 Change-Id: I9f03e7039761f4d2956b7d4c2bdeecf99ef2d955 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2603759Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Commit-Queue: Nancy Wang <nancylingwang@chromium.org> Cr-Commit-Position: refs/heads/master@{#843296}
-
Ted Meyer authored
It's no longer used, so get rid of it. Change-Id: I2e9b98b3719a71645f8148dcc1acaae804559be4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623155 Commit-Queue: Ted Meyer <tmathmeyer@chromium.org> Reviewed-by:
Frank Liberato <liberato@chromium.org> Cr-Commit-Position: refs/heads/master@{#843295}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/8fccd82e4e02..59abfbcd2b03 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: I58cc47d2c3a3107a3ccf93bdb2e3b33e2600db60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627986Reviewed-by:
-
Regan Hsu authored
Fixed: 1164582 Bug: 1106937 Change-Id: Iac5a7f61cd0f3b3354c4e9281342b07edb18b26b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627145Reviewed-by:
Mark Pearson <mpearson@chromium.org> Reviewed-by:
-
Philip Rogers authored
Transform nodes store a changed field that is used to cause damage in the compositor (see: PaintArtifactCompositor::PropertyTreeStateChanged). We need to ensure changed state is not lost when decompositing (see: PaintArtifactCompositor::DecompositeTransforms). This patch takes a simple approach of recording the changes of decomposited transform nodes on PendingLayers, and using that to cause damage. This fixes a bug where a change on a decomposited transform node failed to cause damage. http://crrev.com/c/2626192 explored an approach of not decompositing nodes with changes but that leads to unnecessary additional layers. Bug: 1164513 Change-Id: I9c6d68f748772e9c2a86158e62bc0c7db3e8733f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627943 Commit-Queue: Philip Rogers <pdr@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Auto-Submit: Philip Rogers <pdr@chromium.org> Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#843292}
-
Kunihiko Sakamoto authored
Now it has the same expiration date as the other WebFont.DownloadTime.* histograms. Bug: 1156194 Change-Id: Ie2e9ec544359dc9498a96064964a173b901f7d9c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2622688Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Takashi Toyoshima <toyoshim@chromium.org> Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#843291}
-
Sinan Sahin authored
This CL adds support for horizontal swipe-to-dismiss gestures, adds fling support and updates the existing motion specs. It also adds unit tests for the mediator. Flings currently don't affect the speed of the resulting animations as it turned out to be complicated to implement. There are several cases that are handled in this CL: - No fling: - If the message is within the dismiss threshold, vertical or horizontal, the message is animated back to the idle position, i.e. center. - If it's outside the threshold, the message is dismissed by being animated to out of screen. - Fling: - If the message is flung toward the center from outside the dismiss threshold, it is animated to the idle position. - If it's flung from within the threshold to the outside, the message is dismissed with animation. - If it's flung toward out of screen from outside the dismiss threshold, the message is dismissed with animation. Bug: 1157213 Change-Id: I82cfac7111e5ada8687be74a90162784a1e7c992 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2602706 Commit-Queue: Sinan Sahin <sinansahin@google.com> Reviewed-by:Pavel Yatsuk <pavely@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Cr-Commit-Position: refs/heads/master@{#843290}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/47e9aed2af83..6c79df687e09 2021-01-13 m.maiya@samsung.com Allow attributes and uniforms to have the same name 2021-01-13 jmadill@chromium.org infra: Fix win-trace-rel bot typo. 2021-01-13 jmadill@chromium.org Program: Support multiple varying packings. 2021-01-13 cnorthrop@google.com Capture/Replay: Add DrawBuffer state to MEC 2021-01-13 jmadill@chromium.org Test Runner: Add a slow tests list. 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 timvp@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: timvp@google.com Test: Test: Aztec Ruins MEC Change-Id: I0eea686ff6ca592f67f32d87b7ada4f6ea2d6481 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628050Reviewed-by:
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/a1598e58..8b42c4e7 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: Id40defc26f7eead5a9b7c77045b5ffa98538cc6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628072Reviewed-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@{#843288}
-
