- 05 Oct, 2020 40 commits
-
-
Jerome Jiang authored
https://chromium.googlesource.com/webm/libvpx.git/+log/97356acb50e2..7e8ea22e4056 $ git log 97356acb5..7e8ea22e4 --date=short --no-merges --format='%ad %ae %s' 2020-10-02 jianj Add codec control to disable loopfilter for vp9 2020-09-30 jianj Add file for rate control interface test. 2020-09-29 jzern ratectrl_rtc_test.cc: fix signed/unsigned comparison 2020-09-29 jzern configure.sh: fix arm64-darwin-gcc match 2020-09-25 jzern configure: add darwin20 support 2020-09-16 jzern vp9_ratectrl,vp9_resize_one_pass_cbr: rm redundant casts 2020-09-16 jzern test/encode_test_driver: rm redundant get() w/unique_ptr Created with: roll-dep src/third_party/libvpx/source/libvpx R=jzern@google.com Change-Id: Id1b2c90b313d4a8ecfc385f26f912bcdb4c73d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2451373Reviewed-by:
James Zern <jzern@google.com> Commit-Queue: Jerome Jiang <jianj@google.com> Cr-Commit-Position: refs/heads/master@{#813991}
-
Xinghui Lu authored
The goal is to replace the SBER checkbox with the enhanced protection message. Enhanced protection message is shown when: 1 Not in incognito mode 2 kEnhancedProtectionMessageInInterstitials flag is enabled. 3 Safe Browsing pref is not managed by policies. 4 Enhanced protection is not already turned on. Bug: 1130721 Change-Id: Ic7175c6210023ebe23e5cd7aedacadf39091528a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2430826 Commit-Queue: Xinghui Lu <xinghuilu@chromium.org> Reviewed-by:
Ali Juma <ajuma@chromium.org> Reviewed-by:
Nate Fischer <ntfschr@chromium.org> Reviewed-by:
Carlos IL <carlosil@chromium.org> Reviewed-by:
Varun Khaneja <vakh@chromium.org> Cr-Commit-Position: refs/heads/master@{#813990}
-
Moe Ahmadi authored
- NTP Realbox has been fully launched in M84 and enabled by default in M86 (crrev.com/c/2354993). - This CL cleans up C++ code affected by the feature only. It leaves JS code in place. This is because (1) the local NTP code will be removed entirely with the launch of the WebUI NTP at a later milestone; and (2) there is still a lot of development in the WebUI NTP. References to <fakebox> in the WebUI NTP will be removed NTP at a later milestone Fixed: 1134781 Change-Id: Ic0a7009ab6464b15c19e8a172f061c0e487ca075 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2446533 Commit-Queue: Moe Ahmadi <mahmadi@chromium.org> Reviewed-by:
Justin Donnelly <jdonnelly@chromium.org> Reviewed-by:
Tibor Goldschwendt <tiborg@chromium.org> Cr-Commit-Position: refs/heads/master@{#813989}
-
Christopher Cameron authored
This was reverted last time because there was no GL context current (because the SharedImage path elides most GL calls). Add a MakeCurrent call before creating the SharedImage. This will need to be removed eventually. Bug: 1108909 Change-Id: I862b8ae7c502e5c4181b313db2be9e6acd4aae9e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2451372Reviewed-by:
Dan Sanders <sandersd@chromium.org> Commit-Queue: ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#813988}
-
Alex Gough authored
Adds a mojo ReadOnlyFile that won't serialize if it can be written. The expectation is that this handle will then be sent to another process which lacks the rights to add any write permissions to the handle. This may not be true on all platforms but is useful where this holds. Code to check for readonly-ness is implemented within mojo rather than base::File as it is (a) difficult to say in general what it means to be readonly, and (b) not possible on every platform. Bug: 1130762 Change-Id: I6f00934005da7e433af4fee94454dfcd28dfd3c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2417549 Commit-Queue: Alex Gough <ajgo@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Ken Rockot <rockot@google.com> Reviewed-by:
Matthew Denton <mpdenton@chromium.org> Cr-Commit-Position: refs/heads/master@{#813987}
-
Ghazale Hosseinabadi authored
This CL adds test coverage for WINDOWS_GET and WINDOWS_GETCURRENT APIs. Bug: 1093066 Change-Id: I8c8535818ffd0b748418c28bb3b4945439ca8593 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2442130 Commit-Queue: Ghazale Hosseinabadi <ghazale@chromium.org> Reviewed-by:
David Bertoni <dbertoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#813986}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/422c039e8e1b..d0b4e1976ca1 2020-10-05 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Please CC ajp@google.com,apolito@google.com,ehmaldonado@google.com,sokcevic@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: ajp@google.com,apolito@google.com,ehmaldonado@google.com,sokcevic@google.com Change-Id: I4a1e48e2de33e3acea5977a089d180118214fd41 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2451330Reviewed-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@{#813985}
-
evliu authored
This CL updates the download progress UI for the Live Caption feature to reflect the total download progress of both the SODA component and the selected language pack component(s). The feature currently only supports the en-US language pack which should be downloaded along side the SODA component. Bug: i1134807 Change-Id: Ie9d7a0b5442d5fdbc63c255f0aea713464ef3225 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2446468Reviewed-by:
Abigail Klein <abigailbklein@google.com> Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Evan Liu <evliu@google.com> Cr-Commit-Position: refs/heads/master@{#813984}
-
David Bienvenu authored
Change-Id: Ib31c2f3cc144b530fa6248e3481f7c6f3f61738a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2451328Reviewed-by:
Jesse McKenna <jessemckenna@google.com> Commit-Queue: David Bienvenu <davidbienvenu@chromium.org> Cr-Commit-Position: refs/heads/master@{#813983}
-
Kristi Park authored
This reverts commit 6a69beb2. Reason for revert: Failing content_browsertests on linux-trusty-rel https://ci.chromium.org/p/chromium/builders/ci/linux-trusty-rel/16561 Original change's description: > Avoid illegal serializations with aria-owns and unincluded nodes > > When adding children, make sure we only add aria-owned children to the > owning nodes. This avoids a common crash in chrome://bookmarks that > has a confusing crash stack. In order to do this, when > ComputeAccessibilityIsIgnored() is called, the relation cache > must already be updated with the knowledge that the object is owned. > > Do not ever allow owned objects to ever have a "not included in tree" > parent. Therefore, they can never be added as second line children > via the recursion in InsertChild(). > > Also re-remove WalkAllDescendants(), which was it was recently > re-added as a band-aid for the chrome://bookmarks crashes. > Without this change, removing WalkAllDescendants() causes assertions > in AXTreeSerializer, when aria-owns points to an unincluded node, > that the same object is being added twice. > > Finally, add better logging and DCHECKs that will help diagnose issues > more quickly. > > Bug: 1100968, 1131848 > Change-Id: I3bb5d069814e144d426b5c3de0991bc41123206f > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2446200 > Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> > Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org> > Cr-Commit-Position: refs/heads/master@{#813955} TBR=dmazzoni@chromium.org,aleventhal@chromium.org Change-Id: Icdc657185e51265e1939d32bd4508bf6cc0b307c No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1100968 Bug: 1131848 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2451509Reviewed-by:
Kristi Park <kristipark@chromium.org> Commit-Queue: Kristi Park <kristipark@chromium.org> Cr-Commit-Position: refs/heads/master@{#813982}
-
Joon Ahn authored
https://screenshot.googleplex.com/7fXF2GjLWEPcAbs Bug: 1125150 Test: browser_tests --gtest_filter=DiagnosticsApp* Change-Id: I77af9ea199c2363636471d3b2b8b1ef739fdc1ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2441531 Commit-Queue: Joon Ahn <joonbug@chromium.org> Reviewed-by:
Zentaro Kavanagh <zentaro@chromium.org> Cr-Commit-Position: refs/heads/master@{#813981}
-
Jimmy Gong authored
Bug: 1106937 Change-Id: Ib40e1fdc8b72731c2b0d55a390fba0367da80f1b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2444797 Commit-Queue: Jimmy Gong <jimmyxgong@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#813980}
-
Jamie Madill authored
When switching to isolated scripts the Lacros testers failed. Disable these tests for now to work around the bug. Bug: angleproject:5124 Change-Id: I5c68ed47be2ac59f039d9139c8e98d7adf3ab701 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2447102Reviewed-by:
Dirk Pranke <dpranke@google.com> Commit-Queue: Jamie Madill <jmadill@chromium.org> Cr-Commit-Position: refs/heads/master@{#813979}
-
Christopher Cameron authored
These functions will be used in capture. Leave the tests in media/gpu/mac, because the tests internally use media::CreateFormatExtensions. Bug: 959962 Change-Id: I14a6c49b1297d505b3780412bab54c4b2abf9d51 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2437477 Commit-Queue: ccameron <ccameron@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#813978}
-
Hui Yingst authored
This CL adds supports for navigating to view destinations with fit type 'FitR' (See table 151 in ISO 32000-1 standard for more details about syntax of "FitR"), which focus the view on a rectangular window specified by the FitR's coordinates parameters. Bug: 55776,535978 Change-Id: I91353e7569830ba306b9d4cc31f32bfb9622c1df Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391735Reviewed-by:
Lei Zhang <thestig@chromium.org> Reviewed-by:
Henrique Nakashima <hnakashima@chromium.org> Commit-Queue: Hui Yingst <nigi@chromium.org> Cr-Commit-Position: refs/heads/master@{#813977}
-
Nicholas Hollingum authored
This CL refactors IsAllowed for borealis into the standard GuestOs approach (i.e. having a pref-keyed singleton). This necessitates minor refactorings of the installer and its tests. Relatedly, this calls for the creation of Borealis prefs, which were also added in the same fashion as the other GuestOs implementations. Bug: b/168763038, b/162562622 Change-Id: Ie153c2a860a174feaa3156801a8415ca99eefcad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2415755Reviewed-by:
Nancy Wang <nancylingwang@chromium.org> Reviewed-by:
Dominic Battré <battre@chromium.org> Reviewed-by:
Daniel Ng <danielng@google.com> Commit-Queue: Nic Hollingum <hollingum@google.com> Cr-Commit-Position: refs/heads/master@{#813976}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/96edaff6ceb3..09e5f06f05dd 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 kristipark@google.com,csharp@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: chromium:1085115,chromium:1105693,chromium:1119472,chromium:1134655 Tbr: kristipark@google.com,csharp@google.com Change-Id: I255e69a3c27bb6bfeb230cf48ab5f7e2be4e6719 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450587Reviewed-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@{#813975}
-
chromium-autoroll authored
https://chromium.googlesource.com/openscreen.git/+log/dee4a03873a1..952113a3bdf5 2020-10-05 jophba@chromium.org Improve OFFER message validation 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/+doc/master/autoroll/README.md Bug: None Tbr: jophba@chromium.org Change-Id: Ieeff93ef07069288184b34b140d81946bbb5ec78 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2451350Reviewed-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@{#813974}
-
Nico Weber authored
gyp is long long gone. Hopefully nobody still set this. (If you do: Set the concurrent_links gn arg instead.) Bug: none Change-Id: Ifef44f50825c15d89dff95af7597944bfdf87da0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2449935 Auto-Submit: Nico Weber <thakis@chromium.org> Commit-Queue: Dirk Pranke <dpranke@google.com> Reviewed-by:
Dirk Pranke <dpranke@google.com> Cr-Commit-Position: refs/heads/master@{#813973}
-
Ken Rockot authored
In preparation for upcoming changes, this applies the repo's python auto-formatting to the entire mojom_js_generator.py file to avoid extra noise alongside more meaningful changes. Bug: 1004256 Change-Id: I227d689b4eff4ee2a5f51bba068490f282151cba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450585 Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org> Auto-Submit: Ken Rockot <rockot@google.com> Reviewed-by:
Oksana Zhuravlova <oksamyt@chromium.org> Cr-Commit-Position: refs/heads/master@{#813972}
-
Ben Mason authored
TBR=govind@chromium.org Change-Id: Ib7956c406c40adc8f3a09ad0fbb68a0a71d63fbe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450692Reviewed-by:
Ben Mason <benmason@chromium.org> Reviewed-by:
Krishna Govind <govind@chromium.org> Commit-Queue: Krishna Govind <govind@chromium.org> Cr-Commit-Position: refs/heads/master@{#813971}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/8c063270..7de00dff 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: Ica6f63ae248b5842ca1fd691cba58bdb2761e0d8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2449917Reviewed-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@{#813970}
-
Mohamed Amir Yosef authored
Instead of having its own implementation, this CL uses the recently introduced ColorTrackingIconView in the autofill popup native views. Bug: 1115952 Change-Id: I77ed51c6fc903d8c8f7eee3bd9a1174f69b44ca2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2440672Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org> Cr-Commit-Position: refs/heads/master@{#813969}
-
Edward Lesmes authored
Generate DIR_METADATA files and remove metadata from OWNERS files for //url. Bug: 1113033 Change-Id: Ieb893059e1e253cfb53387de4fc37bcc580aa3af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450925 Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Reviewed-by:
Chris Palmer <palmer@chromium.org> Cr-Commit-Position: refs/heads/master@{#813968}
-
Brian Malcolm authored
This means that for Dasher organizations the manager is the domain (foo.com), but for FlexOrgs the manager will be an email address (user@foo.com). Screenshot (https://screenshot.googleplex.com/9buie7RDDnnRXyo) BUG=chromium:1081272 Change-Id: I689b10ee85e1d48f2f450c003d2e458a0649f151 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2451389Reviewed-by:
Moe Ahmadi <mahmadi@chromium.org> Commit-Queue: Brian Malcolm <bmalcolm@chromium.org> Cr-Commit-Position: refs/heads/master@{#813967}
-
Ilya Sherman authored
R=mpearson@chromium.org Bug: none Change-Id: Ia3500bd41e7cdbb52097340100a5fba28cf2ad3a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2415270 Commit-Queue: Ilya Sherman <isherman@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Reviewed-by:
Weilun Shi <sweilun@chromium.org> Auto-Submit: Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#813966}
-
Eric Orth authored
As was previously only done for address results, also allow non-address results to read a TTL from SOA records for NXDOMAIN and NODATA responses. This allows negative non-address results to be cached (but only for the non-transient NXDOMAIN and NODATA cases). For both address and non-address negative response parsing, do not read any TTLs unless an SOA record is present. But if an SOA record is present, still allow using the min TTL between that record and any other parsed records present (e.g. CNAME records that are still valid to be present in an NXDOMAIN response). Fixed: 1121785 Change-Id: I200f45b60c30d89ee53e45fa2cdb70302b617c09 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2446016 Commit-Queue: Eric Orth <ericorth@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#813965}
-
John Williams authored
This change fixes two related problems, one causing notifications to appear when they shouldn't, and another causing a notification to appear in the media dialog after it has been deleted, causing a crash if it is clicked. Change-Id: Ia78ae95af2afe6d1024e86c12ebacdf0720d84cb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424629Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Reviewed-by:
Takumi Fujimoto <takumif@chromium.org> Reviewed-by:
Tommy Steimel <steimel@chromium.org> Commit-Queue: John Williams <jrw@chromium.org> Cr-Commit-Position: refs/heads/master@{#813964}
-
Findit authored
This reverts commit f13525f7. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 813940 as the culprit for failures in the build cycles as shown on: https://analysis.chromium.org/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtL2YxMzUyNWY3MzYzNzNmOGFhM2ZhNWQ1YzQxY2Y3ZTcxNTExYTc0MDIM Sample Failed Build: https://ci.chromium.org/b/8867243040948303664 Sample Failed Step: compile Original change's description: > Roll Dawn from df909306835a to b04a92f01be0 (1 revision) > > https://dawn.googlesource.com/dawn.git/+log/df909306835a..b04a92f01be0 > > 2020-10-05 enga@chromium.org Add a per-thread proc table using thread local storage > > 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 kainino@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: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: kainino@google.com > Change-Id: I5b8a66c618951312fdc5d3ede4f0c861ef17cd30 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450581 > Reviewed-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@{#813940} Change-Id: If43f8e52042eb5c6d31f7896ceeb6d56b6c00e1f No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: None 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 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450792 Cr-Commit-Position: refs/heads/master@{#813963}
-
Lucas Radaelli authored
Reland explanation: A test I wrote tested specific size values for the semantic tree. The chrome a11y code that creates the tree for us is non-deterministic, so we can't check for a specific tree size. I updated the tests to only test for a minimum threshold, which is fine in this case here. This is a reland of fdae2298 Original change's description: > [fuchsia][a11y] Sends full semantic tree when semantics are enabled. > > This change fixes the bug where chrome was sending the full semantic tree only for the first time that semantics were enabled. This happened because the semantic tree was not getting cleared on the chrome side when disabled. when semantic were disabled / enabled, the events fired on the tree included only the diffs from the previous state of the tree. > > Test: web_engine_browsertests > > Bug: fuchsia:59680, 1134147 > Change-Id: I8266d6436f9bfb9ee9e89a0f46c0916bac7a5e75 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2442646 > Commit-Queue: Lucas Radaelli <lucasradaelli@google.com> > Reviewed-by: Sergey Ulanov <sergeyu@chromium.org> > Reviewed-by: Sharon Yang <yangsharon@chromium.org> > Cr-Commit-Position: refs/heads/master@{#813771} Bug: fuchsia:59680 Bug: 1134147 Change-Id: I606b7628c480b775c04d84894faaba73f74789c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450704 Commit-Queue: Lucas Radaelli <lucasradaelli@google.com> Auto-Submit: Lucas Radaelli <lucasradaelli@google.com> Reviewed-by:
Sharon Yang <yangsharon@chromium.org> Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Cr-Commit-Position: refs/heads/master@{#813962}
-
Malay Keshav authored
Adds fieldtrial testing config for Viz GLSolidColorQuad fast draw experiment. Bug: 1134771 Change-Id: Ia30ba3b1c23a2b980993556d8f90c9f98a57d72d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450912Reviewed-by:
Steven Holte <holte@chromium.org> Commit-Queue: Malay Keshav <malaykeshav@chromium.org> Cr-Commit-Position: refs/heads/master@{#813961}
-
James Hawkins authored
Bug: 1045266 Test: OSSettingsInternetSubpage* R=khorimoto@chromium.org Change-Id: Ic4c1409828456121bd66f80700f23990ced14742 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2446191 Commit-Queue: James Hawkins <jhawkins@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#813960}
-
Jesse Schettler authored
Instead of firing custom events when dropdown selections are changed, use data bindings to set the scanning-app element's properties to the selected values. Bug: 1059779 Test: Select a scanner and verify its capabilities are obtained. Change-Id: If8927a4898dca25720c7f8550fe640fad160178a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2448668Reviewed-by:
Jimmy Gong <jimmyxgong@chromium.org> Commit-Queue: Jesse Schettler <jschettler@chromium.org> Cr-Commit-Position: refs/heads/master@{#813959}
-
Leonard Grey authored
Bug: 1014639 Change-Id: I550f129e9a72cc371b5bdfa06be3c38280c10db5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450703 Auto-Submit: Leonard Grey <lgrey@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#813958}
-
Frank Liberato authored
Rather than create one VideoProcessor per wrapper, create one per TextureSelector. This reduces the number of required processors to one per decoder init, rather than one per picture buffer. Bug: 1133568 Change-Id: I87d58c49742e083ca3cdf3c67841a153375f1a4a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2441290Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Frank Liberato <liberato@chromium.org> Cr-Commit-Position: refs/heads/master@{#813957}
-
Dale Curtis authored
Cross-origin audio is still allowed to play out, it just can't be captured by the containing page. Bug: 1128657, 1134679 Test: Unit tests added. Change-Id: Id4c73e315072b8683e45a2ddf929d534f1da9928 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450390 Auto-Submit: Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Will Cassella <cassew@google.com> Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#813956}
-
Aaron Leventhal authored
When adding children, make sure we only add aria-owned children to the owning nodes. This avoids a common crash in chrome://bookmarks that has a confusing crash stack. In order to do this, when ComputeAccessibilityIsIgnored() is called, the relation cache must already be updated with the knowledge that the object is owned. Do not ever allow owned objects to ever have a "not included in tree" parent. Therefore, they can never be added as second line children via the recursion in InsertChild(). Also re-remove WalkAllDescendants(), which was it was recently re-added as a band-aid for the chrome://bookmarks crashes. Without this change, removing WalkAllDescendants() causes assertions in AXTreeSerializer, when aria-owns points to an unincluded node, that the same object is being added twice. Finally, add better logging and DCHECKs that will help diagnose issues more quickly. Bug: 1100968, 1131848 Change-Id: I3bb5d069814e144d426b5c3de0991bc41123206f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2446200 Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#813955}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/6d93a63356e1..afe6ca45b6da 2020-10-05 bclayton@google.com Merge changes I48e99f11,I1a914ff6 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: Idadaba65112faf8228f152f106f1156aa076c241 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450852Reviewed-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@{#813954}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/c9e3d3e3a7e0..d93ee76664c7 2020-10-05 patrick.brosset@microsoft.com New jump-to-var feature in the Styles pane 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: chromium:1124707 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I01a9a81b0dd1d4a10a1efeb64880b61af1b2a37b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450583Reviewed-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@{#813953}
-
Tina Wang authored
Also added a helper api for setting the policy to integer. Bug: 1131052, 1065522 Change-Id: I2c745f2e145c932fab21396afbd9e2689aba9d4c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2443635 Commit-Queue: Tina Wang <tinazwang@chromium.org> Reviewed-by:
Mike Dougherty <michaeldo@chromium.org> Cr-Commit-Position: refs/heads/master@{#813952}
-