- 08 Jan, 2021 40 commits
-
-
Brandon Jones authored
Previously dataOffset and size were always in bytes, which isn't consistent with the WebGPU spec. Corresponding CTS test here: https://github.com/gpuweb/cts/pull/431 Bug: 1163667 Change-Id: I5360cfbd66542c044dcf909b8673d3ed3f5e6724 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2615520Reviewed-by:
Corentin Wallez <cwallez@chromium.org> Commit-Queue: Brandon Jones <bajones@chromium.org> Cr-Commit-Position: refs/heads/master@{#841617}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/d8ca7d624751..fa449cf3b0d0 2021-01-08 jmadill@chromium.org Fix separable Geometry Shaders. 2021-01-08 jmadill@chromium.org Merge Program/ProgramPipeline::getMergedVaryings(). If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC ianelliott@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: ianelliott@google.com Change-Id: Iec8d1c8a2172b107ba5cea105456f12cdb089170 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618199Reviewed-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@{#841616}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/24cfa1c1796a..a24bf6b63c40 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 dalecurtis@google.com,wjmaclean@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:1151860 Tbr: dalecurtis@google.com,wjmaclean@google.com Change-Id: Ica0d4d702cedb9f9cfcb4d3500df7dbbf67b5c07 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618245Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
James MacLean <wjmaclean@chromium.org> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#841615}
-
Philipp Hancke authored
BUG=chromium:1164376 Change-Id: Ic9321b007e652f8d6b0ca40e490645735296317b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2616411Reviewed-by:
Harald Alvestrand <hta@chromium.org> Commit-Queue: Philipp Hancke <philipp.hancke@googlemail.com> Cr-Commit-Position: refs/heads/master@{#841614}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/60b433cf0b29..0e4e5ae5944a 2021-01-08 ehmaldonado@google.com Reland "[owners] Refactor OwnersClient." 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 ajp@google.com,apolito@google.com,ehmaldonado@google.com,sokcevic@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: ajp@google.com,apolito@google.com,ehmaldonado@google.com,sokcevic@google.com Change-Id: I344a3ae5bedbc7be7a7d7de6aee33317b336c6c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2617282Reviewed-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@{#841613}
-
Sunggook Chue authored
OsIntegrationManager is a proxy class that doesn't have to know its detailed OS calls instead it delegates a work to the target class if it exists. AppShortcutManager handles shortcut creation (see CreateShortcuts in OsIntegrationManager) that includes proper telemetry message at the end of it. However the current DeleteShortcuts is simply handled by the OsItengrationManager instead of AppShortcutManager. The change is to follow pattern of CreateShortcuts for the shortcut deletion that seems more consistent in terms of OsItegrationManager and AppShortcutManager relationship. Bug: 1151796 Change-Id: I01e80b0a13ef1169a238d65a2ffc5acb6cca292f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2606680Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Commit-Queue: Daniel Murphy <dmurph@chromium.org> Cr-Commit-Position: refs/heads/master@{#841612}
-
Nancy Wang authored
Add the class FullRestoreDataHandler to observe AppRegistryCache. When the app is removed, remove the full restore data from both FullRestoreReadHandler and FullRestoreSaveHandler. BUG=1146900 Change-Id: Ie55b6310e3e302ac4829b7c76c10880928266651 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2608045 Commit-Queue: Nancy Wang <nancylingwang@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#841611}
-
Claude van der Merwe authored
This CL: 1. Does not initialize the network cache until the user's networks have been loaded. 2. Queues calls to GetAllSyncableNetworks until the network cache has been loaded Bug: 1154341 Change-Id: I158cb29109c9f8de52ff09f1c82866931e371459 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2600119 Commit-Queue: Claude van der Merwe <cvandermerwe@google.com> Reviewed-by:
Azeem Arshad <azeemarshad@chromium.org> Reviewed-by:
Jon Mann <jonmann@chromium.org> Cr-Commit-Position: refs/heads/master@{#841610}
-
Allen Bauer authored
Bug: 938501 Change-Id: Idcc0c7970542266d5b4b53b938238309f063e27f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618487 Commit-Queue: Allen Bauer <kylixrd@chromium.org> Commit-Queue: Wei Li <weili@chromium.org> Reviewed-by:
Wei Li <weili@chromium.org> Auto-Submit: Allen Bauer <kylixrd@chromium.org> Cr-Commit-Position: refs/heads/master@{#841609}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/3ce4e8ee1301..11e6cfe60a92 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: Ic81f2494a44e073389df2d30df907565429b0d57 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618162Reviewed-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@{#841608}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/a2e02836a260..c4efeef83334 2021-01-08 dawn-autoroll@skia-public.iam.gserviceaccount.com Roll Tint from 766e31d50710 to 1e01c2c11613 (3 revisions) 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 enga@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: enga@google.com Change-Id: I302a5d2316ea7e0f5225be6dea072905436266a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618500Reviewed-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@{#841607}
-
Bo Liu authored
ScreenOrientationProvider(Impl) is currently coded to assume the embedding Activity handles (and thus is not destroyed and recreated) on orientation change. All the API methods take WindowAndroid. This does not work for embedder that recreates the Activity (and by extension the WindowAndroid) on orientation change. This causes orientation requests made in this transition time to be completely dropped. Fix this for cases for requests made from WebContents from native code. If there is no WindowAndroid, add an observer to to wait until WebContents gets a WindowAndroid to make the request. Bug: 1159529 Change-Id: Iae177faffa67d3e4db58ea1e0d5a9df989d303a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2603856 Commit-Queue: Bo <boliu@chromium.org> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Cr-Commit-Position: refs/heads/master@{#841606}
-
Ana Salazar authored
Set the multipaste clipboard menu option as a new feature, depending on whether or not the feature flag should show. Bug: 1156270 Change-Id: I1b8c30bbb506c360a0206a31bbebea0286123d1e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618491Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Ana Salazar <anasalazar@chromium.org> Cr-Commit-Position: refs/heads/master@{#841605}
-
Will Cassella authored
This CL enables DAV1D on Android, which allows decoding of AV1 videos via Dav1dVideoDecoder, as well as decoding AVIF images via AVIFImageDecoder. Binary-Size: Decoders are large. Change-Id: I63bfb0b31a38f4ccde4e7aafe8f16bca7d8b926f Bug: 2558924 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2605293Reviewed-by:
Richard Coles <torne@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Commit-Queue: Will Cassella <cassew@google.com> Cr-Commit-Position: refs/heads/master@{#841604}
-
Liquan (Max) Gu authored
Since the isShowWaitingForUpdatedDetails parameter is unused in buildPaymentRequestUI(), this CL is to delete it. Change-Id: Ia98e24fab92e71505358abaa80ded9ff20047520 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2615321Reviewed-by:
Nick Burris <nburris@chromium.org> Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org> Cr-Commit-Position: refs/heads/master@{#841603}
-
Gordon Seto authored
Fix flaky OSSettingsCellularNetworksListV3Test failures caused by DOM not rendering completely before testing started. This is fixed by triggering the DOM to flush again before executing the rest of the test. This fix is confirmed by running the test with [100/100] passes. Fixed: 1164157 Change-Id: Ic014252a5ed749bc6641e6a6ab2f21383f09b165 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618480Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Commit-Queue: Gordon Seto <gordonseto@google.com> Cr-Commit-Position: refs/heads/master@{#841602}
-
Kyle Horimoto authored
This will provide granular results for potential failure reasons for Nearby Share and Phone Hub. Note that location::nearby::chrome::BluetoothClassicMedium is the only client of this function, so we can be confident that results of this metric are due to Nearby Connections. Fixed: 1163605 Bug: 1106937 Change-Id: Ib1091eb6f41f09daca038a5d07071bd81feae561 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2613737 Auto-Submit: Kyle Horimoto <khorimoto@chromium.org> Commit-Queue: Brian White <bcwhite@chromium.org> Reviewed-by:
Brian White <bcwhite@chromium.org> Reviewed-by:
Ryan Hansberry <hansberry@chromium.org> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#841601}
-
Nancy Wang authored
This CL implements the notification based on the full restore ui review deck: https://docs.google.com/presentation/d/1kg1HAyjHc3l9EnaBehCQS3K_O7BmLpE6x_JWAAGUOMc/edit#slide=id.g838f61fb61_2_38 For “ask every time” users, if they show consistent behavior, Chrome OS can suggest them to change defaults: If users choose “Restore” 3x in a row, show the set restore pref notification to suggest that they can set restore to default. Add the pref "restore_selected_count" to record how many times the user has selected the restore option. If the count is equal or more than 3 times, show the set restore pref notification. BUG=1146900 Change-Id: I98a3fd05116b4f722d48a76a5aef45d3cf299c4f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2606404 Commit-Queue: Nancy Wang <nancylingwang@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#841600}
-
chromium-autoroll authored
https://chromium.googlesource.com/vulkan-deps.git/+log/e395b66ed41c..a86dded0f15e 2021-01-08 chromium-autoroll@skia-public.iam.gserviceaccount.com Roll SPIRV-Cross from ce18d1b8a563 to 702c903f982d (1 revision) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/vulkan-deps-chromium-autoroll Please CC ianelliott@google.com,enga@google.com,radial-bots+chrome-roll@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: ianelliott@google.com,enga@google.com,radial-bots+chrome-roll@google.com Change-Id: Ifde5b67bf812b4400c5560ef3b170cb91c346d36 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2616823Reviewed-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@{#841599}
-
Siye Liu authored
This partially reverts commit d46bdb4f. Reason for revert: the change causes a regression where inserting text at end of current block and next block is an inline block, then the new selection will be end up at the beginning of next block. Per suggestion in crbug.com/1161370#c15, we only need to partially revert the change( change made in VisiblePositionTemplate::Create. Original change's description: > [Editing] Fix canonical caret position at line break > > Consider this testcase: > <style>div { width: min-content; padding: 5px; }</style> > <div contenteditable>line1<wbr>line2</div> > which is rendered as > line1 > line2 > > Before this patch, when clicking at the beginning of the 2nd line, the > caret would appear at the end of the 1st one, because CanonicalPosition > would search backwards even with a downstream affinity. > > Also, when clicking at the beginning of the 1st line and pressing the > down arrow key, the caret would move to the end of the 1st line instead > of to the beginning of the 2nd one. And pressing the key again would > have no effect, the caret would refuse to go down. > > This patch fixes these problems by making CanonicalPosition take a > TextAffinity parameter which affects whether the canonical position is > first searched backwards or forwards. If no suitable candidate is found, > it will still search in the other direction. > > And then, VisiblePosition::Create takes care of deciding between the > upstream and the downstream canonical positions, depending on the > affinity and whether there is a line break. > > Bug: 1002937 > > Web tests: > TEST=external/wpt/editing/run/caret-navigation-around-line-break.html > > Unit tests: > TEST=All/ParameterizedVisibleUnitsLineTest.inSameLine/0 > TEST=All/ParameterizedVisibleUnitsLineTest.inSameLine/1 > TEST=All/ParameterizedVisibleUnitsWordTest.StartOfWordShadowDOM/0 > TEST=All/ParameterizedVisibleUnitsWordTest.StartOfWordShadowDOM/1 > TEST=VisiblePositionTest.ShadowV0DistributedNodes > TEST=VisibleUnitsLineTest.endOfLine > TEST=VisibleUnitsLineTest.isEndOfLine > TEST=VisibleUnitsLineTest.isLogicalEndOfLine > TEST=VisibleUnitsLineTest.isStartOfLine > TEST=VisibleUnitsLineTest.logicalEndOfLine > TEST=VisibleUnitsLineTest.logicalStartOfLine > TEST=VisibleUnitsLineTest.startOfLine > TEST=VisibleUnitsTest.canonicalPositionOfWithHTMLHtmlElement > TEST=VisibleUnitsTest.canonicalPositionOfWithInputElement > TEST=VisibleUnitsTest.canonicalizationWithCollapsedSpaceAndIsolatedCombiningCharacter > > Change-Id: I82d86d40a87513b2e92c024735957e9f71154094 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2410404 > Commit-Queue: Oriol Brufau <obrufau@igalia.com> > Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> > Cr-Commit-Position: refs/heads/master@{#813744} Bug: 1002937 Bug: 1161370 Change-Id: I65dbc8b442ae308f42582095e4693d9f146b8b32 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2616734Reviewed-by:
Siye Liu <siliu@microsoft.com> Reviewed-by:
Oriol Brufau <obrufau@igalia.com> Commit-Queue: Siye Liu <siliu@microsoft.com> Cr-Commit-Position: refs/heads/master@{#841598}
-
Brandon Wylie authored
TBR=peconn@chromium.org Bug: 1164424 Change-Id: If98fe7d9ef0f688816c26eec3abf32786d130a9d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618486 Commit-Queue: Brandon Wylie <wylieb@chromium.org> Reviewed-by:
bttk <bttk@chromium.org> Cr-Commit-Position: refs/heads/master@{#841597}
-
Clark DuVall authored
We are planning on running binary experiments for isolated splits enabled/disabled on M89. I want to make sure there are no problems with the disabled version before branch cut. I'll revert this CL after a couple days. Bug: 1150162 Change-Id: I20061a079e897058625506dab810c4584c200fec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618367 Commit-Queue: Clark DuVall <cduvall@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#841596}
-
Erik Chen authored
This is a reland of 8d4df26b Original change's description: > Set "dev" channel for all lacros builds. > > Linux-chrome (of which lacros is a variant) has its channel set as a > runtime environment variable by the launcher script. For Lacros, we must > set the environment variable from ash. For now, we always set "dev" for > all builds of Lacros. > > Change-Id: I840286b6fd5772701c3f6d927986405697b82097 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570448 > Commit-Queue: Erik Chen <erikchen@chromium.org> > Reviewed-by: James Cook <jamescook@chromium.org> > Cr-Commit-Position: refs/heads/master@{#833460} Change-Id: I1d42534b8e289e1df63286658d9c7601357e82dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2617099Reviewed-by:
James Cook <jamescook@chromium.org> Commit-Queue: Erik Chen <erikchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#841595}
-
Kevin McNee authored
This test is flaky. Bug: 1144228 Change-Id: If00d25d5f3115ff203c9b333c5e617a2ece63657 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618082 Commit-Queue: Kevin McNee <mcnee@chromium.org> Commit-Queue: James MacLean <wjmaclean@chromium.org> Auto-Submit: Kevin McNee <mcnee@chromium.org> Reviewed-by:
James MacLean <wjmaclean@chromium.org> Cr-Commit-Position: refs/heads/master@{#841594}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/f78841938e2d..6ddca3188e2e 2021-01-08 cpinnamaneni@microsoft.com keyboard accessiblity for Add new context menu in data grid 2021-01-08 jacktfranklin@chromium.org Workflow improvements to component docs 2021-01-08 tvanderlippe@chromium.org Use top level await in component_docs 2021-01-08 tvanderlippe@chromium.org Remove component_docs from GRD 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:1164006 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I00fcbfb3bc7a020151af395bfa4ef77ae70ab524 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618161Reviewed-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@{#841593}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/afc78f5e6ae9..11e6cfe60a92 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: If9319b67d5e281ce80d281d8472930f7f1e4b750 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618366Reviewed-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@{#841592}
-
Scott Violet authored
This is no longer used. BUG=none TEST=none Change-Id: Id063e0eb48ccb46c1d0ae40946a251c8d8f4882a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2617121 Commit-Queue: James Cook <jamescook@chromium.org> Auto-Submit: Scott Violet <sky@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#841591}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/11e6cfe60a92..61125414310a 2021-01-08 treehugger-gerrit@google.com Merge "tracing: Add macro for retrieving category group name from state pointer" 2021-01-08 treehugger-gerrit@google.com Merge "tracing: Allow dynamically computed categories with TRACE_EVENT_API_GET_CATEGORY_GROUP_ENABLED" 2021-01-08 treehugger-gerrit@google.com Merge "tracing: Avoid clash with variables called |trace_id|" 2021-01-08 fmayer@google.com Merge "Expose heapprofd_client_api to mainline modules." 2021-01-08 hjd@google.com Merge "upkeep: Make loop variable const&" 2021-01-08 hjd@google.com Merge "trace_processor: Report error on traces <1us" 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: Iefa411feb5b4b0c1068dae5d94cfdbd5e0483cb1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618236Reviewed-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@{#841590}
-
David Van Cleve authored
This change adds a flag option to enable platform-provided trust token issuance (https://bit.ly/platform-provided-trust-tokens) in order to make manual testing easier. R=svaldez Bug: 1130248 Test: Confirmed old "Enabled" option -> PPTT off, new option -> PPTT on Change-Id: I191b08172147b3056a268fd630fcd07d7af6a5a0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2616140 Commit-Queue: David Van Cleve <davidvc@chromium.org> Commit-Queue: Matt Menke <mmenke@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Reviewed-by:
Steven Valdez <svaldez@chromium.org> Auto-Submit: David Van Cleve <davidvc@chromium.org> Cr-Commit-Position: refs/heads/master@{#841589}
-
Richard Townsend authored
Attempts to fix an ASAN-detected crash for IsPrefetchOnly() Documents. Bug: 901056, 1164226, 1160665, 1164377 Change-Id: I74c75c58d3e2d9319f67997e3b08d1ab7d5e008d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618362Reviewed-by:
Mason Freed <masonfreed@chromium.org> Commit-Queue: Richard Townsend <richard.townsend@arm.com> Cr-Commit-Position: refs/heads/master@{#841588}
-
Owen Min authored
Using if defined instead of idef, and include build/build_config.h References: https: //chromium.googlesource.com/chromium/src/+/master/styleguide/c++/c++.md#platform_specific-code Change-Id: I1336313e002eeee85496d31089349826a60fc34a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618398Reviewed-by:
Zach Trudo <zatrudo@google.com> Commit-Queue: Owen Min <zmin@chromium.org> Cr-Commit-Position: refs/heads/master@{#841587}
-
David Grogan authored
When deriving flex base size of an svg that has an aspect ratio but no natural height or width, we were ignoring min/max sizes specified in the cross-axis direction, even though they should transfer through the aspect ratio and restrict the stretch fit into the available size. Bug: 1162704 Change-Id: If502de43a876e41e6f3784aea089edcd2467ba60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2614470Reviewed-by:
Christian Biesinger <cbiesinger@chromium.org> Commit-Queue: David Grogan <dgrogan@chromium.org> Cr-Commit-Position: refs/heads/master@{#841586}
-
Matthew Porter authored
This change adds a check for the system animation setting prior to animating. This ensures when users explicitly opt into having no animations, that we honor that preference. Change-Id: I2a63a9ea40566932005a3e32b8ee061d9fc879a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2617199Reviewed-by:
Caroline Rising <corising@chromium.org> Commit-Queue: Matthew Porter <matt.porter@microsoft.com> Cr-Commit-Position: refs/heads/master@{#841585}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/f5aed172c693..fafb47739a31 2021-01-08 borenet@google.com [infra] Filter PathKit and CanvasKit tryjobs when cutting Chrome branch 2021-01-08 nifong@google.com debug build for wasm gm tests 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 johnstiles@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: johnstiles@google.com Change-Id: I5e6917f6c08320260e5667d7475d0d09529536d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618229Reviewed-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@{#841584}
-
Leonard Grey authored
Bug: 1152274 Change-Id: I68caf298c2009923b450619cd6ebb0ad4b94870d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2615203Reviewed-by:
Andrey Kosyakov <caseq@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Commit-Queue: Leonard Grey <lgrey@chromium.org> Cr-Commit-Position: refs/heads/master@{#841583}
-
Gavin Williams authored
Extending to M91 for new enterprise printer status icons introduced in M89. Change-Id: I7c51781d77aa6a5a575460bcd2a03d80566a3533 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2616984 Auto-Submit: Gavin Williams <gavinwill@chromium.org> Reviewed-by:
Zentaro Kavanagh <zentaro@chromium.org> Commit-Queue: Zentaro Kavanagh <zentaro@chromium.org> Cr-Commit-Position: refs/heads/master@{#841582}
-
Brandon Wylie authored
TBR=blundell@chromium.org Bug: 1164414 Change-Id: Iabfd418962724d2ce28f44a9b4d1ef549d038c9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618364 Commit-Queue: Brandon Wylie <wylieb@chromium.org> Auto-Submit: Brandon Wylie <wylieb@chromium.org> Reviewed-by:
Patrick Noland <pnoland@chromium.org> Cr-Commit-Position: refs/heads/master@{#841581}
-
Zhenyao Mo authored
1) GPU switching is considered and this CL made sure the hardware GPU info displayed in the about:gpu is the last active GPU before Chrome falls back to SwiftShader. 2) Don't put SwiftShader info into hardware GPU section. Before this CL, if we run Chrome with GPU acceleration off, SwiftShader ended up in the hardware GPU section. BUG=1154047 TEST=manual, gpu bots R=kbr@chromium.org Change-Id: I08ea41a25d40610e0d13da83f8b5dfeb50011b57 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2613741Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Zhenyao Mo <zmo@chromium.org> Cr-Commit-Position: refs/heads/master@{#841580}
-
Ryan Sturm authored
Since there can be a time gap between when the url loader interceptor is handed off to content/ and when the throttles allow the request to proceed, there is a possibility of forwarding_client_ not being set up while the streaming request pointer is null. I suspect this is where the crash is coming from. Bug: 1164190 Change-Id: I1e68fa7898737ba71b68ec681903b88ece88c8d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2617858 Commit-Queue: Tarun Bansal <tbansal@chromium.org> Auto-Submit: Ryan Sturm <ryansturm@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Cr-Commit-Position: refs/heads/master@{#841579}
-
Gil Dekel authored
This CL updates the display configurator API and tests to reflect unified modeset testing. Bug: b:176819129 Test: display_unittests && ozone_unittests Change-Id: Ib87bd884457320b0fafd764d818bb3b2b56d7364 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2613152 Commit-Queue: Gil Dekel <gildekel@chromium.org> Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#841578}
-