- 27 Mar, 2020 40 commits
-
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/4502a6360996..dd82c211fcb5 git log 4502a6360996..dd82c211fcb5 --date=short --first-parent --format='%ad %ae %s' 2020-03-27 treehugger-gerrit@google.com Merge "traced_perf: mallopt(M_PURGE) when going quiescent" Created with: gclient setdep -r src/third_party/perfetto@dd82c211fcb5 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: None Tbr: perfetto-bugs@google.com Change-Id: I04059e061d7cdff5f53b7f3068577da8ed944999 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124060Reviewed-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@{#754199}
-
Tim Judkins authored
Adds histogram logging to extension navigations caused by tabs.create, tabs.update, windows.create and browser.openTab (the latter only being used by apps), detecting if the URLs passed to those functions have the devtools scheme. Bug: 1049265 Change-Id: I7ac97e66ecf31d01d571936614a2d509deb6af9c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2102784Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Commit-Queue: Tim Judkins <tjudkins@chromium.org> Cr-Commit-Position: refs/heads/master@{#754198}
-
Peng Huang authored
Right now, the vulkan_tests can only run with X11. This CL make it work with android. Note: vulkan_tests is not running on any bots right now. Bug: 1065499 Change-Id: Ie8f9c452d2a77beb8e3c8d4c1fa715a8b708c2cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2125009 Commit-Queue: Peng Huang <penghuang@chromium.org> Reviewed-by:
Chris Blume <cblume@chromium.org> Reviewed-by:
Khushal <khushalsagar@chromium.org> Cr-Commit-Position: refs/heads/master@{#754197}
-
Livvie Lin authored
Fixes the case where a full HTTP URL will show in the omnibox, but get removed when clicking into the omnibox to edit. This patch will retain the HTTP scheme so that it's easier to add an 's' to attempt navigation to HTTPS. Bug: 1061576 Change-Id: I94d96bcb89b20a8c8bf2fc63dd5825d25f799907 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2122861 Commit-Queue: Livvie Lin <livvielin@chromium.org> Reviewed-by:
Tommy Li <tommycli@chromium.org> Cr-Commit-Position: refs/heads/master@{#754196}
-
Marijn Kruisselbrink authored
Color should be different in for example dark mode, so make sure to get the color from the current theme. Bug: 1065451 Change-Id: I581605d4f4c52f2ca2a50126e1a20d9ec865c2d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2125034 Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Commit-Queue: Michael Wasserman <msw@chromium.org> Auto-Submit: Marijn Kruisselbrink <mek@chromium.org> Reviewed-by:
Michael Wasserman <msw@chromium.org> Cr-Commit-Position: refs/heads/master@{#754195}
-
chromium-autoroll authored
Roll silvermont AFDO profile from 83-4085.6-1584956258-benchmark-83.0.4091.0-r2 to 83-4085.6-1584956258-benchmark-83.0.4094.0-r1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/cros-afdo-silvermont-chromium Please CC c-compiler-chrome@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 Tbr: c-compiler-chrome@google.com Change-Id: Ie79981394a2c345a7f729494c39b6935ec3d04f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2125111Reviewed-by:
-
edchin authored
In recent CL: crrev.com/c/2122820, EXPECT_EQ was inadvertently changed to ASSERT_EQ. This CL fixes that recent mistake. Change-Id: I239e980a7ae7b24ae709faeff3e57be3078c2b6c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2125018 Commit-Queue: edchin <edchin@chromium.org> Commit-Queue: Owen Min <zmin@chromium.org> Auto-Submit: edchin <edchin@chromium.org> Reviewed-by:
Owen Min <zmin@chromium.org> Cr-Commit-Position: refs/heads/master@{#754193}
-
Robert Ogden authored
Bug: 1023485 Change-Id: I8581e00f867b04e5312df0ea1fabdb06690c4d1f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2121086Reviewed-by:
Ryan Sturm <ryansturm@chromium.org> Commit-Queue: Robert Ogden <robertogden@chromium.org> Cr-Commit-Position: refs/heads/master@{#754192}
-
Robert Ogden authored
This CL actually makes a working feature out of Isolated Prerender. Now, prefetches done by the tab helper will be taken and used by the navigation interceptor and replayed over mojo channels via FromString Loader. For ease of manual testing, this CL also adds some command line flags: * override proxy hosts * set unlimited number of prefetches per SRP Additionally, the following changes are also made: * remove the FromSRP feature flag, consolidating under kIsolatePrerenders * testing for probing moves to browser tests instead of unittests * isolation of prerenders support removed, but code stubs left in place since that support will be re-added soon * small mojo receiver leak fixed * added prefetch timeout Bug: 1023485 Change-Id: I7b4d9e30a3e125b525b7b10ce5151b82570c84f1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2118397 Commit-Queue: Robert Ogden <robertogden@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Reviewed-by:
-
Robert Sesek authored
This reverts commit 1b8f4946. Reason for revert: This was just a bandaid. Internal change has rolled in. Original change's description: > Temporarily restore CustomTabsConnection.extractCreatorPackage. > > An internal class apparently overrides this method, and now > is broken because it is marked @Override. > > Tbr: wychen@chromium.org > No-Try: true > Bug: 1065440, 832124 > Change-Id: I0a8e1bf64c99c004dfa3a9a4cee91da71112bd37 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124232 > Commit-Queue: Robert Sesek <rsesek@chromium.org> > Reviewed-by: Robert Sesek <rsesek@chromium.org> > Cr-Commit-Position: refs/heads/master@{#754079} TBR=wychen@chromium.org,rsesek@chromium.org Change-Id: I1164c811f506ebbd0d93dd22ab6bff4c11d193b7 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1065428, 832124 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124061Reviewed-by:
Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#754190}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/774019051243..baf491f249db Created with: gclient setdep -r src-internal@baf491f249db 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 jbudorick@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: chromium:1013783,chromium:832124 Tbr: jbudorick@google.com Change-Id: I27d4ff34291c43408481e0e1d27c0bcb989cecd1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124043Reviewed-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@{#754189}
-
Sergey Ulanov authored
Previously WebEngine was implementing RequestMediaAccessPermission(), but not CheckMediaAccessPermission(). Check*() is called when a page tries to enumerates devices. It returns deviceIDs for audioinput devices only when the page can access microphone and that functionality didn't work properly. Bug: 1064813 Change-Id: I9dc37d5e35eee0c3ddd02c8e6c852763f0ec3cd2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2121446Reviewed-by:
David Dorwin <ddorwin@chromium.org> Commit-Queue: David Dorwin <ddorwin@chromium.org> Auto-Submit: Sergey Ulanov <sergeyu@chromium.org> Cr-Commit-Position: refs/heads/master@{#754188}
-
Peter Kasting authored
This means callers only need to call TearDown() if they need to do something between teardown and destruction, which most don't; and they cannot fail to call TearDown() (and thus leave objects alive). So it's both simpler and safer. Bug: none Change-Id: Ia7c8088df6475af28e37e81215ee704dd8e5650f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2125187 Commit-Queue: Peter Kasting <pkasting@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#754187}
-
Dana Fried authored
Now if the available size of a layout has changed, its children will be re-laid-out to ensure that they can react (in this case by animating). Solves a bug where: - An animating layout is embedded in a flex layout - The animating layout can drop to zero size/drop out - The flex layout is created at a very small size and then resized larger This happened with the extensions container in PWA windows under very specific conditions but could affect animating layouts elsewhere as well. Bug: 1057901 Change-Id: Ie18da24284dadf538d641ad5c2c15fc55d2b3b3c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2123107 Commit-Queue: Dana Fried <dfried@chromium.org> Reviewed-by:
Connie Wan <connily@chromium.org> Cr-Commit-Position: refs/heads/master@{#754186}
-
chromium-autoroll authored
https://chromium.googlesource.com/openscreen.git/+log/2e33129995df..e928c969dbb5 git log 2e33129995df..e928c969dbb5 --date=short --first-parent --format='%ad %ae %s' 2020-03-27 rwkeane@google.com mDNS: Add Service Type Enumeration 2020-03-27 btolsch@chromium.org Make all sockets go through select() 2020-03-27 miu@chromium.org Cast Streaming Standalone Sender: Congestion control, and video. 2020-03-27 rwkeane@google.com mDNS: Cap Cache Size in MdnsQuerier Created with: gclient setdep -r src/third_party/openscreen/src@e928c969dbb5 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/openscreen-chromium Please CC jophba@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Bug: None Tbr: jophba@chromium.org Change-Id: Iab3fda277ffbdb154b9508676fbe3400f466f3aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2125170Reviewed-by:
-
chromium-autoroll authored
Roll broadwell AFDO profile from 83-4044.62-1584958487-benchmark-83.0.4091.0-r2 to 83-4044.62-1584958487-benchmark-83.0.4094.0-r1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/cros-afdo-broadwell-chromium Please CC c-compiler-chrome@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 Tbr: c-compiler-chrome@google.com Change-Id: I538268691e8b9f02da6c09f8ec5ac070865b9de5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2125176Reviewed-by:
-
Matt Jones authored
Bug: 952703 Change-Id: I5040d4a1aff5227c8fe825acb62f5e1bd865b081 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124970Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Matthew Jones <mdjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#754183}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/f95a35fb706f..07e5b8f0edb6 git log f95a35fb706f..07e5b8f0edb6 --date=short --first-parent --format='%ad %ae %s' 2020-03-27 csmartdalton@google.com Rename TessellatingPathRendererTests.cpp -> "Triangulating" 2020-03-27 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader 02e15b249b12..3ca41df3d3ba (10 commits) Created with: gclient setdep -r src/third_party/skia@07e5b8f0edb6 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 robertphillips@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: robertphillips@google.com Change-Id: Ia41dc81b9c762d489b62d1f9c214232e5ab29b87 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124046Reviewed-by:
-
Eugene But authored
Old target created zip archive, while new target simply copies the directory. Creating zip archive requires to list every file in the archive, which is hard to maintain. Copying the directory would work fine because compression can be done on the build bot. Bug: 1064181 Change-Id: I92825cb56f614e328052987f4d6fa86602b41972 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2125014 Auto-Submit: Eugene But <eugenebut@chromium.org> Reviewed-by:
Ali Juma <ajuma@chromium.org> Commit-Queue: Ali Juma <ajuma@chromium.org> Cr-Commit-Position: refs/heads/master@{#754181}
-
Ian Wells authored
This is a reland of f2033302 Original change's description: > Add tests for FeedStore > > Bug: 1044139 > Change-Id: I1a72a48c438c53299397a161dfcaabeae0501452 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2109258 > Commit-Queue: Ian Wells <iwells@chromium.org> > Reviewed-by: Dan H <harringtond@chromium.org> > Cr-Commit-Position: refs/heads/master@{#753844} Bug: 1044139 Change-Id: I1d48e4cb18d313230b18ac1205d782458dbf2e95 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2123641 Commit-Queue: Ian Wells <iwells@chromium.org> Reviewed-by:
Dan H <harringtond@chromium.org> Cr-Commit-Position: refs/heads/master@{#754180}
-
Alexander Cooper authored
When including the device/vr/test target into content there is a name collision with FakeSensorProvider from fake_sensor_and_provider under //services. In order to enable the device/vr version to have whatever changes the device/vr tests need, this change renames this class from FakeSensorProvider to FakeXRSensorProvider Change-Id: Id07ff9371f9bb30c85ae9a33be46e37ea44c8140 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124533 Auto-Submit: Alexander Cooper <alcooper@chromium.org> Reviewed-by:
Piotr Bialecki <bialpio@chromium.org> Commit-Queue: Alexander Cooper <alcooper@chromium.org> Cr-Commit-Position: refs/heads/master@{#754179}
-
Josh Horwich authored
Remove code form ARC graphics tracing related to NYC-based SurfaceFlinger ReleaseBuffer event detection, since ARC no longer uses Android N. BUG=b:151958629 TEST=chrome://arc-graphics-tracing Change-Id: I126a71321fcf4b778eb732c169302ed5015b1c23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2125188Reviewed-by:
Yury Khmel <khmel@chromium.org> Commit-Queue: Josh Horwich <jhorwich@chromium.org> Cr-Commit-Position: refs/heads/master@{#754178}
-
Danan S authored
This will allow SupervisedUserInitiatedExtensionInstall, which is already enabled by default, to take effect, which will enable the parent permission dialog for supervised users to install extensions. Bug: 957832 Change-Id: If851c79f07817d6f044ed3ca1b634516f8cbcbd7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2123410Reviewed-by:
Aga Wronska <agawronska@chromium.org> Commit-Queue: Dan S <danan@chromium.org> Cr-Commit-Position: refs/heads/master@{#754177}
-
Adam Langley authored
A GATT write has a one-byte op-code and a two byte attribute handle at the beginning. Therefore the control-point needs to reduce the MTU by three bytes. BUG=1002262 Change-Id: I02a29a519d8dc87f05960beb155d49a9f1b22c2c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124244 Auto-Submit: Adam Langley <agl@chromium.org> Commit-Queue: Martin Kreichgauer <martinkr@google.com> Reviewed-by:
Martin Kreichgauer <martinkr@google.com> Cr-Commit-Position: refs/heads/master@{#754176}
-
Tina Wang authored
Bug: 1065404 Change-Id: Ie26610d8e4496c7ecf80efa82143ca99b4f595b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124728 Commit-Queue: Tina Wang <tinazwang@chromium.org> Reviewed-by:
Guillaume Jenkins <gujen@google.com> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Reviewed-by:
sebsg <sebsg@chromium.org> Cr-Commit-Position: refs/heads/master@{#754175}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/761afa07..b9280b4d 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: I8169249a5294d5a3b0d70892ae4a18bee7139519 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124095Reviewed-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@{#754174}
-
Vladimir Levin authored
This patch ensures that we gracefully handle the fact that we may be disconnected when we receive a viewport intersection notification. This is a consequence of delaying viewport intersection notifications to the beginning of the next frame. Note that this isn't a problem right now, but when selection is preventing locks, then we run into DCHECKs. The patch doing so is upcoming: https://chromium-review.googlesource.com/c/chromium/src/+/2122857 R=chrishtr@chromium.org Change-Id: I8449cc6018dd75f3de5962e122b8f79fb250c602 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124975Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Commit-Queue: vmpstr <vmpstr@chromium.org> Cr-Commit-Position: refs/heads/master@{#754173}
-
Peter Kasting authored
This is yet more precursor work for making AshTestHelper an AuraTestHelper subclass. It changes the constructor args to what AshTestHelper will need to supply. This results in moving context factory configuration up to the constructor. There are two conditionals in this patch that cannot currently succeed: (1) |disable_animations| (constructor arg) is never currently false. (2) |test_screen_| is never currently null when checked in TearDown(). Both of these conditions will be able to succeed when AshTestHelper is a subclass. Bug: none Change-Id: I7375fda8acaebf50199e6a9a04751e671b867005 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124241 Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:
-
Jeff Yoon authored
- xcode build version 11c29 and xcode_build_version property in ci.star - mb configs to mb_config.pyl - ios_clang_tests introduced to encompass ios ToT tests Generated files: - chromium.ci.json - chromium.clang.json - cr-buildbucket.cfg Bug: 1055164,912681 Change-Id: I4a884ad8222d6da2642c76bc8fbd10f74c418342 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2113078 Commit-Queue: Jeff Yoon <jeffyoon@chromium.org> Reviewed-by:
John Budorick <jbudorick@chromium.org> Reviewed-by:
Aaron Gable <agable@chromium.org> Cr-Commit-Position: refs/heads/master@{#754171}
-
Scott Violet authored
BUG=1064588 TEST=none Change-Id: I8dc72f2efc49b8d311feb214fcb0b8379583be85 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2122241 Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:
Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#754170}
-
Ayu Ishii authored
This changes adds CookieStore API to the CookiePolicyBrowserTest to ensure that third party cookie blocking works with the new API. Change-Id: I606ff485b4b4c5b933640fd106c4b57cd23f638c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2119186Reviewed-by:
Christian Dullweber <dullweber@chromium.org> Reviewed-by:
Maksim Orlovich <morlovich@chromium.org> Commit-Queue: Ayu Ishii <ayui@chromium.org> Cr-Commit-Position: refs/heads/master@{#754169}
-
Frank Liberato authored
Also fixes binding P010. Change-Id: Iba389bf5f883662d1ac2f7aa396992ff662d009d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2107054 Auto-Submit: Frank Liberato <liberato@chromium.org> Reviewed-by:
Ted Meyer <tmathmeyer@chromium.org> Commit-Queue: Ted Meyer <tmathmeyer@chromium.org> Commit-Queue: Frank Liberato <liberato@chromium.org> Cr-Commit-Position: refs/heads/master@{#754168}
-
Toby Huang authored
In response to the COVID-19 crisis, we launched the "extensions lite" feature that enables supervised users to install extensions from the ExtensionInstallWhitelist policy. In the hurry, we didn't add unit tests for the original CL. This CL adds unit tests for crrev.com/c/2109977. Bug: 1063099 Change-Id: Iaca12f16aedf6b1bd7e9a0b2c406ed7631f9942d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2121463Reviewed-by:
James Cook <jamescook@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Reviewed-by:
-
Xianzhu Wang authored
This is not fully correct, but we have to accept it in our current multicol painting based on FragmentClips. Actually we have already allowed non-atomic effects in multicol within composited layers since SlimmingPaintV175. A fragmented element with effect applies the effect on each fragment separately. We have to do this because each fragment has its own fragment clip, and its own paint properties because they may depend on the fragment clip. This CL enables non-atomic composited effects for CompositeAfterPaint. This is not an issue in pre-CompositeAfterPaint which doesn't allow fragmentation of composited layers (which is incorrect). The root issue will be fully fixed by LayoutNG block fragmentation which doesn't need FragmentClips. Bug: 1064341 Change-Id: Id6ae4c263381f24d037f3c2bc493d73cd050598e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124340 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#754166}
-
Nate Fischer authored
If no flags are toggled, flags are shown in the same order (the order hardcoded in ProductionSupportedFlagList). If the user has already toggled some flags (enabled/disabled), these flags float to the top of the list when the user revisits the UI. The flag order only moves when we recreate the flag UI. So flags will stay in the same place as the user interacts with the UI, and only move as a convenience if they return to the UI and need to go back to default. This is mostly consistent with chrome://flags (the difference is that we won't reset the order when the user clicks "reset all to default," for simplicity and convenience if the user changes their mind to re-enable some of those flags). Fixed: 1059478 Test: Manual - verify flags float to the top when I revisit the flag UI Change-Id: I01cac5e7c38b35be765c3e111f4b0d5ea4e3941f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124532Reviewed-by:
Richard Coles <torne@chromium.org> Commit-Queue: Nate Fischer <ntfschr@chromium.org> Cr-Commit-Position: refs/heads/master@{#754165}
-
Sergey Ulanov authored
Currnetly runner always redirects AudioCapturer to the agent and the AudioCapturer implementation provided by the agent supports echo cancellation, noise suppression and automatic gain control. Also, in the future the default AudioCapturer will implement these effects as well. Updated AudioManagerFuchsia::GetInputStreamParameters() to report these effects as supported. This ensures that WebRTC will not try to use built-in versions of these effects. Bug: 1065207 Change-Id: I9997dc603544441c0e1bc96516915943e08d7a2f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124305 Auto-Submit: Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
-
Jiawei Li authored
Adds a ExecuteJavaScript method for CastWebContents to run script on the main frame's context. The method would accept string script and a OnceCallback that is used to receive a result later. Bug: Internal b/150822089 Test: cast_web_contents_browsertest Change-Id: I15e43f62036907e667278f954d06b0bb035c59cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2123639 Commit-Queue: Jiawei Li <lijiawei@chromium.org> Reviewed-by:
Sean Topping <seantopping@chromium.org> Reviewed-by:
Yuchen Liu <yucliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#754163}
-
dpapad authored
Bug: 1026426 Change-Id: I1016b954c98bad62d1c121f590beffbbbb9610fd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2123187 Commit-Queue: dpapad <dpapad@chromium.org> Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#754162}
-
Matt Jones authored
Bug: 952703 Change-Id: I70e46da08c593b4f94d6225cc7cff2f152010da2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2121265Reviewed-by:
Jinsuk Kim <jinsukkim@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Commit-Queue: Matthew Jones <mdjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#754161}
-
Nico Weber authored
We only ship 64-bit asan runtimes on Windows, so we shouldn't try to build 32-bit binaries in 64-bit asan builds. Also improve an existing assert so that it catches problems like this at `gn gen` time in the future, by using current_cpu instead of target_cpu. Bug: 1065287 Change-Id: I511e50b9578650f85c0beb236ee1de9af6166fb5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2125029 Commit-Queue: Nico Weber <thakis@chromium.org> Commit-Queue: Nicolas Ouellet-Payeur <nicolaso@chromium.org> Auto-Submit: Nico Weber <thakis@chromium.org> Reviewed-by:
Nicolas Ouellet-Payeur <nicolaso@chromium.org> Cr-Commit-Position: refs/heads/master@{#754160}
-
