- 08 Apr, 2019 40 commits
-
-
Raul Tambre authored
The script still works with Python 2. There are no intended behaviour changes. Bug: 941669 Change-Id: I9d0d56b95eccc82da7820347877f4df0339ff731 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1556773 Auto-Submit: Raul Tambre <raul@tambre.ee> Commit-Queue: Asanka Herath <asanka@chromium.org> Reviewed-by:
Asanka Herath <asanka@chromium.org> Cr-Commit-Position: refs/heads/master@{#648721}
-
Cathy Li authored
[Explore sites][Touchless]: Ensure that category title will always be visible when a site has focus. Bug: 944258 Change-Id: I7bae69cad28c93affd08afcb8646dfc52ec0e4de Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1550002Reviewed-by:
Justin DeWitt <dewittj@chromium.org> Commit-Queue: Justin DeWitt <dewittj@chromium.org> Commit-Queue: Cathy Li <chili@chromium.org> Cr-Commit-Position: refs/heads/master@{#648720}
-
Joshua Pawlicki authored
Bug: 881076 Change-Id: I4b6172fb454138a622a1beb671c5c54a51171390 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1548067 Auto-Submit: Joshua Pawlicki <waffles@chromium.org> Reviewed-by:
Sorin Jianu <sorin@chromium.org> Commit-Queue: Joshua Pawlicki <waffles@chromium.org> Cr-Commit-Position: refs/heads/master@{#648719}
-
Jochen Eisinger authored
Bug: 944754 Change-Id: I653d8dc62723ddf631dfd2ef78b14e4675c1ca63 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1553542Reviewed-by:
Evan Stade <estade@chromium.org> Commit-Queue: Jochen Eisinger <jochen@chromium.org> Cr-Commit-Position: refs/heads/master@{#648718}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/edab510dfad8..eba396cc66d3 git log edab510dfad8..eba396cc66d3 --date=short --no-merges --format='%ad %ae %s' 2019-04-08 bclayton@google.com Rename 'unittests' to 'gles-unittest' Created with: gclient setdep -r src/third_party/swiftshader@eba396cc66d3 The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. 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_optional_gpu_tests_rel TBR=swiftshader-team+autoroll@chromium.org Change-Id: Ic4700466e08ad379206afcdb10bb26fedb9984d9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1557986Reviewed-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@{#648717}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/eec47f93..c796dae2 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,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I8235e1ecd3a5aa77374dea39e69d7a952accf52c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1557788Reviewed-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@{#648716}
-
Eugene But authored
The root cause should be fixed in crrev.com/c/1553501 . This CL simply enables the test. Bug: 845879 Change-Id: I396396ef661501855a1f3082449f8a1caa246eaf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1555251Reviewed-by:
Mike Dougherty <michaeldo@chromium.org> Commit-Queue: Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#648715}
-
Steven Valdez authored
Bug: 641225 Change-Id: I743d0ef2269935e76ce26ee874b4e15f35c50fd4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1067603 Commit-Queue: Steven Valdez <svaldez@chromium.org> Reviewed-by:
Steven Valdez <svaldez@chromium.org> Reviewed-by:
Ryan Hamilton <rch@chromium.org> Reviewed-by:
David Benjamin <davidben@chromium.org> Cr-Commit-Position: refs/heads/master@{#648714}
-
Eric Orth authored
This matches the HostResolverManager behavior where all requests get silently cancelled if the manager is destroyed. Now if a ContextHostResolver is destroyed, all requests created by that resolver get silently cancelled, leaving requests from other resolvers alone. Motivation: For DoH, need to ensure that if a context (and its per-context resolver) are destroyed, any requests potentially using that context for DoH are cancelled. Previously, DoH always used the "primary" context and we took special care to cancel all DNS requests on destruction of that context, but DoH will soon use any context from the per-context resolvers. Bug: 934402 Change-Id: I99d087bdd17ac8e2bd54efa4c425e63abf0568ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1549897Reviewed-by:
Matt Menke <mmenke@chromium.org> Commit-Queue: Eric Orth <ericorth@chromium.org> Cr-Commit-Position: refs/heads/master@{#648713}
-
Yuzu Saijo authored
This CL updates wpr files for leak detection. Change-Id: Ibac5224621fb0ceee65f68888afa0480602ae396 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1554464Reviewed-by:
Keishi Hattori <keishi@chromium.org> Commit-Queue: Yuzu Saijo <yuzus@chromium.org> Cr-Commit-Position: refs/heads/master@{#648712}
-
chromium-autoroll authored
The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast TBR=cr-fuchsia+bot@chromium.org Change-Id: I88eb3a84fe94f81d7d1ec9d75c336911ada37a01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1557987Reviewed-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@{#648711}
-
chrome://translate-internalsMoe Ahmadi authored
Bug: 944079 Change-Id: If6b80ec575b38423e66832061bb239f67f24df93 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1541816 Commit-Queue: Moe Ahmadi <mahmadi@chromium.org> Reviewed-by:
anthonyvd <anthonyvd@chromium.org> Reviewed-by:
Mike Dougherty <michaeldo@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#648710}
-
Ella Ge authored
This CL adds another field predicted_scroll_update_delta to keeps the scroll delta after prediction. And also updates the AverageLag to take the predicted_scroll_update_delta into account. Bug: 946212 Change-Id: I1ba2bc5bd644c630d53d7f02d6ab4c4c4259f09b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1549346 Commit-Queue: Ella Ge <eirage@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Timothy Dresser <tdresser@chromium.org> Cr-Commit-Position: refs/heads/master@{#648709}
-
Harald Alvestrand authored
Bug: chromium:854385 Change-Id: Iae271e42cea733464730e7560b7caa52f57860f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1556844 Commit-Queue: Harald Alvestrand <hta@chromium.org> Reviewed-by:
Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#648708}
-
David Roger authored
Bug: 949043 Change-Id: I651d497efcb46e2a6acac24721ff59e66e5f1edc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1554351Reviewed-by:
Boris Sazonov <bsazonov@chromium.org> Commit-Queue: David Roger <droger@chromium.org> Cr-Commit-Position: refs/heads/master@{#648707}
-
Tomasz Wiszkowski authored
This change lays a corner stone for works on Omnibox site favicons. Doc: http://doc/1-gTFVwUV2uq374osWmK-Ll4gsUiz6eUz85GOm-BuPl8 Bug: 949753 Change-Id: I1de3ca7a2f2089f07ac3b65c43382a27ab525f11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1553952Reviewed-by:
Matthew Jones <mdjones@chromium.org> Reviewed-by:
Justin Donnelly <jdonnelly@chromium.org> Commit-Queue: Ender <ender@google.com> Cr-Commit-Position: refs/heads/master@{#648706}
-
Weilun Shi authored
Change VariationsServiceStartsRequestOnNetworkChange to unit test instead of browser test. Using the mock variations service to perform the same test. Bug: 905714 Change-Id: I66c4b6c91ec94933c19218398af9057f736ad736 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1550189Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Auto-Submit: Weilun Shi <sweilun@chromium.org> Cr-Commit-Position: refs/heads/master@{#648705}
-
Kevin McNee authored
If an async hit test results in a renderer hitting a remote frame, ignore it if input events should not be routed to that frame, as is the case with portals. Bug: 932581 Change-Id: I610442ac56383257dc02d6b3f0f0e2bea1f0fbb0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1553914Reviewed-by:
Lucas Gadani <lfg@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Commit-Queue: Kevin McNee <mcnee@chromium.org> Cr-Commit-Position: refs/heads/master@{#648704}
-
Eric Orth authored
Each individual URLRequestContext gets its own HostResolver instance. Also, because that HostResolver becomes a dependency of the HttpNetworkSession, constructed a new session for the media context rather than reusing the session from the main context and built the whole context from scratch rather than relying on the dangerous URLRequestContext::CopyFrom(). Saved the sessions to a unique_ptr rather than leaking it as was done previously. Bug: 934402 Change-Id: I1c61f58406c2df66786da72146c4eb2631f6450c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1529518Reviewed-by:
Luke Halliwell <halliwell@chromium.org> Reviewed-by:
Asanka Herath <asanka@chromium.org> Commit-Queue: Eric Orth <ericorth@chromium.org> Cr-Commit-Position: refs/heads/master@{#648703}
-
Etienne Bergeron authored
The main goal of this CL is to remove an usage of PlatformFontWin. The test RenderTextTest.HarfBuzz_UniscribeFallback is creating a PlatformFontWin class and directly manipulate the HFontRef/HFONT to put the localized name. The initial goal of test was to ensure the fast-path for font fallback is called. ShapeRuns is trying the following fonts: 1) PrimaryFont / SecondaryFont 2) GetFallbackFont (for a given text) a) win7 : Use of Uniscribe fallback b) win10 : Use of DWrite fallback 3) GetFallbackFonts (enumerate all fonts) The test was designed to force the fallback to hit 2), while impossible to succeed with 3). Unfortunately, on windows 10, the "Meiryo" font is not installed by default and it's part of the Japaneese extension. The font constructor replace it by Arial which is making the path 3) to be hitted and the test to (incorrectly) pass. We are adding checks that the font name and localized font name are kept correctly. We are adding a windows 10 localized font. R=asvitkine@chromium.org CC=dfried@chromium.org, robliao@chromium.org Bug: 944227 Change-Id: I7990e973d6702abee998ccafeee753b947cca0bd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1554001 Commit-Queue: Etienne Bergeron <etienneb@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Robert Liao <robliao@chromium.org> Cr-Commit-Position: refs/heads/master@{#648702}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/90b1865e2a8b..9f958344898c git log 90b1865e2a8b..9f958344898c --date=short --no-merges --format='%ad %ae %s' 2019-04-08 jmadill@chromium.org Add MD browser to DEPS. Created with: gclient setdep -r src/third_party/angle@9f958344898c The AutoRoll server is located here: https://autoroll.skia.org/r/angle-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. 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_optional_gpu_tests_rel TBR=ynovikov@chromium.org Change-Id: I5df388d5268f1621c0f3d578a3e26085a4bab1d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1557885Reviewed-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@{#648701}
-
Sharon Yang authored
This is a known TODO, so commenting out the unnecessary logging. Bug: 944885 Change-Id: Ib8816806e6bc5819a82af333973e04c1e4a4bdb4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1554652Reviewed-by:
Colin Blundell <blundell@chromium.org> Reviewed-by:
Wez <wez@chromium.org> Commit-Queue: Sharon Yang <yangsharon@chromium.org> Cr-Commit-Position: refs/heads/master@{#648700}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/e8c2d95ed45f..7ce37d66a86d git log e8c2d95ed45f..7ce37d66a86d --date=short --no-merges --format='%ad %ae %s' 2019-04-08 stevenperron@google.com Fix use of Logf to avoid format security warning (#2498) 2019-04-05 zoddicus@users.noreply.github.com Add WebGPU->Vulkan and Vulkan->WebGPU flags in spirv-opt (#2496) 2019-04-05 46733637+JasperNV@users.noreply.github.com spirv-opt: Behave a bit better in the face of unknown instructions (#2487) 2019-04-05 stevenperron@google.com Add fix storage class code. (#2434) Created with: gclient setdep -r src/third_party/SPIRV-Tools/src@7ce37d66a86d The AutoRoll server is located here: https://autoroll.skia.org/r/spirv-tools-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=dsinclair@chromium.org Change-Id: I070f936d09937f039988ed1e42219f1e41284c06 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1557888Reviewed-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@{#648699}
-
Brian White authored
Times are small, consistent, and now on a background thread. Bug: 888748 Change-Id: I93684f43d8a711dcac6d950b6f03dccfa8ba55e0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1558130 Commit-Queue: Brian White <bcwhite@chromium.org> Commit-Queue: Alexei Svitkine <asvitkine@chromium.org> Auto-Submit: Brian White <bcwhite@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#648698}
-
Denis Kuznetsov authored
1) PolicyTestServer can be configured not to ask for device attributes during enrollment. 2) PolicyTestServer can be configured to produce specific HTTP error codes during enrollment Bug: 950471 Change-Id: Ie49080260bfc4d07ae46b3f64a72df750a09913d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1556804 Commit-Queue: Denis Kuznetsov <antrim@chromium.org> Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#648697}
-
Alexander Hendrich authored
Feature properties whitelist and blacklist should only contain SHA-1 hashes of actual extension IDs. We can't verify whether the hash was generated from an actual extension ID, but we can ensure that only valid SHA-1 hashes are contained. Invalid values will cause an compile error. Bug: none Change-Id: I4a62d3bee9737a7c87963b7179e89ea974e12e60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1554498Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Commit-Queue: Alexander Hendrich <hendrich@chromium.org> Cr-Commit-Position: refs/heads/master@{#648696}
-
Xiaocheng Hu authored
These are deprecated functions without any use other than in test code. Hence, this patch removes them. The removal also makes it easier to migrate to hit test based up/down caret movements: http://bit.ly/2WB70oR Bug: 947179 Change-Id: I64fdf639477770515bcb4fa929f01eb908566e3f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1553317Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#648695}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/ccdd6a14ac44..09d022cbb8a6 git log ccdd6a14ac44..09d022cbb8a6 --date=short --no-merges --format='%ad %ae %s' 2019-04-08 kjlubick@google.com [pathkit] build with newer emscripten 2019-04-08 reed@google.com Revert "Revert "Move localmatrix routines to shaderbase, no need to be public."" Created with: gclient setdep -r src/third_party/skia@09d022cbb8a6 The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. 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 TBR=egdaniel@chromium.org Change-Id: I0beed32a49a63861e17beb220b63299a6b43cbed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1557889Reviewed-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@{#648694}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/cb0a4cdcabe1..fb43b375bc15 git log cb0a4cdcabe1..fb43b375bc15 --date=short --no-merges --format='%ad %ae %s' 2019-04-08 lalitm@google.com Merge "trace_processor: eliminate more uses of the proto API" Created with: gclient setdep -r src/third_party/perfetto@fb43b375bc15 The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=perfetto-bugs@google.com Change-Id: Iff369acb272211e819ff49de0566369117110292 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1557887Reviewed-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@{#648693}
-
Steven Bennetts authored
This replaces the //chromeos/dbus dependency with just //chromeos/dbus/shill in //chromeos/network and a few other BUILD.gn files. For mechanical changes to services/device/geolocation: TBR=mcasas@chromium.org Bug: 948390 Change-Id: I07ba8c79dfa603fb6018e2b2166ca8813240c4b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1553679 Commit-Queue: Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#648692}
-
Ian Vollick authored
Updates the interest ring UX for video with spatial navigation. Bug: None Change-Id: Id5a5ac5860859710be8959b1c1923c5982831fd5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1554820Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Commit-Queue: Ian Vollick <vollick@chromium.org> Cr-Commit-Position: refs/heads/master@{#648691}
-
Saman Sami authored
activation_dependencies in CompositorFrameMetadata is always populated even if the deadline is zero. Almost all frames have a zero deadline, which means we're doing a lot of unnecessary work. Don't go through activation_dependencies for such frames. Bug: 938947 Change-Id: I7ee1852a8b96b63530d0348538761f4da1969774 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1557786Reviewed-by:
kylechar <kylechar@chromium.org> Commit-Queue: Saman Sami <samans@chromium.org> Cr-Commit-Position: refs/heads/master@{#648690}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/3c8363e80d5f..cfc84d9bdd36 Created with: gclient setdep -r src-internal@cfc84d9bdd36 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=huangs@chromium.org,battre@chromium.org,collinbaker@chromium.org,tasak@chromium.org Change-Id: I840cfc07a43a3f3a703f4e053133b6b4aef784ec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1557884Reviewed-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@{#648689}
-
Christian Fremerey authored
Before this CL, class FrameSinkVideoCapturerImpl uses a somewhat hard-to-follow protocol with InterprocessFramePool for resurrecting video frames in case that the source content did not change. This CL changes this protocol to a simpler-to-follow mechanism, which also can reduce the cases where content is re-captured even though it is already available in a previously captured buffer. Change-Id: I635e3cf0dce61f704a6b613702791f03ff0c217a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1479154 Commit-Queue: Christian Fremerey <chfremer@chromium.org> Reviewed-by:
Yuri Wiitala <miu@chromium.org> Cr-Commit-Position: refs/heads/master@{#648688}
-
Greg Fiorentino authored
This change adds a new_tab_url for the DuckDuckGo search engine. Change-Id: I37be02e07eb7e4aa90f115455ce7a21832ff4eab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1555048Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Commit-Queue: Vasilii Sukhanov <vasilii@chromium.org> Cr-Commit-Position: refs/heads/master@{#648687}
-
Francois Doray authored
When the --no-sandbox flag is used, hanging child processes can outlive a browser process that gets killed. This results in leftover processes on bots when the process launcher sequence is made CONTINUE_ON_SHUTDOWN (see https://crbug.com/830954#c18). With this CL, all child processes are part of a "Kill on Job Close" job and are guaranteed not to outlive the browser process. This is a prerequisite to make the process launcher sequence CONTINUE_ON_SHUTDOWN, which will fix ~12% of shutdown hangs on Windows. Bug: 830954 Change-Id: Ieec2b0a4cfc7db93dfffde947cae9fdb46fedb02 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1548839Reviewed-by:
Will Harris <wfh@chromium.org> Commit-Queue: François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#648686}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/glslang/+log/e06c7e9a515b..0527c9db8148 git log e06c7e9a515b..0527c9db8148 --date=short --no-merges --format='%ad %ae %s' 2019-04-08 johnkslang@users.noreply.github.com Merge pull request #1752 from dgkoch/dkoch_build_fix18 Created with: gclient setdep -r src/third_party/glslang/src@0527c9db8148 The AutoRoll server is located here: https://autoroll.skia.org/r/glslang-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=dsinclair@chromium.org Change-Id: Ic782049349a48f153dfa74da527fc9aff618c152 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1557883Reviewed-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@{#648685}
-
Xianda Sun authored
This is a reland of ea1cc855 Original change's description: > Merge cc layer's hit test bits > > This patch merges all cc layer's hit test bits into one: |hit_testable|. > Now the bit is true if layer draws its content or is always hit testable > according to layer types. > > In the follow-up patch, ui::Layers will be able to set if they want to > accept events or not, so whether a layer is hit testable depends on: > > hit_testable = accept_events && (draws_content || > hit_testable_without_draws_content). > > Bug: 924294 > Change-Id: If455182790154451bec35fdd7c533b727cee96cf > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1427788 > Reviewed-by: Robert Flack <flackr@chromium.org> > Reviewed-by: enne <enne@chromium.org> > Reviewed-by: Antoine Labour <piman@chromium.org> > Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> > Reviewed-by: Philip Rogers <pdr@chromium.org> > Commit-Queue: Xianda Sun <sunxd@chromium.org> > Cr-Commit-Position: refs/heads/master@{#645761} Bug: 924294, 949564 Change-Id: I5f6be11291ccc007076db82b479deef26ef379a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1551685 Commit-Queue: Xianda Sun <sunxd@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Saman Sami <samans@chromium.org> Reviewed-by:
enne <enne@chromium.org> Reviewed-by:
Robert Flack <flackr@chromium.org> Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#648684}
-
Josh Karlin authored
What: This CL dramatically speeds up pretty printing of xml files. It speeds up 'git cl format' for CLs with histograms.xml changes from 9 seconds to 3 seconds. This also speeds up other common operations like 'git cl upload'. How: The pretty printer now processes an instance of ElementTree instead of minidom (and will convert minidom to etree if necessary). There is overhead converting minidom to etree but it's still an improvement for those cases where clients only speak minidom. The histograms pretty printer has been rewritten to speak ElementTree. The others (rappor, ukm, actions) still speak minidom and they should be converted in followup CLs but it's less important since their XML files are much smaller. Note: Top-level comments aren't supported by ElementTree, so I've written a SAX parser to copy everything above the first tag in the document and paste it into the result of pretty printing. This is in etree_util.py Otherwise, pretty printing should behave identically. I've improved the testing to catch any mistakes I may have made, but given this involves parsing I wouldn't be surprised if a follow-up CL or two isn't required. Bug: 945354 Change-Id: I28990d245f5d471203f6430e08c8a98e3ba70d03 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1538783 Commit-Queue: Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#648683}
-
Dominic Battre authored
This CL disables the http/tests/devtools/sxg/sxg-prefetch-fail.js and http/tests/devtools/sxg/sxg-prefetch.js for virtual/sxg-with-network-service as well. TBR=horo@chromium.org Bug: 851363,950083 Change-Id: Ifc5d93e7637179cb3774dd9192f8829f5211198b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1556791Reviewed-by:
Dominic Battré <battre@chromium.org> Commit-Queue: Dominic Battré <battre@chromium.org> Cr-Commit-Position: refs/heads/master@{#648682}
-