- 01 Dec, 2020 40 commits
-
-
Andrew Xu authored
The bug was introduced by https://crrev.com/c/2542925 The problem is: the contents view's insets are ignored when setting a menu item's height. To solve this bug, all constants related to multipaste menu views are grouped in one file. It increases the code readability. Bug: 1154070 Change-Id: Ie44ecf40afd1796ce6d18ccd8be921c29ee79199 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2566448Reviewed-by:
David Black <dmblack@google.com> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Andrew Xu <andrewxu@chromium.org> Cr-Commit-Position: refs/heads/master@{#832513}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/356cef301b81..0c2cc2356170 2020-12-01 mtklein@google.com rearrange types in SkRuntimeEffect program_fn() 2020-12-01 herb@google.com use SkGlyphRect to record subrun bounds 2020-12-01 csmartdalton@google.com Extract reusable functions from stroke tessellation shaders 2020-12-01 mtklein@google.com disambiguate skvm::bit_cast() 2020-12-01 ethannicholas@google.com Allow SkASSERTF to take zero varargs parameters 2020-12-01 mtklein@google.com remove "half" term from SkVM 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 westont@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: westont@google.com Change-Id: Ibb28e22d160aa26545d22337452060844e5b9bf6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568370Reviewed-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@{#832512}
-
chromium-autoroll authored
Roll Chrome Linux PGO profile from chrome-linux-master-1606823843-898956163ed2fa02f28039f4033baf36c9ffa10d.profdata to chrome-linux-master-1606845551-c0991c25d04e0fb7cdc34afe442412c8219bff33.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: I666dfd585e6944b56aaf70ac5418fce90820c450 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567048Reviewed-by:
-
Elly Fong-Jones authored
Bug: 1154345 Change-Id: I87e53f807e7682a171a5e5f9850e9e09d96649d3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568436 Commit-Queue: Robert Liao <robliao@chromium.org> Reviewed-by:
Robert Liao <robliao@chromium.org> Cr-Commit-Position: refs/heads/master@{#832510}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1606823843-0f5277758f530be04bbb2f9dce57100bc533b372.profdata to chrome-mac-master-1606845551-f7436cdc1d8a17c203d7167ce8ba0cc00b1d3773.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: I8e002f119c3fde36344ab1a77469653e12978749 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568410Reviewed-by:
-
Dave Tapuska authored
Since ScheduleAnimation has moved inside blink we no longer need the intermediate RenderWidget for WebPagePopups anymore. BUG=1097816 Change-Id: Icba7c74a025f5bb7edb5b4f1baf38f75f2417555 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2562959Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
danakj <danakj@chromium.org> Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Cr-Commit-Position: refs/heads/master@{#832508}
-
Aleks Totic authored
This fix makes Legacy match TablesNG/FF. It fixes a corner case: - when cell percentage width is equal to percentage to total percentage width do not use cell's percentage to compute table's intrinsic width. Bug: 958381 Change-Id: Icc8fac3678cf40ea8ae693a2a19735a74bf24c38 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568262Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Aleks Totic <atotic@chromium.org> Cr-Commit-Position: refs/heads/master@{#832507}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/42433abb9596..6d300e3738db 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: Iae65cfc4950d5c072376fb1df4f556976a15be4f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568214Reviewed-by:
-
Max Curran authored
page load. This CL adds tracking of translate errors over the course of a page load. This summary includes the first translation error and the total number of errors. This information will be later added to the new Translate UKM (see design doc for full details). Full design doc: https://docs.google.com/document/d/1dyWh1Xw5VgUA00VA-5PTgKQ6ItziPBnSyeDR8saJ9vM/edit?usp=sharing Bug: 1114868 Change-Id: I92b4912cd175c6e5943c24e095d42eb8091c2e14 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2556339 Commit-Queue: Max Curran <curranmax@chromium.org> Reviewed-by:
Ryan Sturm <ryansturm@chromium.org> Reviewed-by:
Scott Little <sclittle@chromium.org> Cr-Commit-Position: refs/heads/master@{#832505}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/efb716af67f6..225d4f420c39 2020-12-01 changhaohan@chromium.org Sort HAR exported logs by startedDateTime 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: If4561a515bc41274311ccabbfa4784d2189ed6ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567743Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/3c1a040a0ffb..d7b599b52009 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 japhet@google.com,gab@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: None Tbr: japhet@google.com,gab@google.com Change-Id: I97a49ddd8165090e41050266153d2804a9559c8f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567741Reviewed-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@{#832503}
-
Josh Nohle authored
Records whether or not a Bluetooth MAC address is set in the local device's private certificate metadata during certificate creation. Note: A missing Bluetooth MAC address is currently not considered necessary for a certificate, and certificate creation can succeed without one. Bug: 1122641, 1105579 Change-Id: I78fa2a1225568a4912db1e995c247bdd7d27ce46 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2563677 Commit-Queue: Josh Nohle <nohle@chromium.org> Reviewed-by:
Weilun Shi <sweilun@chromium.org> Reviewed-by:
James Vecore <vecore@google.com> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#832502}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/a3bcd1c0e2e9..6d300e3738db 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: I58d1b402b48ad5d975e58b40e9def6f3b5f23650 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568255Reviewed-by:
-
Peter Wen authored
This reverts commit 625caaa3. Reason for revert: Failed https://ci.chromium.org/ui/p/chromium/builders/ci/android-archive-rel/17017/overview Original change's description: > Android: Reduce deps for prebuilts > > Prebuilt jars do not need the full classpath since they are either jars > ready to be passed to ijar, or they just need a dep on a non-java target > to unzip the jar from its aar. > > Previously header jars could depend on impl jars due to passing the full > classpath for prebuilt jars, but this should not happen as it defeats > the purpose of header jars being fast to compile. Added a regression > test to ensure chrome_java__header doesn't depend on base_java__impl. > > Bug: 1154302 > Fixed: 1154302 > Change-Id: I896490bf99bf62777c083f0766064c734484977b > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567618 > Reviewed-by: Clark DuVall <cduvall@chromium.org> > Commit-Queue: Clark DuVall <cduvall@chromium.org> > Commit-Queue: Peter Wen <wnwen@chromium.org> > Auto-Submit: Peter Wen <wnwen@chromium.org> > Cr-Commit-Position: refs/heads/master@{#832488} TBR=wnwen@chromium.org,cduvall@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com Change-Id: Ib4032d0a2ee8cedf8e5f5a645d25824a1adaeda3 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1154302 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2566305Reviewed-by:
Peter Wen <wnwen@chromium.org> Commit-Queue: Peter Wen <wnwen@chromium.org> Cr-Commit-Position: refs/heads/master@{#832500}
-
Gordon Seto authored
Create cellular setup iconset and move activation code page icons into the iconset. Bug: 1093185 Change-Id: I06fe411ecf059d180b3f999279052e87b888bbf3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2566354 Commit-Queue: Gordon Seto <gordonseto@google.com> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#832499}
-
Natalie Chouinard authored
TBR=fhorschig@chromium.org Bug: 1154362 Change-Id: I087f1a05e800144414051c01bd9f9e09d1b53a87 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567499Reviewed-by:
Natalie Chouinard <chouinard@chromium.org> Commit-Queue: Natalie Chouinard <chouinard@chromium.org> Cr-Commit-Position: refs/heads/master@{#832498}
-
Xing Liu authored
Use the Reading list folder icon on bookmark bottom sheet and main bookmark UI. Bug: 1149664 Change-Id: I4a28f62df8f678a1a72c422576b76b5ffdc42eea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2553341 Commit-Queue: Xing Liu <xingliu@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Shakti Sahu <shaktisahu@chromium.org> Cr-Commit-Position: refs/heads/master@{#832497}
-
Jamie Madill authored
Revert "Fix readPixels incorrectly allowing RGBA / UNSIGNED_SHORT without EXT_texture_norm16 support" This reverts commit 80b096ab. Reason for revert: Causing failure on ANGLE bots. See bug. Bug: chromium:1154356 Original change's description: > Fix readPixels incorrectly allowing RGBA / UNSIGNED_SHORT without EXT_texture_norm16 support > > Add readPixels validation for RGBA / UNSIGNED_SHORT combination. This is > only valid with EXT_texture_norm16 extension enabled. > > Bug: 1152259 > Change-Id: I0e10b7d29f3b362c4054500270bbad87dcde599f > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2559797 > Commit-Queue: Shrek Shao <shrekshao@google.com> > Reviewed-by: Kenneth Russell <kbr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#832141} TBR=kbr@chromium.org,jdarpinian@chromium.org,shrekshao@google.com,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com Change-Id: If71af6582a51aeee39541a4e1a0c693162ba7f12 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1152259 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568438Reviewed-by:
Jamie Madill <jmadill@chromium.org> Commit-Queue: Jamie Madill <jmadill@chromium.org> Cr-Commit-Position: refs/heads/master@{#832496}
-
Vladimir Levin authored
This patch ensures that we property check that hidden-matchable children should be skipped. This only affects hidden-matchable, because hidden hides everything to the buggy if statement would work and auto allows all activations so the result of the buggy return is the same as it would have been without the bug. The effect of this bug is that hidden-matchable children are exposed to accessibility, which they shouldn't be. R=chrishtr@chromium.org, jarhar@chromium.org Change-Id: I863889889cb28e4d3ab075f599f7660dc8637cff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567342Reviewed-by:
Joey Arhar <jarhar@chromium.org> Commit-Queue: vmpstr <vmpstr@chromium.org> Cr-Commit-Position: refs/heads/master@{#832495}
-
Karthika Pai authored
This is part of a migration that replaces the old <histogram-suffixes> syntax that was used to denote groups of histogram to the new patterned histogram syntax. Bug: 758782 Change-Id: I6cde5e15fb8d43b58006569ca01cab5765fb79e3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2552631Reviewed-by:
-
Ben Wagner authored
I happened to notice while running this benchmark locally that the "Call" button was still active and the "Hang Up" button was inactive. After investigating the original test page, this indicates the benchmark wasn't actually testing anything. I checked at a revision before https://chromium-review.googlesource.com/c/chromium/src/+/2560261 was submitted and saw the same thing. This story now appears to work correctly when running locally on Mac. Change-Id: I700d1a25b9b58caed5109575d12c18b84bafd519 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2563662 Auto-Submit: Ben Wagner aka dogben <benjaminwagner@google.com> Reviewed-by:
Mirko Bonadei <mbonadei@chromium.org> Reviewed-by:
John Chen <johnchen@chromium.org> Commit-Queue: John Chen <johnchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#832493}
-
Jesse Schettler authored
Limit the arc_property_util_expand_property_contents_fuzzer input size to avoid timing out on ClusterFuzz. Bug: 1153405 Change-Id: Id1ea39f7544fc95355fd39b5a291f9538d68a137 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567817 Auto-Submit: Jesse Schettler <jschettler@chromium.org> Commit-Queue: Yusuke Sato <yusukes@chromium.org> Reviewed-by:
Yusuke Sato <yusukes@chromium.org> Cr-Commit-Position: refs/heads/master@{#832492}
-
Xianzhu Wang authored
Previously during a translation animation, as the animation didn't have scale, we would fallback to use the native scale. In cases that the animating element had a big accumulated scale from ancestors, the scale would be too small compared to the ideal scale. Another failure case was that when a big animation scale would cause the rasterized layer to be larger than the viewport, we would also fallback to use the native scale, which might be also too small if the layer had a big accumulated scale from ancestors. Now don't adjust scale for transform animation if the animation doesn't animate scale. And don't fallback to native scale when the scale is too big, but calculate a scale that just makes the rasterized layer not larger than the viewport. Bug: 1153428 Change-Id: I4a4f3133b01099752629f6710c8375a7b715ab0b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2566053Reviewed-by:
vmpstr <vmpstr@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#832491}
-
Michael Thiessen authored
We need to actually launch Settings for the workaround to work, so to make sure later tests don't fail because the settings workaround was already applied, we need to return to the launcher after launching settings. I'm not actually sure about anything I just said though, as these flakes are like 1/100 and while I couldn't repro locally after this fix they could still be present. Example flake here on MainSettingsFragmentTest: https://ci.chromium.org/p/chromium/builders/ci/Lollipop%20Phone%20Tester/28012 Bug: 1152413 Change-Id: I1dd77366c2eb9c422dbe75e3efecb3e29ed00920 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2566352 Commit-Queue: Michael Thiessen <mthiesse@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Cr-Commit-Position: refs/heads/master@{#832490}
-
Peter Kotwicz authored
This CL introduces android_nocompile_test_suite() and android_nocompile_library() build rules. The android_nocompile_test_suite() template tries to compile its dependent android_nocompile_library() targets and checks that: - The compile fails - The compile output contains the error message specified in the android_nocompile_library() template. The android_nocompile_library() uses a temporary output directory so that compiling "all" still works. The CL converts |errorprone_plugin_tests| to use android_nocompile_test_suite(). BUG=1132014 Change-Id: I80a372a06a1fa7fa54546ac3ca0a1c48e8ee96ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2538313Reviewed-by:
Dirk Pranke <dpranke@google.com> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org> Cr-Commit-Position: refs/heads/master@{#832489}
-
Peter Wen authored
Prebuilt jars do not need the full classpath since they are either jars ready to be passed to ijar, or they just need a dep on a non-java target to unzip the jar from its aar. Previously header jars could depend on impl jars due to passing the full classpath for prebuilt jars, but this should not happen as it defeats the purpose of header jars being fast to compile. Added a regression test to ensure chrome_java__header doesn't depend on base_java__impl. Bug: 1154302 Fixed: 1154302 Change-Id: I896490bf99bf62777c083f0766064c734484977b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567618Reviewed-by:
Clark DuVall <cduvall@chromium.org> Commit-Queue: Clark DuVall <cduvall@chromium.org> Commit-Queue: Peter Wen <wnwen@chromium.org> Auto-Submit: Peter Wen <wnwen@chromium.org> Cr-Commit-Position: refs/heads/master@{#832488}
-
Lukasz Anforowicz authored
This CL removes code that used to log the 'Navigation.TimeToCommit' UMA metrics which have expired on 2018-03-30 (in favor of Navigation.StartToCommit variants). This CL also removes code that used to log the 'Navigation.TimeToURLJobStart' UMA metrics which have expired in M85. This CL removes fields that were used for supporting the removed UMA metrics, including the `url_job_start_time_` field. Since unit tests would never simulate NavigationURLLoaderDelegate::OnRequestStarted they would always exit early from Navigator::RecordNavigationMetrics. After removal of the field, the early exit no longer happens in unit tests, which makes them more closely follow/simulate the behavior of the production code. This CL also introduces a small change in behavior of the production code related to logging an "Unload" UKM event during session restore. This change seems okay, since that both before and after this CL, that UKM event would be logged when restoring a tab, when navigating an empty tab via omnibox, and in other scenarios where there is no real "unload" event (i.e. it seems okay not to special-case session restore here). The removal also covers the 6 suffixes and so also removes: Navigation.TimeToCommit_SessionRestored_BeforeUnloadDiscounted Navigation.TimeToURLJobStart_SessionRestored_BeforeUnloadDiscounted Navigation.TimeToCommit_NewRenderer_BeforeUnloadDiscounted Navigation.TimeToURLJobStart_NewRenderer_BeforeUnloadDiscounted Navigation.TimeToCommit_ExistingRenderer_BeforeUnloadDiscounted Navigation.TimeToURLJobStart_ExistingRenderer_BeforeUnloadDiscounted The removal should help consolidate the content::RestoreType::CURRENT_SESSION and content::RestoreType::LAST_SESSION enum values (because code logging the metrics was the only place that distinguished these values). Bug: 1150940 Fixed: 1030145, 1030141 Change-Id: I2036e6884b90dccfc5cc6588e3b8a5a867ee7670 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2551736 Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Reviewed-by:
Charlie Harrison <csharrison@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Auto-Submit: Łukasz Anforowicz <lukasza@chromium.org> Cr-Commit-Position: refs/heads/master@{#832487}
-
Robert Ma authored
This only affects the Chromium log formatter of wptrunner. We want to produce a valid metadata and full logs separately, the former as the "-expected.txt" artifact and the latter as "-stderr.txt". Bug: 1154085 Cq-Include-Trybots: luci.chromium.try:linux-wpt-identity-fyi-rel,linux-wpt-input-fyi-rel Change-Id: I059e05005d2b5f72708c783c5c81deaa86f8b417 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567094 Commit-Queue: Robert Ma <robertma@chromium.org> Reviewed-by:
Luke Z <lpz@chromium.org> Cr-Commit-Position: refs/heads/master@{#832486}
-
James Cook authored
Make the path sanitization code in DownloadPrefs more closely match the version used by ash-chrome (existing chrome for chromeos). There's still more refactoring work to do to make the behavior match exactly, but this lets users have a bit more flexibility with their download location. Bug: 1148848 Test: added to unit_tests Change-Id: I54048b60db3191f49187bf7645384f4d2a95218d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2566360Reviewed-by:
Xing Liu <xingliu@chromium.org> Commit-Queue: James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#832485}
-
Ivan Murashov authored
Using auto for a type in declaration of a constant previously declared with a clearly specified type considered by GCC as a type mismatch. An error example: ../../base/threading/hang_watcher.cc:44:39: error: conflicting declaration 'constexpr const auto base::HangWatchScopeEnabled::kDefaultHangWatchTime' ../../base/threading/hang_watcher.h:68:32: note: previous declaration as 'const base::TimeDelta base::HangWatchScopeEnabled::kDefaultHangWatchTime' Now the declaration of kDefaultHangWatchTime in the cc file matched to the declaration in the header file. Bug: 819294 Change-Id: I108a771f9c8023cb13470ba0a4eaf6207e32b522 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2565578Reviewed-by:
Gabriel Charette <gab@chromium.org> Reviewed-by:
Oliver Li <olivierli@chromium.org> Commit-Queue: Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#832484}
-
kylechar authored
All the tests under SurfaceAggregatorPerfTest.* are currently producing an empty aggregated frame. The TransferableResources created are invalid andtThe resources are all rejected by DisplayResourceProvider. This early exits aggregation at the first child frame containing resources, which produces an empty result. Fix the tests by specifying the correct resource type and including a mailbox. Also add a check to the tests that verifies the number of RenderPasses and DrawQuads after aggregation is correct. Only verify during warmup runs so this has no impact on performance. Bug: 1154343 Change-Id: I78d841137a22e3b55e842350059e1a4cbaa168ff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567621Reviewed-by:
Sean Gilhuly <sgilhuly@chromium.org> Commit-Queue: kylechar <kylechar@chromium.org> Cr-Commit-Position: refs/heads/master@{#832483}
-
Max Curran authored
milliseconds to match the data being recorded. The stated units of OfflineIndicator.ShownDuration were seconds[1], but the data being reported was in milliseconds[2]. The Java interface for recording time histograms requires the durations to be stored in longs with units of milliseconds, so this change switches the units of the histogram to match the reported data. [1] https://uma.googleplex.com/p/chrome/histograms?sid=005d3b5589e4a01a7df40fefea7a5b3c [2] https://source.chromium.org/chromium/chromium/src/+/master:chrome/android/java/src/org/chromium/chrome/browser/offlinepages/indicator/OfflineIndicatorControllerV2.java;l=142 Bug: 1151504 Change-Id: Ie55abc479d29d048201036c8c0b176f0f9f2f836 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2552896Reviewed-by:
Sinan Sahin <sinansahin@google.com> Reviewed-by:
-
Zhaoyang Li authored
This is a follow up of crrev/c/2547921 to land the configs in correct sequence so CLs can pass CQ. Bug: 1090188 Change-Id: I67a766fc6baa99f596ab1e818e0dbaf9b6c1aadf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2566333Reviewed-by:
Yuke Liao <liaoyuke@chromium.org> Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org> Cr-Commit-Position: refs/heads/master@{#832481}
-
Francois Doray authored
Today, PageNode::IsLoading() transitions to "true" when a response is received for a main frame different-document navigation (WebContentsObserver::DidReceiveResponse()). It transitions to "false" when the load has stopped (WebContentsObserver::DidStopLoading()) and the page has been idling for a short timeout. This implies that PageNode::IsLoading() is "false" between when a navigation starts and when the initial response is received. We want to build a policy that preempts BEST_EFFORT tasks when any page is loading. If we use PageNode::IsLoading() to build that policy, BEST_EFFORT tasks will still be able to execute between when a navigation starts and when the initial response is received. This is undesirable, because BEST_EFFORT tasks could still interfere with navigation. This CL solves the issue by replacing PageNode::IsLoading() with PageNode::GetLoadingState(). This method returns an enum: - kLoadingNotStarted: No top-level document has started loading yet. - kLoading: A different top-level document is loading. This correspond to WebContents::IsLoadingToDifferentDocument(). - kLoadedBusy: A different top-level document finished loading, but the page did not reach CPU and network quiescence since then. - kLoadedIdle: The page reached CPU and network quiescence after loading the current top-level document, or the load failed. In a different CL, we will preempt BEST_EFFORT tasks when any page is kLoading or kLoadedBusy. Bug: 887407 Change-Id: Ie88a56457309aa86221f1ea31f7ceda731547b07 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2300400 Commit-Queue: François Doray <fdoray@chromium.org> Reviewed-by:
Joe Mason <joenotcharles@chromium.org> Cr-Commit-Position: refs/heads/master@{#832480}
-
Ahmed Fakhry authored
This CL adds recording UMA histograms for reasons that lead to an ongoing video recording to end. This CL also fixes a flaky test. BUG=1142994, 1141927 TEST=Modified existing tests Change-Id: I97db6dadc0a63d98dc75b43fd7696115060b310b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2559273 Commit-Queue: Ahmed Fakhry <afakhry@chromium.org> Reviewed-by:
Sammie Quon <sammiequon@chromium.org> Reviewed-by:
-
Ben Joyce authored
This causes blank test_logs (which may come when a test crashes) to just be <pre></pre> causing the summary to think there is content. Bug: 1151186 Change-Id: Ie31dcaa4d7ed0d7318eb2e2485b71147f00fc36c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2566694Reviewed-by:
Nodir Turakulov <nodir@chromium.org> Commit-Queue: benjamin joyce <bjoyce@chromium.org> Cr-Commit-Position: refs/heads/master@{#832478}
-
Gil Dekel authored
This CL consolidates all the UMA logic from configure_displays_task.cc into helper functions to help reduce the cognitive load when sifting through the task's logic. No functional changes. Test: Change-Id: I947c56153ef5ad9799efea67e1cbb2f4674dba9f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2566293Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Reviewed-by:
Daniele Castagna <dcastagna@chromium.org> Commit-Queue: Gil Dekel <gildekel@chromium.org> Cr-Commit-Position: refs/heads/master@{#832477}
-
Ryan Sturm authored
This CL adds report_raw_headers to all search prefetch requests. When the request is being served, the raw headers are stripped unless the intercepted request also has report_raw_headers set. This allows dev tools to see the request headers correctly without special handling to tie a prefetch request to a specific tab. Bug: 1142014 Change-Id: I619374e424a74286ffdafdb184d1ffd7a2b74763 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2559283 Commit-Queue: Ryan Sturm <ryansturm@chromium.org> Reviewed-by:
Robert Ogden <robertogden@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#832476}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/6d2a0fef9315..6c54473c3710 2020-12-01 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). 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: Iba655744290f13472f2f915c265e8105606cdccb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567742Reviewed-by:
-
Thomas Guilbert authored
This CL reduces variablity in the video-currentTime.html test by waiting until we decode the first frame before playing the video, and then waiting for the play() promise to resolve before starting at timer to check the currentTime. Bug: 1006852 Change-Id: I3c0d9817f3f77f2a0bf085917f578bc11fd19b3a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567570 Commit-Queue: Thomas Guilbert <tguilbert@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#832474}
-
