- 12 Oct, 2020 40 commits
-
-
lonyele authored
When selection is happening, apply text-decoration-color from selection pseudo style to the selected element Bug: 1110393 Change-Id: I3829c7071b85458c43975d622f0913b8f8c64fd7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2383212Reviewed-by:
Stephen Chenney <schenney@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Commit-Queue: Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#816130}
-
Nico Weber authored
Normally, we allow running several links in parallel if there's enough memory, since links tend to be memory- and io-bound, not compute bound. However, in LTO builds the linker does codegen for every linked translation unit, which needs a lot of CPU. Previously, we used to hardcode 8 threads per link for thinlto builds, which makes builds needlessly slow on machines with many cores. Instead, automatically use all cores for a thinlto link, but only run one link in parallel at once. chromeos-chrome-9999.ebuild in the Chrome OS build and link_jobs_32 in mb_config.pyl currently manually set the number of threads per lto link to the number of cores. Once this change here is in, we should stop explicitly setting the arg there and then we can turn this from a gn arg to a regular variable that's not settable in args.gn Bug: 1132930 Change-Id: If2fda3e38b2b1827beb2da844f024f52211210db Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2464782Reviewed-by:
Hans Wennborg <hans@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Auto-Submit: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#816129}
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC cr-fuchsia+bot@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast Tbr: cr-fuchsia+bot@chromium.org Change-Id: I6892611036fe227ce0b4437dd8206494367e1571 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2465686Reviewed-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@{#816128}
-
Igor authored
This will disallow the usage of Lacros browser by default to managed users. For unmanaged users Lacros will be available. Also it will be available for users where the admin set the policy LacrosAllowed to true. BUG=chromium:1136199 TEST=Manual test on device Change-Id: I60554ab7ed7813207aa602eb17801a4e82be47d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2456808 Commit-Queue: Igor <igorcov@chromium.org> Reviewed-by:
Bartosz Fabianowski <bartfab@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Reviewed-by:
Igor <igorcov@chromium.org> Cr-Commit-Position: refs/heads/master@{#816127}
-
Stephen Chenney authored
For tiled image painting the image was not correctly oriented. Fix it by pre-orienting the image before creating the tiling shader. The test still fails due to a lack of fuzzy matching, but the result is now correct. See external/wpt/css/css-images/image-orientation/image-orientation-background-properties.html Bug: 1066634 Change-Id: Ie0a2f534bf760174d337fdaa6838e82b33280d46 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2464902Reviewed-by:
Fredrik Söderquist <fs@opera.com> Commit-Queue: Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#816126}
-
Yuki Shiino authored
This is a follow-up of https://crrev.com/c/2418513. We need to intercept getcwd and realpath, which allocate memory internally. The reason is the same as 2418513. Bug: 1111332 Change-Id: I50c43056609b69020dc84bf181ec6247067cb982 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2438093 Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Reviewed-by:
Will Harris <wfh@chromium.org> Reviewed-by:
Benoit L <lizeb@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#816125}
-
Anders Hartvoll Ruud authored
This is only used by test code, and it's standing in the way of implementing tree-scoped references, so this CL removes this capability. Most of the tests could be fixed with just a simple Reset (for example: BasicCycle). This means that the cascade is empty after each Reset, so those tests are no longer implicitly testing that declarations appearing later overwrite those that appear earlier. But that's OK, there are still loads of tests which cover this explicitly. RevertInKeyframeResponsive is supposed to test what happens when --x changes during an animation that depends on --x _via_ revert. So here we can't just do an plain Reset, we need to re-add all the other declarations as well, to simulate a situation where only --x changed. Then there were a few tests which for some reason calculate the animation update and _then_ Add stuff to the MatchResult (for example: AnimatingVarReferences). This does not happen in production. Moved the Add calls to before the first Apply call. Change-Id: I00c3b26cbd7b9581e1bd61b5cd27163ebe651b92 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2464935Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#816124}
-
Ehimare Okoyomon authored
Screenshot: https://crbug.com/1136533#c1 Bug: 1136533 Change-Id: I6140f9e49a723afd0dd4ae22b059784b2cf73d2f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2461308 Commit-Queue: Ehimare Okoyomon <eokoyomon@chromium.org> Reviewed-by:
Clark DuVall <cduvall@chromium.org> Reviewed-by:
Christian Dullweber <dullweber@chromium.org> Cr-Commit-Position: refs/heads/master@{#816123}
-
Eric Seckler authored
Currently, base::CPU::GuessCoreTypes() is called in multiple places and executes the same code multiple times, even though the result is constant. There's already some static caching in different places. This patch moves the static caching into base::CPU::GuessCoreTypes() and renames it to base::CPU::GetGuessedCoreTypes(). Bug: 1081760 Change-Id: Ifaff01cc19abc48a36d5fe19bc4cb9a9cfa4fd24 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2463309 Commit-Queue: Eric Seckler <eseckler@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#816122}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/9024c3764962..ac0366e76f36 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 amraboelkher@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: amraboelkher@google.com Change-Id: If146743d69e69ea72e8f52539482c7cfbbe0e4e0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2465922Reviewed-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@{#816121}
-
Marc Treib authored
It was unused. Bug: 647505 Change-Id: I19b16e8a5c99d0c490e8e0df05ec29985d98b7cb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2463918Reviewed-by:
Maksim Moskvitin <mmoskvitin@google.com> Commit-Queue: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#816120}
-
Finnur Thorarinsson authored
This change of function contract is the by-product of a discussion on fixing issue 1130909, where we decided to do a bit of additional cleanup as well. Bug: 1130909 Change-Id: I28d0e244ead44b8f6525bf1e0d86633256d06281 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2456786Reviewed-by:
Peter Conn <peconn@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Gang Wu <gangwu@chromium.org> Commit-Queue: Finnur Thorarinsson <finnur@chromium.org> Cr-Commit-Position: refs/heads/master@{#816119}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/68bd685a7643..dec35c569444 2020-10-12 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Chromium from 77bfcdcd to efbcef25 (569 revisions) 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 ynovikov@chromium.org 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: ynovikov@chromium.org Change-Id: Ib16c6154813710d0a5b60de4b176b7f1dbdc0cb0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2462740Reviewed-by:
-
Victor Hugo Vianna Silva authored
The code to migrate sync.local_device_guids to the new sync.local_device_guids_with_timestamp has been active for 1 year (crrev.com/1827435), so it can be removed now. TBR=treib@chromium.org TBR=droger@chromium.org Fixed: 994339 Change-Id: If6fed35ada178808a4171d790f51451f5a8192df Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2464934 Commit-Queue: Victor Vianna <victorvianna@google.com> Reviewed-by:
Marc Treib <treib@chromium.org> Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#816117}
-
Fredrik Söderqvist authored
This allows "content negotiation" to detect support for SVG favicons. Bug: 1026564 Change-Id: I612a08872f16bdb0dc71b9779090b5759806f815 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1926312 Commit-Queue: Fredrik Söderquist <fs@opera.com> Reviewed-by:
David Benjamin <davidben@chromium.org> Reviewed-by:
Mathias Bynens <mathias@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#816116}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/07b0b1dc..26d93a4d 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: Ib963131764aef6cec54151d7f9ea26f6bd8e1859 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2465670Reviewed-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@{#816115}
-
Victor Hugo Vianna Silva authored
Before this CL, screenreaders would read the buttons in the sync consent dialog, but wouldn't read the text content unless the user focused it with the mouse. With this CL, we ensure that at least the dialog title ("Turn on sync?") is read once before the buttons. Screencast: crbug.com/1130433#c3 Fixed: 1130433 Change-Id: I2dbdae2489be7672bd871a63384db2885d1bfcc1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2465842Reviewed-by: -
Paula Vidas authored
This is necessary for two client tests that use the new invalidations system. Different clients need different tokens because the (fake) server will use the tokens to determine invalidations recipients. Bug: 1135167 Change-Id: I0f60de8d27ad6b6a338818cde530df2f860c056f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2461012Reviewed-by:
Rushan Suleymanov <rushans@google.com> Reviewed-by:
-
Anders Hartvoll Ruud authored
As far as I can tell, this check exists to ensure that complex Shadow DOM v0 selectors don't cross any boundaries they shouldn't (see Issue 360679). The problem is that for e.g. ::part(foo):is(:focus), the :focus part is detected as an illegal boundary crossing, since the TreeScope of context.scope and context.element are different. This function doesn't seem entirely right to me, but at this point I want to touch Shadow DOM v0 as little as possible, since it's very close to being removed. Hence I'm basically just disabling the check for :is/:where. Bug: 568705 Change-Id: I2febcd37c9772b11f91ae93df87acb7649a8de91 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2464263Reviewed-by:
-
sandromaggi authored
This CL adds a new web-action to get the attribute of an element. This is required for extending the |GetElementStatusAction| to also handle the text content of an element. The attributes can be nested. Bug: b/169924567 Change-Id: Id5ff86d907d34d8cbf8e56aa8dfd377fe8f934bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2463233Reviewed-by:
Stephane Zermatten <szermatt@chromium.org> Reviewed-by:
Luca Hunkeler <hluca@google.com> Commit-Queue: Sandro Maggi <sandromaggi@google.com> Cr-Commit-Position: refs/heads/master@{#816111}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/3326535126e4..72cc54c5b852 2020-10-12 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 9ef87d94..c67306a2 (815958:816064) 2020-10-10 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision d97ea1b0..9ef87d94 (815854:815958) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@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: webrtc-chromium-sheriffs-robots@google.com Change-Id: I1fa3a78ee3b705d6cf952a196a77023c03c059b4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2462739Reviewed-by:
-
Marc Treib authored
The hope is that this will resolve test flakiness; see linked bug. Bug: 1136758 Change-Id: I78697c296d21a4202e69b1aa9f9eb264f676317d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2463562 Commit-Queue: Marc Treib <treib@chromium.org> Reviewed-by:
Mohamed Amir Yosef <mamir@chromium.org> Cr-Commit-Position: refs/heads/master@{#816109}
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1602448744-d06fc1e3f11f340d5ab319c12d5a6fb4491c2b6c.profdata to chrome-win64-master-1602482293-b6c9af61d9b709e1e409c88a2a609d5546a5c2ce.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: Ib43a9e444cc25ec682c130f18dbad17f21008559 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2465644Reviewed-by:
-
Morten Stenshorne authored
Bug: 294205 Change-Id: Ief9e9bc948019a6d74ec15781e96dd3917879794 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2462261Reviewed-by:
-
Victor Hugo Vianna Silva authored
ProfileSyncService mostly creates the task runner and passes it to the engine, so this CL moves the creation to the engine. The one use of the runner by ProfileSyncService is replaced with posting a task to the thread pool. Bug: 1123881 Change-Id: Ifef2806b527424b30e2a0d6ef07cfca026ee07b1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2461325Reviewed-by:
-
Dmitry Gozman authored
Bug: 1137143 Change-Id: I0e28864a58cfd558e899eaa5c8ee4cebff559098 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2463605Reviewed-by:
Yang Guo <yangguo@chromium.org> Commit-Queue: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#816105}
-
Jiewei Qian authored
This is a reland of de6bbcbc The reland deletes EXPECT_DCHECK_DEATH to all launch tests, because death tests aren't reliable in browsertest. And manually test LaunchSystemWebApp behaves correctly in debug / DCHECK builds. Test=Manually verified debug build and release build behaves correctly. - When DCHECK is on: DCHECKs when launching with a wrong profile - When DCHECK is off: launches into an appropriate profile Original change's description: > system-web-apps: better handle incognito in LaunchSystemWebApp > > LaunchSystemWebApp used whatever profile is provided in the parameter to > create SWA windows and launching SWAs, even if the profile may not > suitable to host a SWA window. > > This CL adds logic to determine the appropriate profile if the provided > one is unsuitable. This serves as a mid-term solution for launching > SWAs, and acts as a safety net to prevent chrome crashing if unsuitable > profiles are provided. > > Specifically, it catches these two types of profiles: > - Guest session "original" profile: launch into guest session's > primary off the record profile (which is used for guest session > browsing and SWAs). > - Normal session incognito profile: launch into the original profile, > because we don't support incognito SWAs. > > Fixed: 1109594 > Change-Id: Ibe4a3b1bf7c811ef1ee02fd967307ad9bf070ee7 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423760 > Commit-Queue: Jiewei Qian <qjw@chromium.org> > Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org> > Cr-Commit-Position: refs/heads/master@{#814602} Change-Id: I5766a26c5376c7e59180e4d9dd2befe015c13e9f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2459010 Commit-Queue: Jiewei Qian <qjw@chromium.org> Reviewed-by:
Giovanni Ortuño Urquidi <ortuno@chromium.org> Cr-Commit-Position: refs/heads/master@{#816104}
-
Eric Willigers authored
Remove #include from source files that do not use ScopedFeatureList. Bug: 1137231 Change-Id: I61cdb2b1909662f048832e85cedffbe9dbaca18f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2463266 Auto-Submit: Eric Willigers <ericwilligers@chromium.org> Commit-Queue: Matt Falkenhagen <falken@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#816103}
-
Jérôme Lebel authored
ForceStartupSigninPromo flag should should not present the promo when being signed in. The flag test is moved after authentication test. Change-Id: Ib4cf710988b39726b9f4dbef80d44eb8f16fde98 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2462133 Auto-Submit: Jérôme Lebel <jlebel@chromium.org> Commit-Queue: Nohemi Fernandez <fernandex@chromium.org> Reviewed-by:
Nohemi Fernandez <fernandex@chromium.org> Cr-Commit-Position: refs/heads/master@{#816102}
-
Francois Beaufort authored
This CL moves some image capture web platform tests to secure contexts as getUserMedia is required to get access to photo-related settings and capabilities. It also removes a test in MediaStreamTrack-applyConstraints-fast.html as applyConstraints handles properly non-ImageCapture constraints. Bug: 1134569 Change-Id: I0b9e3e824bccc8f056c68735f8c04a94d0fc0c7f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2445209 Commit-Queue: François Beaufort <beaufort.francois@gmail.com> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#816101}
-
Koji Ishii authored
This patch changes |CSSParserFastPaths| so that `hyphens: auto` is accepted as a valid CSS when |USE_MINIKIN_HYPHENATION| is on, rather than only on Android. This patch has no behavior changes. Bug: 652964 Change-Id: Id5c4c92798a6b10292e7a2505515bb7efd48d1de Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2465412 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#816100}
-
chromium-autoroll authored
Roll Chrome Linux PGO profile from chrome-linux-master-1602460024-2af6533fe6c4354707f21413721100fe04991470.profdata to chrome-linux-master-1602482293-c39f07959f0e29f7d514a51869e00b511fbb2f8b.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: I74de475988eb83739aecbf57a72659f116ef8cb6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2465503 Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Reviewed-by:
-
Rakina Zata Amni authored
These tests do not intend to have failed navigations, but they actually failed silently, mostly due to 404s because of bad URLs. Soon (after crrev.com/c/2437714 lands) these tests will actually fail because of the failed navigations. This CL ensures that these navigations uses the correct URL, or disables the test in cases where that's not possible. Bug: 1133115 Change-Id: I4db7c06cfdd08ab8a4ccac3ca8fa51bc4b5917d3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2438550 Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#816098}
-
Kenichi Ishibashi authored
These test classes use ServiceWorkerRegistration. Move these classes and tests to service_worker_registry_unittest.cc so that service_worker_storage_unittest.cc can be moved to the Storage Service. ServiceWorkerRegistration can't be used from the Storage Service. The reason we had two classes was that one provided a way to simulate browser restart and the other didn't. Since there is no specific reason to keep that separation this CL merges these classes into one class (ServiceWorkerRegistryResourceTest). Bug: 1016064 Change-Id: I21367ebf817a81d9ccdf0b5e2042673e5093c553 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2463041Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Cr-Commit-Position: refs/heads/master@{#816097}
-
Monica Basta authored
Bug: 1063856 Change-Id: Ic1a10a9fd1924166f8c855ff0421df855b26122b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2441407 Commit-Queue: Monica Basta <msalama@chromium.org> Auto-Submit: Monica Basta <msalama@chromium.org> Reviewed-by:
Esmael Elmoslimany <aee@chromium.org> Cr-Commit-Position: refs/heads/master@{#816096}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/src/third_party/freetype2.git/+log/20186d1be641..82d331556ce7 2020-10-12 apodtele@gmail.com Unnest markdown. 2020-10-10 wl@gnu.org * Version 2.10.3 released. 2020-10-10 wl@gnu.org Document changes to last release. 2020-09-25 wl@gnu.org [autofit] Synchronize with ttfautohint. 2020-09-25 wl@gnu.org Move `scripts/make_distribution_archives.py` to `src/tools`. 2020-09-24 wl@gnu.org * src/cff/cffgload.c (cff_slot_load): Scale `vertBearingY`. 2020-09-24 wl@gnu.org * src/base/ftobjs.c (FT_Load_Glyph): Trace glyph metrics. 2020-09-22 wl@gnu.org [meson] Move auxiliary scripts to `builds/meson`. 2020-09-21 david.turner.dev@gmail.com Add python script for building tarballs. 2020-09-21 wl@gnu.org * scripts/extract_freetype_version.py: Fix regex typos. 2020-09-21 david.turner.dev@gmail.com Add Meson build project file. 2020-09-19 apodtele@gmail.com Documentation updates. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/freetype-chromium Please CC bungeman@google.com,drott@google.com,thestig@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_chromium_msan_rel_ng;luci.chromium.try:linux-blink-rel;luci.chromium.try:mac10.12-blink-rel;luci.chromium.try:win10-blink-rel;luci.chromium.try:win7-blink-rel Tbr: bungeman@google.com,drott@google.com,thestig@google.com Change-Id: I8e84ef063c07f9e89934f7566048f3e18b90d4e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2465225Reviewed-by:
Dominik Röttsches <drott@chromium.org> Commit-Queue: Dominik Röttsches <drott@chromium.org> Cr-Commit-Position: refs/heads/master@{#816095}
-
Eric Willigers authored
DesktopPWAsWithoutExtensions has shipped. Browser tests no longer need to be parameterized. Builds on https://chromium-review.googlesource.com/c/chromium/src/+/2454774 https://chromium-review.googlesource.com/c/chromium/src/+/2462343 Retire /BookmarkApps entries from testing/buildbot/filters/lacros.browser_tests.filter and rename /WebApps entries. Bug: 1065748 Change-Id: I0a6cc2f0b11303a5d3a2c75c7447e720d051e06f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2456466Reviewed-by:
Alexey Baskakov <loyso@chromium.org> Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Alexey Baskakov <loyso@chromium.org> Auto-Submit: Eric Willigers <ericwilligers@chromium.org> Cr-Commit-Position: refs/heads/master@{#816094}
-
Ilya Nikolaevskiy authored
Bug: chromium:1132299 Change-Id: Id47f3c4167a5ab0cf40e9ce7c63174377b075ea8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2461374Reviewed-by:
Mirko Bonadei <mbonadei@chromium.org> Commit-Queue: Ilya Nikolaevskiy <ilnik@chromium.org> Cr-Commit-Position: refs/heads/master@{#816093}
-
dpapad authored
This is in preparation of eventually auto-generating webui_resources.grd, which will produce IDs derived from a file's path. Currently this naming convention is used inconsistently. Bug: 1132403 Change-Id: I59673142f6dc1f1bd320f9185d9cfe0942270594 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2461989Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Reviewed-by:
Mike Dougherty <michaeldo@chromium.org> Reviewed-by:
Richard Coles <torne@chromium.org> Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Reviewed-by:
-
Rahul Goyal authored
Before this CL, overlay images were always retrieved from a target URL. This CL allows the backend to specify the image from a variety of sources, as used in other places of the system. This will make overlay images more versatile. The old way of fetching images from URLs is still supported by specifying a BitmapDrawable as input. Bug: b/168023114 Change-Id: I994dc10cda30e04f77cb8acbe10563575417d1b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2410067 Commit-Queue: Rahul Goyal <goyalrahul@google.com> Reviewed-by:
Clemens Arbesser <arbesser@google.com> Reviewed-by:
Marian Fechete <marianfe@google.com> Cr-Commit-Position: refs/heads/master@{#816091}
-
