- 10 Dec, 2020 40 commits
-
-
Luciano Pacheco authored
In the SWA Data Source register all the resources from the file_manager extension so we can use the same relative paths from the main.html used in the extension. With this change we can stop inlining the CSS via flattenhtml GRD option. Bug: 1113981 Change-Id: I3eb00b8ae3b0dc79273e1cdea00b5abc1426812a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580670 Commit-Queue: Luciano Pacheco <lucmult@chromium.org> Auto-Submit: Luciano Pacheco <lucmult@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#835567}
-
David Dorwin authored
Also replace initialization of deprecated log_service_channel member with new members log_sink_channel and log_sink_socket. Bug: 1136681, fuchsia:63529 Change-Id: I0bf1e785c17829eb19b193c7544cdd8d4e51542c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2581020 Commit-Queue: David Dorwin <ddorwin@chromium.org> Auto-Submit: David Dorwin <ddorwin@chromium.org> Reviewed-by:
Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#835566}
-
Glen Robertson authored
Also update outdated doc comment. Change-Id: I1c5161c11f3f5727b191f2fea55563c4596167cb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580964Reviewed-by:
Varun Khaneja <vakh@chromium.org> Reviewed-by:
Alan Cutter <alancutter@chromium.org> Reviewed-by:
Ryan Sleevi <rsleevi@chromium.org> Reviewed-by:
Trent Apted <tapted@chromium.org> Commit-Queue: Glen Robertson <glenrob@chromium.org> Cr-Commit-Position: refs/heads/master@{#835565}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/83498ed6d228..d94a77b304f4 2020-12-10 natsu@google.com Set prefersDedicatedAllocation for AHB If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Please CC swiftshader-team+autoroll@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_chromium_msan_rel_ng;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;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: swiftshader-team+autoroll@google.com Change-Id: I63954a6a6059761e7a9bdb0d7e013824de8f8af7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2582956Reviewed-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@{#835564}
-
Frédéric Wang authored
This CL removes host names and "localhost6" and "localhost6.localdomain6" from the list of known IPv6-only localhost. This means they will be resolved using the native DNS resolver rather than Chrome's internal one and that they won't be treated as "potentially trustworthy" origins [1] [2]. This aligns with the behavior of WebKit and Firefox, is expected to have low backward compatibility risk and one can configure things to preserve existing support [3] [4]. [1] https://tools.ietf.org/html/draft-west-let-localhost-be-localhost-06 [2] https://w3c.github.io/webappsec-secure-contexts/#is-origin-trustworthy [3] https://chromestatus.com/feature/5698580851458048 [4] https://groups.google.com/a/chromium.org/g/blink-dev/c/bmdcI_q2yWQ Bug: 1153337 Change-Id: I344e4aebe4caebc30c70f8dcda1ce87ee0937bda Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570568Reviewed-by:
Mike West <mkwst@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Commit-Queue: Frédéric Wang <fwang@igalia.com> Cr-Commit-Position: refs/heads/master@{#835563}
-
Frank Liberato authored
This CL adds an off-by-default option to use media::DecoderStream as WebRTC's external decoder, rather than a media::VideoDecoder directly. This allows: - Chrome's decoder selection algorithm can choose between hw and software video decoders based on resolution, and any other criteria that we use for non-rtc playback. - Chrome can fall back and forward between HW and SW decoders. - All of Chrome's SW decoder stack is available, rather than only those decoders which also have HW implementations (AV1). Design doc: https://docs.google.com/document/d/1UIkqHucVttNjiMk9wAaoFUJcZ2PQSDZmLleXQutMVZQ/edit?usp=sharing Change-Id: I59ade0b4e5a482f28bbb52ffb522bf6c50eaad2a Bug: 1132903,1136495, 1157227 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2495515Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Henrik Boström <hbos@chromium.org> Reviewed-by:
Hirokazu Honda <hiroh@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Frank Liberato <liberato@chromium.org> Cr-Commit-Position: refs/heads/master@{#835562}
-
Eric Willigers authored
Before writing any shared files to disk, we delete any files from past shares that are more than 10 minutes old. Bug: 1153215 Change-Id: I0994641915df3830c372bf5593b1b421d8ae1cdd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2581701 Commit-Queue: Eric Willigers <ericwilligers@chromium.org> Auto-Submit: Eric Willigers <ericwilligers@chromium.org> Reviewed-by:
Glen Robertson <glenrob@chromium.org> Cr-Commit-Position: refs/heads/master@{#835561}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/c2a1746b42d9..af11a00f7849 2020-12-10 skia-autoroll@skia-public.iam.gserviceaccount.com Roll Dawn from 30805557e651 to 29fd62989338 (3 revisions) 2020-12-10 jsimmons@google.com Cache text blobs computed by TextLine::paintText 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 jmbetancourt@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: jmbetancourt@google.com Change-Id: I884d89b926086e03dd77fbd934f187e1d8ae2eea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583039Reviewed-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@{#835560}
-
Thomas Guilbert authored
This CL converts SyncStatusCallback from a base::Callback to a base::OnceCallback. There a few small changes that happen as a result of dealing with move-only types. Most notably is that custom GMOCK actions do not play well with them types, and some actions had to be re-written as functors. Bug: 1152272 Change-Id: I1591795c947ce08121138b9c6a85e877884569b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576469Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Kinuko Yasuda <kinuko@chromium.org> Auto-Submit: Thomas Guilbert <tguilbert@chromium.org> Cr-Commit-Position: refs/heads/master@{#835559}
-
Jiewei Qian authored
This CL exposes Web App's start_url as publisher_id to AppService. Web App start_url is used to calculate AppId, and can be used to launch (navigate to) the App. App Service publisher_id is the platform-specific identifier for an App. Using start_url as publisher_id gives AppService users more flexibility in interacting with the App. This is useful in tests. For example, performing checks after navigating to the App's url in a browser tab. Bug: 1155337 Change-Id: Ie5d8796e178322ebd634386565d2c312c1fcec00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2581340 Commit-Queue: Jiewei Qian <qjw@chromium.org> Reviewed-by:
Alexey Baskakov <loyso@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#835558}
-
Kyle Williams authored
Wraps the Chrome Reporting Pipeline API in a CfM Service to allow other services to enqueue telemetry and log information. BUG=b:137780359 TEST='autoninja -C out/Default/ chrome/test:unit_tests && xvfb-run ./out/Default/unit_tests --gtest_filter=CfmLoggerServiceTest.*' Change-Id: I147f172c103c42df1d2ea93b592d7f9bfa125a69 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522216Reviewed-by:
Dominick Ng <dominickn@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
Zach Trudo <zatrudo@google.com> Commit-Queue: Kyle Williams <kdgwill@chromium.org> Cr-Commit-Position: refs/heads/master@{#835557}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/dd9c4208af2e..81356f4bf38c 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: I7f51b2f9f4e77ec5346c1efdb51ed54dceccdf59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583119Reviewed-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@{#835556}
-
Jason Lin authored
We only need one notifier id. Bug: b/167491603 Change-Id: I426317ef4d87f9aeff91832c26bb613f8138320b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580380 Commit-Queue: Jason Lin <lxj@google.com> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Reviewed-by:
Joel Hockey <joelhockey@chromium.org> Cr-Commit-Position: refs/heads/master@{#835555}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/627f4a6b8dc3..dd9c4208af2e 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: I4244d8b1616304d31c1b447cbaa233d65014291b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583118Reviewed-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@{#835554}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/3c56ca23d926..32e1d74200bc 2020-12-10 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS. 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: Id8a61b48f5891acea2fc9db00502813e4a703e1b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2582968Reviewed-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@{#835553}
-
Carlos IL authored
Bug: 1061611 Change-Id: I3498e5c4c13657d573128c081f1a80097610792d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583137 Auto-Submit: Carlos IL <carlosil@chromium.org> Commit-Queue: Emily Stark <estark@chromium.org> Reviewed-by:
Emily Stark <estark@chromium.org> Cr-Commit-Position: refs/heads/master@{#835552}
-
Thomas Guilbert authored
This CL mirrors the changes landed in acbd2eae, and exposes VideoEncoder to workers. The changes in this CL rely on the conclusions from the previous CL. Notably, there is a need for a synchronous wait when getting the GPU factories due to some threading issues, and there is no support for logging from workers. Bug: 1094169 Change-Id: I2da6cdb2afd7b80e342268cbbfcb00fea64ad37f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2578002 Commit-Queue: Thomas Guilbert <tguilbert@chromium.org> Reviewed-by:
Eugene Zemtsov <eugene@chromium.org> Reviewed-by:
Dan Sanders <sandersd@chromium.org> Cr-Commit-Position: refs/heads/master@{#835551}
-
Stefan Zager authored
Change-Id: I4febb376c13fe82fe2ffcb3efc2dc4a315665b1e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583185Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Stefan Zager <szager@chromium.org> Cr-Commit-Position: refs/heads/master@{#835550}
-
Mitsuru Oshima authored
Let the client (callee) should handle empty case instead. Bug: 1156889 Test: updated the test cases. Change-Id: Iccea2a70784fdd4280f41ec07732ec5993831282 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580228 Commit-Queue: Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Robert Flack <flackr@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#835549}
-
Kyle Williams authored
This cl fixes minor issues with tests and defines a good way to test CfM Chromim Services. Bug:b:175079076 Test:'autoninja -C out/Default/ chrome/test:unit_tests chromeos:chromeos_unittests && xvfb-run ./out/Default/unit_tests --gtest_filter=CfmBrowserServiceTest.* && ./out/Default/chromeos_unittests --dbus-stub --gtest_filter=CfmHotlineClientTest.*' Change-Id: I3193e611818af08060f305d37799c9b79d97e2b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577733 Commit-Queue: Kyle Williams <kdgwill@chromium.org> Reviewed-by:
Ryo Hashimoto <hashimoto@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Auto-Submit: Kyle Williams <kdgwill@chromium.org> Cr-Commit-Position: refs/heads/master@{#835548}
-
edchin authored
This removes these flags and cleans up unused codepaths: * AddWebContentDropInteraction * DragAndDrop Both flags have been launched 100% in Finch and enabled by default TOT. Bug: 1101363, 1099646 Change-Id: I654dc96a8f41b4e9b013be0108989aa657b3b635 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2581033Reviewed-by:
Sergio Collazos <sczs@chromium.org> Commit-Queue: edchin <edchin@chromium.org> Cr-Commit-Position: refs/heads/master@{#835547}
-
Yuta Hijikata authored
The change is mostly mechanical replacing defined(OS_CHROMEOS) with BUILDFLAG(IS_CHROMEOS_ASH) and GN variable is_chromeos with is_chromeos_ash with some special cases (For those cases please refer to http://go/lacros-macros). The patch is made in preparation to switching lacros build from target_os=linux to target_os=chromeos. This will prevent lacros from changing behaviour after the switch. Bug: 1052397 Change-Id: I54158a0001b9c7d7f29d879b20f05e9b4b4e9260 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580923Reviewed-by:
Oksana Zhuravlova <oksamyt@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Commit-Queue: Yuta Hijikata <ythjkt@chromium.org> Cr-Commit-Position: refs/heads/master@{#835546}
-
Yuta Hijikata authored
The change is mostly mechanical replacing defined(OS_CHROMEOS) with BUILDFLAG(IS_CHROMEOS_ASH) and GN variable is_chromeos with is_chromeos_ash with some special cases (For those cases please refer to http://go/lacros-macros). The patch is made in preparation to switching lacros build from target_os=linux to target_os=chromeos. This will prevent lacros from changing behaviour after the switch. Bug: 1052397 Change-Id: I67ce28e4f8863d9247e57e03b771fb3f6bf7f5d6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2565042 Commit-Queue: Yuta Hijikata <ythjkt@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#835545}
-
Francois Doray authored
The thread handle should be used instead of the thread id for thread manipulations. It is available immediately after thread creation, unlike the thread id which is available only after the main function is entered. Also, on Windows, the thread handle remains valid after the thread has exited. This is a prerequisite to remove the wait after compositor thread initialization https://source.chromium.org/chromium/chromium/src/+/master:third_party/blink/renderer/platform/scheduler/common/thread.cc;l=96;drc=5b1ca7b1087e13d963bc4058d9406a838fb7f9ca Bug: 1080709 Change-Id: Ia0b72aa1b3a86454cffa774131944db87ced0843 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2578172Reviewed-by:
Alexander Timin <altimin@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Commit-Queue: Kentaro Hara <haraken@chromium.org> Auto-Submit: François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#835544}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=lakpamarthy@chromium.org Change-Id: I644f551c9634679d466ee86890f908d5a95407fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583702Reviewed-by:
Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#835543}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/26392d8577ab..a6fc821995dc 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 meredithl@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: meredithl@google.com Change-Id: I8048acca66782ea69a58d52851b5f38ef9f0fe75 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583542Reviewed-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@{#835542}
-
Ce Chen authored
The variant to be launched: http://screenshot/6pp7qvc8gfMGyxm Bug: 925072 Change-Id: I931f6a2432466d1b3692773256634aaad12d14dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2578505Reviewed-by:
Justin Donnelly <jdonnelly@chromium.org> Commit-Queue: Ce Chen <cch@chromium.org> Cr-Commit-Position: refs/heads/master@{#835541}
-
Satoshi Niwa authored
https://chromium.googlesource.com/chromiumos/platform2/system_api.git/+log/642f74bf3abe..11ce1d136747 $ git log 642f74bf3..11ce1d136 --date=short --no-merges --format='%ad %ae %s' 2020-11-11 hardikgoyal cryptohome: add AuthSession and unguessable token to identify it 2020-11-25 niwa cryptohome: Implement SetProjectId() 2020-05-29 xzhou system_api: add security key challenge response messages. Created with: roll-dep src/third_party/cros_system_api Change-Id: I23eba9ae7490a19446261e5fc53892eb4802356d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583582 Commit-Queue: Satoshi Niwa <niwa@chromium.org> Commit-Queue: Ryo Hashimoto <hashimoto@chromium.org> Auto-Submit: Satoshi Niwa <niwa@chromium.org> Reviewed-by:
Ryo Hashimoto <hashimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#835540}
-
Kent Tamura authored
* AXLayoutObject::ComputeAccessibilityIsIgnored() and LayoutObject::IsListMarkerForSummary() Skip LayoutObjects for summary::marker. The owner <details> already exposes open/closed information, and TextAlternative for disclosure-open and disclosure-closed are helpless. Test changes: * nth-pseudo.html Update expected numbers because now the UA stylesheet contains first-of-type. * offset-parent-does-not-leak-ua-shadow.html Use DETAILS instead of SUMMARY because SUMMARY doesn't have a UA shadow tree any longer. * details-clone.html It tested if UA shadow elements were cloned. But the shadow elements are not created after this CL. The test is converted to a pixel test to check if cloned details/summary elements have identical appearance. * details-marker-style.html Add a comment about unsupported properties. Bug: 590014 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng_disabled Change-Id: I2eda05da1af100b43ce624bfd464513b16af8c32 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577115Reviewed-by:
Koji Ishii <kojii@chromium.org> Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#835539}
-
Kyle Horimoto authored
This CL fixes an issue which can be caused when multiple concurrent Nearby Connection requests are requested by SecureChannel. When a connection disconnects, we check to see if there are any more active connections; if so, we shut down the process. Before this CL, we'd return early if that was the case. However, this means that if there were 1 attempt ongoing and 1 queued, then the queued attempt would never get to move forward after the first attempt disconnected (due to the early return). This CL fixes the issue by simply checking to see if there is another request which should be tried after the first one fails. This CL also adds a regression test which fails without the fix. Bug: 1156162 Change-Id: I914ba7ce5ec47ba107228b19641d849ffabf04ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583116 Commit-Queue: Kyle Horimoto <khorimoto@chromium.org> Commit-Queue: James Vecore <vecore@google.com> Auto-Submit: Kyle Horimoto <khorimoto@chromium.org> Reviewed-by:
James Vecore <vecore@google.com> Cr-Commit-Position: refs/heads/master@{#835538}
-
Josh Nohle authored
By default, sort the multi-device setup drop-down list by the potential host phones' last activity time. These values are returned from the CryptAuth server for phones that have already adopted DeviceSync v2. Note: Some old phones that are not using DeviceSync v2 will not have this information. Those phones will be displayed after the phones with a last activity time, and they will be sorted in the same way as before this flag was enabled. Bug: 923594 Change-Id: Ib915d1814a2932bf06cd32d9dfdb3be335a520ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583216 Commit-Queue: Josh Nohle <nohle@chromium.org> Commit-Queue: Kyle Horimoto <khorimoto@chromium.org> Auto-Submit: Josh Nohle <nohle@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#835537}
-
Rachel Carpenter authored
This CL points help app in app search to the new sandboxed LSS. Design doc: go/lss-sandboxing Implementation plan: go/lss-sandboxing-impl Bug: b/174514210 Change-Id: Ia3f3b442372d371bce57e199a64352f308894ae5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576234 Commit-Queue: Rachel Carpenter <carpenterr@chromium.org> Reviewed-by:
Giovanni Ortuño Urquidi <ortuno@chromium.org> Reviewed-by:
Alex Gough <ajgo@chromium.org> Reviewed-by:
Thanh Nguyen <thanhdng@chromium.org> Cr-Commit-Position: refs/heads/master@{#835536}
-
Dale Curtis authored
This implements AV1 hardware decoding according to the DXVA2 spec: https://www.microsoft.com/en-us/download/details.aspx?id=101577 Bug: 1115846 Test: Manual check of many streams. Passes all AV1 CQ tests. Change-Id: Ic920484af92fa56fd0422f8d989692be7118cfb4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2495791 Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Frank Liberato <liberato@chromium.org> Reviewed-by:
James Zern <jzern@google.com> Cr-Commit-Position: refs/heads/master@{#835535}
-
Mila Green authored
Bug: 1151106 Change-Id: I032321a96a06da9e80bef50b8ef76ef4525d2fc6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580906Reviewed-by:
Sorin Jianu <sorin@chromium.org> Reviewed-by:
Joshua Pawlicki <waffles@chromium.org> Commit-Queue: Mila Green <milagreen@chromium.org> Cr-Commit-Position: refs/heads/master@{#835534}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/dd9c4208af2e..81356f4bf38c 2020-12-10 delphij@google.com DO NOT MERGE - Merge Android R QPR1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:linux-perfetto-rel Bug: chromium:172690556 Tbr: perfetto-bugs@google.com Change-Id: I9fae442447d8bcde3813e1aec08574dff2a47888 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583545Reviewed-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@{#835533}
-
Matt Menke authored
CrossOriginEmbedderPolicyReporter calls into NetworkContext's reporting API. Reporting information can be used to track users across sites, so needs to be keyed on NetworkIsolationKey. This CL adds a NetworkIsolationKey to its constructor, and plumbs the right NetworkIsolationKey through. ServiceWorker/SharedWorkers currently use a NetworkIsolationKey as if they were top frame loads, but once they're sharded by top frame origin, that will need to change. Bug: 1143453 Change-Id: I8acbe720a17d7e2d4ff013bd277f9810c09f9c90 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2578164 Commit-Queue: Matt Menke <mmenke@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#835532}
-
Andrey Kosyakov authored
This is a refinement of previous fix for issue 1149042, that also takes care of another problem. The check that forces full frames is now moved downstream to the CompositorFrameSinkSupport, where we're able to use a more adequate criteria for whether full frame is needed. Drive-by: discard pending output requests after an externally-driven frame is done. Bug: 1149042, b/173651870 Change-Id: I26cd851315c3d9059403ef96f9a9bb5f21dfaafd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2557734 Commit-Queue: Andrey Kosyakov <caseq@chromium.org> Reviewed-by:
Sunny Sachanandani <sunnyps@chromium.org> Cr-Commit-Position: refs/heads/master@{#835531}
-
Haiyang Pan authored
on the android, linux, win10, mac, iOS, chromeos platforms. This follows the CL crrev.com/c/2580166. The existing CI configs on android, linux, and win10 are removed as well. (The CI test config on android will be removed via reverting crrev.com/c/2454729) Bug: 1099916 Change-Id: I02bd3280486de170a1c8ffcd2d2f0dc6b03e3adb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583105 Commit-Queue: Haiyang Pan <hypan@google.com> Reviewed-by:
Stephen Martinis <martiniss@chromium.org> Cr-Commit-Position: refs/heads/master@{#835530}
-
chromium-autoroll authored
Roll Chrome Linux PGO profile from chrome-linux-master-1607515179-f1c33f017a68d1555043f7e4b5e6f959b5d2d5d2.profdata to chrome-linux-master-1607558393-7b448dadc25433e8ca3294be917bb2299ab3dcfb.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: I92cc68f2458e59557bf81ca68aa272e69674a89b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583544Reviewed-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@{#835529}
-
Yi Gu authored
This reverts commit 7f95bc55. Reason for revert: Updating the backend in chrome://flags reliably leads to crash. Reverted locally and the crash was gone. Original change's description: > [WebOTP] Use a feature with variations instead of a multi value switch > > This allows WebOTP backend to be configured via finch trial infra. > > > Bug: 1153880 > Change-Id: I645171b4635595a48091ff3f40a63839321cf5ab > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2564007 > Commit-Queue: Majid Valipour <majidvp@chromium.org> > Reviewed-by: Nasko Oskov <nasko@chromium.org> > Reviewed-by: Yi Gu <yigu@chromium.org> > Reviewed-by: Majid Valipour <majidvp@chromium.org> > Cr-Commit-Position: refs/heads/master@{#835511} TBR=nasko@chromium.org,majidvp@chromium.org,yigu@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com Change-Id: I10dc087b539041f42781525e30f527846a708203 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1153880 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583117Reviewed-by:
Yi Gu <yigu@chromium.org> Commit-Queue: Yi Gu <yigu@chromium.org> Cr-Commit-Position: refs/heads/master@{#835528}
-