- 09 Apr, 2020 40 commits
-
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/ebb5c85ab932..10b9675c807b git log ebb5c85ab932..10b9675c807b --date=short --first-parent --format='%ad %ae %s' 2020-04-09 jacktfranklin@chromium.org Strip line breaks when copying into TextPrompt 2020-04-09 alexrudenko@chromium.org Determine whether request params should be decoded by default 2020-04-09 jacktfranklin@chromium.org Fix poor contrasts in dark mode in computed styles view 2020-04-09 tvanderlippe@chromium.org Use CSSMetadata URL regex in StylePropertyTreeElement.js Created with: gclient setdep -r src/third_party/devtools-frontend/src@10b9675c807b 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/+/master/autoroll/README.md Bug: chromium:1066415 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I823b230604e9c129e2d06aad27f4b6f226258006 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2144379Reviewed-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@{#757870}
-
Vladimir Levin authored
This patch eliminates an unintentional re-entrant call to create a scoped force update object in Element::focus. This wasn't really a bug since the scopes would be deleted in the reverse order of creation, but in order to change this code further, we should maintain a guarantee that we do not create scopes on the stack that already has scoped objects. This patch does this by making the ctor private and allowing a few document functions to access it as friends. All other callers should be calling one of the document functions, depending on what type of update they need. R=chrishtr@chromium.org Fixed: 1068330 Change-Id: I32ac2fa6b095def65d64531e68ae03ab0d1d7b7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2140062Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Reviewed-by:
Aaron Leventhal <aleventhal@chromium.org> Commit-Queue: vmpstr <vmpstr@chromium.org> Cr-Commit-Position: refs/heads/master@{#757869}
-
David Van Cleve authored
TrustTokenRequestRedemptionHelper, which is responsible for executing Trust Tokens redemption operations, currently has its logic for generating a signing-and-verification key pair mocked out. This CL implements a concrete key pair generator satisfying the TrustTokenRequestRedemptionHelper::KeyPairGenerator interface on top of BoringSSL, using Ed25519, so that it's possible to construct redemption helpers with key pair generators that actually generate keys. Bug: 1068677 Change-Id: Ibe69486cba589884cfa69254971b9ec244b51cf7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2139443Reviewed-by:
Steven Valdez <svaldez@chromium.org> Commit-Queue: David Van Cleve <davidvc@chromium.org> Cr-Commit-Position: refs/heads/master@{#757868}
-
Chris Sharp authored
This involves adding a few missing deps. gn check output for changes: ERROR at //chrome/browser/policy/policy_path_parser_win.cc:17:11: Can't include this header from here. #include "chrome/install_static/policy_path_parser.h" ^----------------------------------------- The target: //chrome/browser/policy:path_parser is including a file from the target: //chrome/install_static:install_static_util ERROR at //chrome/browser/policy/policy_path_parser_mac.mm:21:11: Can't include this header from here. #include "build/branding_buildflags.h" ^-------------------------- The target: //chrome/browser/policy:path_parser is including a file from the target: //build:branding_buildflags Change-Id: If70fc54a85ee31089a51aff2c0d08d5af5d8558a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2140414Reviewed-by:Owen Min <zmin@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Commit-Queue: Chris Sharp <csharp@chromium.org> Cr-Commit-Position: refs/heads/master@{#757867}
-
Corentin Wallez authored
Bug: chromium:1064305 Change-Id: Id49edb06b68f2ce91fc6edc5f092a2b2dcb165f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2143795Reviewed-by:
Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org> Cr-Commit-Position: refs/heads/master@{#757866}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/5076bd228fba..5d1c16380705 git log 5076bd228fba..5d1c16380705 --date=short --first-parent --format='%ad %ae %s' 2020-04-09 mtklein@google.com fix JIT min/max 2020-04-09 fmalita@chromium.org [svg] Skip "inherited" presentation attributes 2020-04-09 jvanverth@google.com D3D fixes to clean up crashes in tests 2020-04-09 robertphillips@google.com Delay creation of GrTextStrike and GrGlyphs until flush time 2020-04-09 tdenniston@google.com [SVG] Fix polyline/polygon point parsing 2020-04-09 fmalita@chromium.org [svg] Adjust container size on Viewer window resize Created with: gclient setdep -r src/third_party/skia@5d1c16380705 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 csmartdalton@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/+/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 Bug: chromium:1056730 Tbr: csmartdalton@google.com Change-Id: I375d467a852b1183653124221bd45b142dfd755c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2144377Reviewed-by:
-
Johann authored
The Finalized version of GC was removed in afdb2e7a and the plugin was updated in f229ff46 Change-Id: I3a89f8e91fed1aaeda301b0d54d168607ad6197d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2143413Reviewed-by:
Anton Bikineev <bikineev@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#757864}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/b5faec02776c..89fa61264af5 Created with: gclient setdep -r src-internal@89fa61264af5 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 nhiroki@google.com,reillyg@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: nhiroki@google.com,reillyg@google.com Change-Id: I3dc123e1c9c117b3249169b189309ce851ca3975 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2144374Reviewed-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@{#757863}
-
Peter Kasting authored
This test is line-for-line identical with the test below it. Long ago these two differed. They don't anymore, so nuke one. Bug: none Change-Id: I80c11632589cb8e781fd4a272eb4540c37129f6e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2143516 Auto-Submit: Peter Kasting <pkasting@chromium.org> Commit-Queue: Thomas Lukaszewicz <tluk@chromium.org> Reviewed-by:
Thomas Lukaszewicz <tluk@chromium.org> Cr-Commit-Position: refs/heads/master@{#757862}
-
Mikel Astiz authored
As of today, BookmarkModelObserver does not distinguish two very different events: 1. A favicon has actually changed for a bookmark. 2. A favicon for a bookmark has been loaded. They both get reported identically and in sync's case it needs to know whether a bookmark should be reuploaded (committed) or not. Treating all favicon-just-loaded events as local changes, as prior to this patch, is prone to undesired uploads that can lead to resurrected bookmarks and other sync conflicts. Before this patch, sync could identify some trivial cases, based on the fact that BookmarkSpecifics (hashed) hasn't changed at all. In such cases, BookmarkModelObserverImpl::BookmarkNodeFaviconChanged() didn't make a distinction, but the commit was later optimized away and never made it to the protocol. This mechanism is notably fragile in case BookmarkSpecifics go through code changes, such as new proto fields being introduced (unrelated to favicons). With this patch, the underlying design flaw is addressed and instead the two scenarios (favicon-just-loaded vs actual favicon change) are distinguished more reliably. A new hash is introduced in per-bookmark sync metadata that represents the last known content of the image, which allows determining whether the image has changed and a commit is needed. Change-Id: Ib88bed201b3f95be083026073a3c9422ab403b2b Bug: 1064945 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2141985Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Reviewed-by:
Mohamed Amir Yosef <mamir@chromium.org> Commit-Queue: Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#757861}
-
Emanuel Ziegler authored
The WPT directory contains some expected failures for tests that do not exist anymore under that name. These files have been removed to avoid confusion. R=ahaas@chromium.org R=binji@chromium.org Change-Id: Icbf3278fe2ec7e80326460e8741fb5b447f096ad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2137396Reviewed-by:
Andreas Haas <ahaas@chromium.org> Reviewed-by:
Ben Smith <binji@chromium.org> Commit-Queue: Emanuel Ziegler <ecmziegler@chromium.org> Cr-Commit-Position: refs/heads/master@{#757860}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/25eeda1872e4..7db1491a85f6 git log 25eeda1872e4..7db1491a85f6 --date=short --first-parent --format='%ad %ae %s' 2020-04-09 titovartem@google.com Restore call's final stats collection in PC level framework Created with: gclient setdep -r src/third_party/webrtc@7db1491a85f6 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/+/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I274d63aa4c9492518b7aeeb4a057fbcf17717009 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2144371Reviewed-by:
-
Steven Bingler authored
Adding a comment describing effects of a compromised renderer and noting that a fix is in progress. Bug: 1069040 Change-Id: I3914730e02cbd3d21dce500c52f7abdaebf53df2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2142613 Commit-Queue: Steven Bingler <bingler@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#757858}
-
Thomas Lukaszewicz authored
Bug: None Change-Id: I8102ce6b9c449e657603fd5173b457c4f669f105 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2140778 Commit-Queue: Thomas Lukaszewicz <tluk@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#757857}
-
Sigurdur Asgeirsson authored
Bug: 1068233 Change-Id: I31999fdfdada0061ca3bd274eded98a858ca1c4a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2137515 Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org> Reviewed-by:
François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#757856}
-
Andrew Grieve authored
This just renames the extensions in order to make build speed summaries distinguish the two. Bug: 1067273 Change-Id: I0a1e14cfed3557d29cd6beb0987436cacfaf6b65 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2140908 Commit-Queue: Andrew Grieve <agrieve@chromium.org> Commit-Queue: Peter Wen <wnwen@chromium.org> Auto-Submit: Andrew Grieve <agrieve@chromium.org> Reviewed-by:
Peter Wen <wnwen@chromium.org> Cr-Commit-Position: refs/heads/master@{#757855}
-
Garrett Beaty authored
The following changes were made to the console: * android-lollipop-arm-rel had its category changed to on_cq to match android-lollipop-arm-rel and android-marshamallow-arm64-rel. * The on_cq builders for the different android versions were grouped together before other on_cq builders. Bug: 1067057 Change-Id: I3f127a2addbe5311e5b05c26e993427aee3f36cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2140096 Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Reviewed-by:
Aaron Gable <agable@chromium.org> Cr-Commit-Position: refs/heads/master@{#757854}
-
Xiyuan Xia authored
RequestNewThroughputTracker creates a ThroughputTracker to track throughput of ui::Compositor. Each ThroughputTracker is assigned a per-compositor unique sequence id. The sequence id will be used on impl side to create a kCustom typed cc::FrameSequenceTracker. When a tracker is started, stopped or canceled, an entry is created in AnimationHost to store the pending start/stop info of the id. This info is pushed to impl side along with other properties. Bug: 1021774 Change-Id: I8cf8b4051bc68054c199d510083abf7bd41cf6e0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008001Reviewed-by:
Robert Flack <flackr@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#757853}
-
Caitlin Fischer authored
These tests correspond to those in metrics_service_user_demographics_browsertest.cc. (Note that there will be a follow-up CL to remove duplicate code.) Bug: 1065870 Change-Id: I13df596c3ca62b90ba138a973db8f344011d02f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132534 Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Roger McFarlane <rogerm@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#757852}
-
Paulo Warren authored
This CL introduces SharedImageRepresentationVaapiOzone, a representation that is responsible for signaling to SharedImageBackingOzone that a VASurface has a pending write. A SharedImageBackingOzone::VaSync() function is added to check on pending VASurface writes before producing a different representation. BUG=1058103 TEST=NONE Change-Id: Ia769f81a76fc0ee3374b696db0eb427f22460bbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132830Reviewed-by:
Khushal <khushalsagar@chromium.org> Reviewed-by:
Andres Calderon Jaramillo <andrescj@chromium.org> Commit-Queue: Paulo Warren <pwarren@chromium.org> Cr-Commit-Position: refs/heads/master@{#757851}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/d56b69f115e2..d9c2e89ef1ea git log d56b69f115e2..d9c2e89ef1ea --date=short --first-parent --format='%ad %ae %s' 2020-04-09 cwallez@chromium.org Fix wgpu::WholeSize not being set correctly inside BindGroup 2020-04-09 cwallez@chromium.org Skip ViewportTest failing on Swiftshader. Created with: gclient setdep -r src/third_party/dawn@d9c2e89ef1ea If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/dawn-chromium-autoroll Please CC cwallez@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel Bug: None Tbr: cwallez@google.com Change-Id: I8a52782e39476be218b25a9b4cb3710700aec5d8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2144372Reviewed-by:
-
Elly Fong-Jones authored
These are a legacy of the Cocoa browser days; Views browsers always have an anchor view, so a separate parent window & anchor rect is not needed. This change also moves setting the bubble's arrow into the constructor, rather than ShowBubble. Bug: None Change-Id: I036facd6b6d1153e55fa84f96f1fc9e58a8cd327 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2140173Reviewed-by:
Dana Fried <dfried@chromium.org> Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#757849}
-
David Tseng authored
Here's another corner case. Suppose a user toggles (either on or off) sticky mode while over an editable. We need to ensure that, even if the user continues to move around the editable or any related nodes of the editable, that we don't interfere with sticky mode state. For example, a user turns on sticky mode while over a content editable. The user navigates by character or word. This would trigger a change in the current range and potentially turn back off sticky mode. RELNOTES: n/a Change-Id: I728060fb30beaa0697b7078332201ed1bee45ecf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2142712 Commit-Queue: David Tseng <dtseng@chromium.org> Reviewed-by:
Akihiro Ota <akihiroota@chromium.org> Cr-Commit-Position: refs/heads/master@{#757848}
-
Mugdha Lakhani authored
Add a browsertest to verify expected SecurityStateClient behavior. Bug: 1052375 Change-Id: I6a063ce298e6576513b019a688452458fd76650e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2144032Reviewed-by:
Colin Blundell <blundell@chromium.org> Commit-Queue: Mugdha Lakhani <nator@chromium.org> Cr-Commit-Position: refs/heads/master@{#757847}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/61094cb6..da31061a 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: I1e37be2ddec058cd2abc102da7dbe7e1eab21786 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2144231Reviewed-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@{#757846}
-
Victor Hugo Vianna Silva authored
The documentation is expanded to reflect that this is the callback executed at the end of the manual (user-triggered) generation flow. The method is renamed to ManualGenerationResultAvailable to match its counterpart AutomaticGenerationAvailable and avoid confusion with ShowPasswordGenerationPopup. The renaming is also justified by the fact that on some platforms a dialog gets shown instead of popup. Bug: 1060131 Change-Id: I147daae8fe3cb4b87be576c9841f87475ae3c63b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2144154Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Commit-Queue: Victor Vianna <victorvianna@google.com> Cr-Commit-Position: refs/heads/master@{#757845}
-
Internal Frameworks Autoroller authored
TBR=bling-p10-rolls@google.com Change-Id: Ibb9775671e95bea115f3006bf0e0879be8ea8b9b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2144251Reviewed-by:
Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#757844}
-
John Budorick authored
Also cleans up a lot of old references to mikecase and yolandyan, both of whom left the team a while ago. Change-Id: I4d17c9044045170e8d6fb43961fe64e265d3e4ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2134783Reviewed-by:
Haiyang Pan <hypan@google.com> Reviewed-by:
John Chen <johnchen@chromium.org> Commit-Queue: John Budorick <jbudorick@chromium.org> Cr-Commit-Position: refs/heads/master@{#757843}
-
Sebastien Marchand authored
This moves everything except the "site_data_cache_facade*.cc" files as they are Chrome specific (dependency on the history service, Incognito, etc). Bug: 1064859 Change-Id: I05c5a598ff7d8d0a40b700bf4f6e7768ff19425e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2134599 Commit-Queue: Victor Costan <pwnall@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Reviewed-by:
Chris Hamilton <chrisha@chromium.org> Cr-Commit-Position: refs/heads/master@{#757842}
-
Garrett Beaty authored
The following changes were made to the console ordering: * The builders in the simple release category were moved before builders with more deeply nested categories; less-nested builders always appear before more-nested builders. * The builders in the simple debug category were move after builders in the simple release category; categories cannot be intermixed. Bug: 1067057 Change-Id: I83c90c89dc4cc9fc7fe3d1debb76532971955911 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2140195 Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Reviewed-by:
-
Mario Sanchez Prada authored
Migrate this test out of third_party/blink/web_tests/css3/filters and into the WPT-specific directory, adding links to the relevant specs and a test assertion describing its purpose. Bug: 1063749 Change-Id: Ic36568e1ad9bcbe98ac851ed4cc3a8d9d4c857e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2144033Reviewed-by:
Stephen Chenney <schenney@chromium.org> Commit-Queue: Mario Sanchez Prada <mario@igalia.com> Cr-Commit-Position: refs/heads/master@{#757840}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/597193051bfc..ebb5c85ab932 git log 597193051bfc..ebb5c85ab932 --date=short --first-parent --format='%ad %ae %s' 2020-04-09 pfaffe@chromium.org Add some missing license headers 2020-04-09 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS. 2020-04-09 tvanderlippe@chromium.org Remove esprima Created with: gclient setdep -r src/third_party/devtools-frontend/src@ebb5c85ab932 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/+/master/autoroll/README.md Bug: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I10ecfa434fecf913c2a3d816fad763fc0518eacd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2143964Reviewed-by:
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/f3ae9d6b5d40..5a992d9caec7 git log f3ae9d6b5d40..5a992d9caec7 --date=short --first-parent --format='%ad %ae %s' 2020-04-09 fmayer@google.com Ingest smaps into trace processor. Created with: gclient setdep -r src/third_party/perfetto@5a992d9caec7 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/+/master/autoroll/README.md Bug: chromium:150930222 Tbr: perfetto-bugs@google.com Change-Id: I319f1ef2d2b288f7a16b595e547f9bae72d249b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2143962Reviewed-by:
-
Vasiliy Telezhnikov authored
When DisplayResourceProvider returns resources it calls ReleaseImageContexts which posts task to Gpu thread and returns resources to client. Client can reuse resources only after ReleaseImageContexts finished work on gpu thread. Currently it works because compositing sequence has high priority and raster does not, so any new raster on returned tile will happen later. This doesn't work for webview, because raster and compositing happen on different thread. This CL ensures correctness by returning sync token from ReleaseImageContexts. Bug: 1068716 Change-Id: I0606bdafa116190451a1d8cb7bbe97078dbd33da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132676 Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org> Reviewed-by:
Jonathan Backer <backer@chromium.org> Cr-Commit-Position: refs/heads/master@{#757837}
-
Vasiliy Telezhnikov authored
On WebView there are two threads where we access gpu: GPU Main Thread and Android Render Thread. When display compositor return resources it signals SyncToken on a sequence that belongs to Android Render Thread. Before this change gpu::Scheduler on main thread would ignore wait on such SyncToken because it's not aware of the sequence. This CL makes sure Scheduler will wait for this sync token to achieve proper synchronization. Bug: 1068716 Change-Id: I64fc5b3328dfc5536dfcf23eff62b4deb7b60b19 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2139365 Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org> Reviewed-by:
Sunny Sachanandani <sunnyps@chromium.org> Cr-Commit-Position: refs/heads/master@{#757836}
-
Yann Dago authored
Bug: 958893 Change-Id: I987a99d3db2b659babe46d2f15cfac6627bc573c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2134396 Commit-Queue: Yann Dago <ydago@chromium.org> Reviewed-by:
Greg Thompson <grt@chromium.org> Cr-Commit-Position: refs/heads/master@{#757835}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/d7bec5552079..5076bd228fba git log d7bec5552079..5076bd228fba --date=short --first-parent --format='%ad %ae %s' 2020-04-09 fmalita@chromium.org [svg] Fix dasharray padding Created with: gclient setdep -r src/third_party/skia@5076bd228fba 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 csmartdalton@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/+/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 Bug: None Tbr: csmartdalton@google.com Change-Id: Ie07c63c208dfcca060d885a86102df140b9b8b25 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2143963Reviewed-by:
-
Mikhail Khokhlov authored
Implements 3 commands that will be used by an autoroller to: - Query the latest dependency version - Query the current dependency version - Make the changes to roll the newer version Bug: b/150129933, skia:10109 Change-Id: I953b728a5555f03a80701e546796534cc74b6147 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2142272 Commit-Queue: Mikhail Khokhlov <khokhlov@google.com> Reviewed-by:
Eric Boren <borenet@google.com> Cr-Commit-Position: refs/heads/master@{#757833}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/glslang/+log/9c3204a1fde0..75de196cecab git log 9c3204a1fde0..75de196cecab --date=short --first-parent --format='%ad %ae %s' 2020-04-09 40001162+alelenv@users.noreply.github.com Add support for EXT_ray_flags_primitive_culling. (#2173) Created with: gclient setdep -r src/third_party/glslang/src@75de196cecab If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/glslang-chromium-autoroll Please CC radial-bots+chrome-roll@google.com,jonahr@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_angle_vk32_deqp_rel_ng;luci.chromium.try:android_angle_vk32_rel_ng;luci.chromium.try:android_angle_vk64_deqp_rel_ng;luci.chromium.try:android_angle_vk64_rel_ng;luci.chromium.try:linux_angle_deqp_rel_ng;luci.chromium.try:linux-angle-rel;luci.chromium.try:win-angle-rel-32;luci.chromium.try:win-angle-rel-64;luci.chromium.try:win-angle-deqp-rel-32;luci.chromium.try:win-angle-deqp-rel-64 Bug: None Tbr: radial-bots+chrome-roll@google.com,jonahr@google.com Change-Id: I703aa08b2792635b511ecce07a83405c5f3ca09a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2143471Reviewed-by:
-
Jérôme Lebel authored
Changing the title case to be: + "Cancel" + "Yes, I'm In" + "No Thanks" + "Add Account" Instead being full upper case. The "More" button already have the right case. More button: https://drive.google.com/open?id=15vqLmU2mCpjz41bOrKdzYvPHubbj2m_y Before: https://drive.google.com/open?id=1LYIyLOwRUyiD5Syzvl648cycq42trYVv https://drive.google.com/open?id=12jBAY5JTTKUgfBwCREWpRnc620btKx-2 After: https://drive.google.com/open?id=10TwDZEc7_qfapCmb651UHjQijhIX81_C https://drive.google.com/open?id=1nnnFpYS5JkzhSibXePGf9JUNeue3dnl8 Bug: 971989 Change-Id: Ib60b1a910d669f03c90613e865d7a986351f4230 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2142293Reviewed-by:
Nohemi Fernandez <fernandex@chromium.org> Commit-Queue: Jérôme Lebel <jlebel@chromium.org> Cr-Commit-Position: refs/heads/master@{#757831}
-
