- 13 Mar, 2020 40 commits
-
-
Natalie Chouinard authored
This is a follow up to https://crrev.com/i/2756704. Bug: 1047357 Change-Id: I850d2478e978d9dab188f9a2a0913ac30a2083c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101716 Commit-Queue: Gang Wu <gangwu@chromium.org> Auto-Submit: Natalie Chouinard <chouinard@chromium.org> Reviewed-by:
Gang Wu <gangwu@chromium.org> Cr-Commit-Position: refs/heads/master@{#750248}
-
Sean Gilhuly authored
There are variants of viz_unittests that use SkiaRenderer Dawn if it is enabled in the build, and variants of cc_unittests are underway. Add them to the SkiaRenderer Dawn FYI bot, which builds with the gn arg "use_skia_dawn = true". Bug: 1021566 Change-Id: Ia0d96a9389308f45e4a697455f396d69d7d20db4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2094758Reviewed-by:
Yuly Novikov <ynovikov@chromium.org> Commit-Queue: Sean Gilhuly <sgilhuly@chromium.org> Cr-Commit-Position: refs/heads/master@{#750247}
-
Charlie Hu authored
This CL migrates UnsizedMedia from feature policy to document policy. Following web tests are being migrated: - unsized-media.tentative.https.sub.html - unsized-media-reporting.html Following web tests are removed, because document policy currently does not have a js API to list all features available. - feature-policy-unsized-media-disabled.html - feature-policy-unsized-media-enabled.html Bug: 993790 Change-Id: Id5e0189c0277c940177460380970eab0015109d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2097028 Commit-Queue: Charlie Hu <chenleihu@google.com> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Reviewed-by:
Philip Jägenstedt <foolip@chromium.org> Reviewed-by:
Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#750246}
-
Robbie McElrath authored
This CL moves the Java-side definition of the kGenericSensorExtraClasses Feature from ChromeFeatureList to a new DeviceFeatureList class that lives in //services/device/public/java. This will allow non-Chrome embedders to query the status of the Feature from Java. Bug: 1058597 Change-Id: Iab3c75fea6c8755de52714be7776547a774842d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095445 Commit-Queue: Robbie McElrath <rmcelrath@chromium.org> Reviewed-by:
Henrique Nakashima <hnakashima@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#750245}
-
Oksana Zhuravlova authored
TBR=dmurph@chromium.org Bug: 1061251 No-Try: true Change-Id: I30bbc831be9069b6b246242f3ed4eeb46576e65c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103247 Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org> Reviewed-by:
Oksana Zhuravlova <oksamyt@chromium.org> Cr-Commit-Position: refs/heads/master@{#750244}
-
Aaron Leventhal authored
There is a discrepancy between BlinkAXTreeSource::GetChildren() and BlinkAXTreeSource::GetParent(). - GetChildren() does not return direct children when they are ignored and not included in the tree. This is because when AXNodeObject::InsertChild() visits an object that is ignored and not included in tree, it recurses and inserts the next generation. - GetParent() always returns the direct parent. This discrepancy an lead to confusion within AXTreeSerializer, with respect to analyzing reparenting. Bug: 651614 Change-Id: I4e4c8c6a2900cf5516cc98f3b260e619220ea7e9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095882 Auto-Submit: Aaron Leventhal <aleventhal@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Reviewed-by:
Adam Ettenberger <Adam.Ettenberger@microsoft.com> Reviewed-by:
Jacques Newman <janewman@microsoft.com> Commit-Queue: Mounir Lamouri <mlamouri@chromium.org> Cr-Commit-Position: refs/heads/master@{#750243}
-
Oksana Zhuravlova authored
This reverts commit 823317ab. Reason for revert: unit_tests failing on https://ci.chromium.org/p/chromium/builders/ci/Linux%20Tests%20%28dbg%29%281%29/87477 and https://ci.chromium.org/p/chromium/builders/ci/Win%207%20Tests%20x64%20%281%29/64989 Original change's description: > [Profiles] Record state of profiles on session start > > This CL introduces new metrics about profile representation state that > get recorded on session start: > - Profile.State.Avatar > - Profile.State.LastUsed > - Profile.State.Name > - Profile.State.UnconsentedPrimaryAccountType > all with 6 suffixes that zoom into particular subpopulations of users. > > Bug: 1060113 > Change-Id: Ifdb7dff6638ba29896e33e4f99086c8ca6e21b00 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2096697 > Commit-Queue: Jan Krcal <jkrcal@chromium.org> > Reviewed-by: Alex Ilin <alexilin@chromium.org> > Reviewed-by: David Roger <droger@chromium.org> > Auto-Submit: Jan Krcal <jkrcal@chromium.org> > Cr-Commit-Position: refs/heads/master@{#750107} TBR=droger@chromium.org,jkrcal@chromium.org,alexilin@chromium.org Change-Id: I2c6a43c3fd5be4c0eb3d73f66007c6f1b209060a No-Presubmit: true No-Tree-Checks: true No-Try: false Bug: 1060113 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2102779 Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org> Reviewed-by:
Oksana Zhuravlova <oksamyt@chromium.org> Cr-Commit-Position: refs/heads/master@{#750242}
-
Robbie McElrath authored
This moves ChromeFeatureList.setTestFeatures to a new base.FeatureList class so it can be shared by other *FeatureList implementations. Eventually this class will the the primary method of querying Feature state, but for now it only handles test configuration. See crrev.com/c/2095445 and the bug for more information. Bug: 1060097 Change-Id: Idd0c8ebc447f9f936192f81fc1465600f28ad7d7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2099470Reviewed-by:
Henrique Nakashima <hnakashima@chromium.org> Reviewed-by:
Richard Coles <torne@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Commit-Queue: Robbie McElrath <rmcelrath@chromium.org> Cr-Commit-Position: refs/heads/master@{#750241}
-
Matt Menke authored
A number of browser tests use URLLoaderInterceptors solely to look at parameters for requests, and they have similar boilerplate code to set that up. This CL moves URLLoaderMonitor from web_request_apitest to content/public/test/, and switches over a couple browser tests to use it. Bug: 1052148 Change-Id: Id1e9a474ecd77017659f471a54621d0b9c35b0ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2092276Reviewed-by:
Karan Bhatia <karandeepb@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Reviewed-by:
Min Qin <qinmin@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Shivani Sharma <shivanisha@chromium.org> Commit-Queue: Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#750240}
-
Aaron Leventhal authored
By unifying AddChildren() methods, the code is easier to follow and harder to break. NOTRY=true Bug: None Change-Id: I385a73fa5bb72cb4b733a4f42bd9f35727660ec0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101372 Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Reviewed-by:
Nektarios Paisios <nektar@chromium.org> Cr-Commit-Position: refs/heads/master@{#750239}
-
Oksana Zhuravlova authored
TBR=jbudorick@chromium.org Bug: 1061249 No-Try: true Change-Id: Ia8392d4bb8c697cea1bd04d7a67cdbbb4f571bc1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103254 Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org> Reviewed-by:
Oksana Zhuravlova <oksamyt@chromium.org> Reviewed-by:
John Budorick <jbudorick@chromium.org> Cr-Commit-Position: refs/heads/master@{#750238}
-
Garrett Beaty authored
The dummy GPU builders are triggered by non-branched builders that won't have the bucketed_triggers property set. Bug: 1061502 No-Try: true Change-Id: I0054470418bd0736f4e256c5ae49680799362e71 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103249 Commit-Queue: John Budorick <jbudorick@chromium.org> Reviewed-by:
John Budorick <jbudorick@chromium.org> Auto-Submit: Garrett Beaty <gbeaty@chromium.org> Cr-Commit-Position: refs/heads/master@{#750237}
-
zhaoyangli authored
Config mb so that this try builder can build with needed gn configs. Bug: 943883 Change-Id: Iad397828705170bf88040922cb4a8d1d74e9dd95 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101723Reviewed-by:
Aaron Gable <agable@chromium.org> Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org> Cr-Commit-Position: refs/heads/master@{#750236}
-
Sahir Vellani authored
Put new implementation of ResizeObserver::observe behind ResizeObserverUpdates flag to prevent compat issues until the final version of Resize Observer is shipped. No JavaScript error shold be thrown when unsupported second argument is passed to ResizeObserver::observe(). Issue was introduced in the following CL: http://crrev.com/c/2004051 Bug: 1056535 Change-Id: I7e6d319d14f9d318e0f68ea3e056cfa27eb7f937 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2077280 Commit-Queue: Sahir Vellani <sahir.vellani@microsoft.com> Reviewed-by:
Philip Rogers <pdr@chromium.org> Reviewed-by:
Daniel Libby <dlibby@microsoft.com> Cr-Commit-Position: refs/heads/master@{#750235}
-
yilkal authored
This Cl modifies AppActivityRegistry to correctly handle corner cases where applications are re-installed by doing the following: 1. If the running active time of an app is non-zero restore the application when initializing AppActivityRegistry even if the application is uninstalled. 2. Only remove entries in CleanRegistry if the application is uninstalled, has no unreported activities and its running active time is zero. Bug: 1060340 Change-Id: Idbefe82a686eaa56d31488d305f93c379d7b2bda Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2097303 Commit-Queue: Yilkal Abe <yilkal@chromium.org> Reviewed-by:
Aga Wronska <agawronska@chromium.org> Cr-Commit-Position: refs/heads/master@{#750234}
-
Alison Maher authored
Handle fragmentation for fieldset content with a negative margin block start. The following was required to accomplish this: 1. Don't wait to layout fieldset content until there is available space in the current fragment. 2. Break before fieldset content if necessary. Bug: 875235 Change-Id: I0c95fe37694e2a0022ed9222db0a7af13cc958b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2099284 Commit-Queue: Alison Maher <almaher@microsoft.com> Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#750233}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/658be97b1940..acd3faab763a git log 658be97b1940..acd3faab763a --date=short --first-parent --format='%ad %ae %s' 2020-03-13 taylori@google.com Merge "ui: Use track name helper for thread tracks" 2020-03-13 hjd@google.com Merge "ui: Fix percentage in thread state label" 2020-03-13 fmayer@google.com Merge "Revert^2 "Assert extra_guardrails fails on user."" Created with: gclient setdep -r src/third_party/perfetto@acd3faab763a 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: Ifca881095f3a2bf1e199d9e30252ffb7bff09106 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103031Reviewed-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@{#750232}
-
Stephen Chenney authored
A previous patch added clamping for sub-pixel borders to ensure they did not round to zero size. The change was done in paint code, leaving the borders as sub-pixel sized in layout. The code prior to that patch clamped the borders during style conversion but did not account for zoom, meaning borders disappeared under zoom. This change removes the clamping in paint and reverts to clamping in the style conversion code, only this time accounting for zoom when considering whether to clamp or not. This will prevent borders growing too large as content is made larger, while preventing sub-pixel borders from disappearing as content is made smaller. Design Doc: https://docs.google.com/document/d/1fAYkOFxp2Luh6OOoXxtwOehmvNRGNss58ibQtVXL0Tw/edit?usp=sharing Bug: 763402, 834489 Change-Id: Iba2ae80b0a981736b93453c1058fd586ba10212c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2097514 Commit-Queue: Stephen Chenney <schenney@chromium.org> Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#750231}
-
Anastasiia Nikolaienko authored
Screenshot: http://screen/eqiMqP4ssYd Bug: 1043108 Change-Id: I04526e314d7666e1b8d5ba71deed50f7cb0f4ba7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2096556Reviewed-by:
Kush Sinha <sinhak@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Anastasiia Nikolaienko <anastasiian@chromium.org> Cr-Commit-Position: refs/heads/master@{#750230}
-
Min Qin authored
BUG=1061042 Change-Id: I91c3d60d0f9be69fb8ed82b3ca8f67434b4b84c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2100716 Commit-Queue: Min Qin <qinmin@chromium.org> Reviewed-by:
Xing Liu <xingliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#750229}
-
Fredrik Söderqvist authored
Change-Id: Ie215b673d393b799ed51b669959b19e94b075e95 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2102728 Auto-Submit: Fredrik Söderquist <fs@opera.com> Commit-Queue: Philip Rogers <pdr@chromium.org> Reviewed-by:
Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#750228}
-
Mario Sanchez Prada authored
This CL converts the message that notifies the browser process of changes in the location of accessibility objects in Blink's accessibility tree. Bug: 1010831 Change-Id: I220a005183012b8a509948711b5766f384cced4c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078914 Commit-Queue: Mario Sanchez Prada <mario@igalia.com> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#750227}
-
Ayu Ishii authored
This change removes the previous iteration of WebOTP, SMS Receiver API, which we ran for Origin Trial. This is now being removed in favor of the credential management version, WebOTP API [1]. WebOTP API Explainer: https://github.com/WICG/WebOTP I2E ending in M80: https://groups.google.com/a/chromium.org/d/topic/blink-dev/-bdqHhCyBwM/discussion Bug: 1045526 Change-Id: I1e73bed5018c814770fa34edcf64daafd234a543 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2097041Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Commit-Queue: Ayu Ishii <ayui@chromium.org> Cr-Commit-Position: refs/heads/master@{#750226}
-
Yilkal Abe authored
This reverts commit 79024af7. Reason for revert: This revert is required because there are scenarios where the profile becomes supervised user after the navigation observer is supposed to be created. i.e. When SupervisedUserNaivgationObserver::MaybeCreateForWebContents is called the user profile is not marked as supervised hence the navigation observer is not created. This resulted in the crashes reported in the bug below. Bug: 1061427 Original change's description: > Only use SupervisedUserNavigationObserver for child accounts. > > This CL makes sure that SupervisedUserNavigationObserver is > created only for supervised user accounts. This saves memory > and processing time. > > Bug: 1043232 > Change-Id: I5d13ce0261d07c29384f5ba5dc83e420ed3138dd > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008315 > Reviewed-by: Scott Violet <sky@chromium.org> > Reviewed-by: Dan S <danan@chromium.org> > Commit-Queue: Yilkal Abe <yilkal@chromium.org> > Cr-Commit-Position: refs/heads/master@{#733750} TBR=sky@chromium.org,danan@chromium.org,yilkal@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1043232 Change-Id: I1767afe66b32f34736af2497793d59f598cb61b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2102764Reviewed-by:
Yilkal Abe <yilkal@chromium.org> Commit-Queue: Yilkal Abe <yilkal@chromium.org> Cr-Commit-Position: refs/heads/master@{#750225}
-
Danyao Wang authored
The new test is a regression test to make sure the manifest icon download is only subject to the CSP policy of the initiator frame. Bug: 1055360 Change-Id: I0efd8b7532b1d6c6174b95d6dacea0bef8a20767 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2097535 Commit-Queue: Danyao Wang <danyao@chromium.org> Reviewed-by:
Rouslan Solomakhin <rouslan@chromium.org> Cr-Commit-Position: refs/heads/master@{#750224}
-
Dave Tapuska authored
In an effort to move compositing layer tree ownership into blink change the way rAF aligned input works. Previously the content layer captured the begin frame dispatched input then let blink know about the main frame. Tell blink now and let blink ask content layer to dispatch rAF aligned input. Eventually all this will go away when blink does everything. Change-Id: I86abe4da3e9005c6973acc8b554c6a87bb9fa485 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101295Reviewed-by:
danakj <danakj@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Cr-Commit-Position: refs/heads/master@{#750223}
-
Xiaocheng Hu authored
FontPreloadManagerTest.OptionalFontFastPreloading is flaky, which might be caused by a race between a timeout firing and a ResourceFinishObserver notification. This patch disables the timeout as a tentative fix. Bug: 1060821 Change-Id: I450b9783c20525a407bc8e3cac19be7b18927b45 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101245Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> Cr-Commit-Position: refs/heads/master@{#750222}
-
Pavel Feldman authored
Permission overrides were implemented for the automation purposes (WebDriver, Puppeteer, Playwright, etc). Before this change, protocol required concrete |origin| to be specified in order to override the permissions. This change makes this |origin| input parameter optional and allows global permission override within the given browser context. TBR=mlamouri for updating chrome/ due to changes in content/ semantics. Change-Id: I35e78307643b179a46e296d81f261e5b596c6252 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095668 Commit-Queue: Pavel Feldman <pfeldman@chromium.org> Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Reviewed-by:
Andrey Kosyakov <caseq@chromium.org> Cr-Commit-Position: refs/heads/master@{#750221}
-
Sahel Sharify authored
After this cl payment sheets on Desktop and Android will show "Continue" rather than "Pay" when a 3rd party(i.e. non-autofill) payment app is selected. Bug: 1055557 Change-Id: I1717703d50e33df5cdc4a3f0e900b29072df19c4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101690 Commit-Queue: Sahel Sharify <sahel@chromium.org> Reviewed-by:
Rouslan Solomakhin <rouslan@chromium.org> Cr-Commit-Position: refs/heads/master@{#750220}
-
Anatoliy Potapchuk authored
Bug: 1061418 Change-Id: I063b863e61b1c788a83c213eef41603e3ad71b1f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2093223 Commit-Queue: Anatoliy Potapchuk <apotapchuk@chromium.org> Reviewed-by:
Alex Ilin <alexilin@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Tommy Li <tommycli@chromium.org> Cr-Commit-Position: refs/heads/master@{#750219}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/dba14f0f51b4..4d806b9daa24 git log dba14f0f51b4..4d806b9daa24 --date=short --first-parent --format='%ad %ae %s' 2020-03-13 aerotwist@chromium.org Updates npm_test to work on Windows Created with: gclient setdep -r src/third_party/devtools-frontend/src@4d806b9daa24 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Bug: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I61401ae15a6ecdc7574b16d8c08a1dec6ab10fae Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2102756Reviewed-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@{#750218}
-
yilkal authored
This Cl ensures that app activity values will not be reported if app activity data reporting toggle is set to false in PerAppTimeLimits policy. Bug: 1042477 Change-Id: Id400aebd71be7a2eac5c35f1b59c4c70dc7f6f33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2096914 Commit-Queue: Yilkal Abe <yilkal@chromium.org> Reviewed-by:
Sergey Poromov <poromov@chromium.org> Reviewed-by:
Aga Wronska <agawronska@chromium.org> Cr-Commit-Position: refs/heads/master@{#750217}
-
John Budorick authored
Follow-up to crrev.com/c/2101384 to account for crrev.com/c/2093536 Bug: 1061198 Change-Id: I3085da3365052e5f0f9384f76bc1511fd27ffad3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2102774 Commit-Queue: John Budorick <jbudorick@chromium.org> Commit-Queue: Ben Pastene <bpastene@chromium.org> Auto-Submit: John Budorick <jbudorick@chromium.org> Reviewed-by:
Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#750216}
-
Nina Satragno authored
Some older authenticators support internal user verification but not UV token or getting UV retries. Before this patch, if internal user verification failed for one of these authenticators we would either drop the request or show an error to the user. With this change, when an authenticator supports falling back to PIN, chrome will show the PIN dialog and alert the user. Some authenticators will immediately fail when sent a uv = required request if their internal uv is locked. To mitigate this behaviour, a touch is requested from devices that return a response too quickly. Bug: 999153 Change-Id: Icffccf208951cd33227fd532b6a569dcc8d93c99 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2097121 Commit-Queue: Nina Satragno <nsatragno@chromium.org> Reviewed-by:
Martin Kreichgauer <martinkr@google.com> Cr-Commit-Position: refs/heads/master@{#750215}
-
Rainhard Findling authored
* Remove ability to focus text-only non-actionable safety check elements and their additional aria labels, as the text in the elements on its own is sufficient for a11y and can be reached by screen readers. * Hide non-essential elements (icons) from aria. Bug: 1060779 Change-Id: Id4bf41f461412d2aa433e051d3518de390fcb63b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2100823Reviewed-by:
dpapad <dpapad@chromium.org> Commit-Queue: Rainhard Findling <rainhard@chromium.org> Cr-Commit-Position: refs/heads/master@{#750214}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/27402f3ffd34..8926292ad6bb git log 27402f3ffd34..8926292ad6bb --date=short --first-parent --format='%ad %ae %s' 2020-03-13 chrome-bot@chromium.org Update config settings by config-updater. 2020-03-13 lamontjones@chromium.org api: add UNVERIFIED_CHROME_BENCHMARK_PERF_FILE 2020-03-13 lamontjones@chromium.org api: compile protos. 2020-03-13 engeg@google.com chromite: add dev-libs/icu to OTHER_CHROME_PACKAGES 2020-03-13 engeg@google.com api service: remove 'quick hack for testing' 2020-03-12 gredelston@google.com Set up pytest 2020-03-12 morg@google.com Enable RVC Android PFQ configs (VM and container) 2020-03-12 sanikak@chromium.org auto_updater: update GetPayloadPropsFile method to ssh into devserver 2020-03-12 tcwang@google.com afdo: Remove indirect calls from AFDO profiles 2020-03-12 vapier@chromium.org licensing: delete unused debug constant 2020-03-12 ayatane@chromium.org metrics: Handle cases where system clock jumps backward Created with: gclient setdep -r src/third_party/chromite@8926292ad6bb If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/chromite-chromium-autoroll Please CC chrome-os-gardeners@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:chromeos-kevin-rel Bug: None Tbr: chrome-os-gardeners@google.com Change-Id: Ia64a72ee748ff0c63e5585d3f9649d3f8da37fa0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2102754Reviewed-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@{#750213}
-
Clark DuVall authored
This is a reland of 9ced8b0f Changes from patch set 1 on. We no longer prepend "/." to paths for L/M where it's not needed since L adds /vendor/lib to all class loaders which breaks the test. Original change's description: > Reland "[WebLayer] Use crazy linker for M- and "/." trick for N+" > > This is a reland of 9b660407 > > Original change's description: > > [WebLayer] Use crazy linker for M- and "/." trick for N+ > > > > Instead of copying libraries on M-, this changes to using the crazy > > linker, which loads the library without any knowledge of what libraries > > have been loaded by the system linker. This requires manual JNI > > registration. To make sure we only register WebLayer JNI when needed, > > a minimal set of JNI methods is registered, and the full set is > > registered later if we require WebView compatibility. > > > > In N+, we switch to prepending "/." to library paths instead of using > > symlinks, which allows us to avoid writing any files to the apps data > > directory. This simplifies the interface quite a bit, allowing > > initializeWebViewCompatibilityMode() to be sync instead of async. I will > > follow up with the Android team to make sure we have a better solution > > for future versions of Android. > > > > The API has not been used in the client app yet, so it should be safe > > to remove M- support for the copy library approach in the > > implementation. The old version of initializeWebViewCompatibilityMode() > > was kept so the WebLayer API version compat tests would still pass. > > > > TBR=agrieve@chromium.org > > > > Bug: 1051358 > > Change-Id: I2cd5ae0e025feaeb5c41cf9ddfafc91cd09fbad7 > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2090024 > > Commit-Queue: Clark DuVall <cduvall@chromium.org> > > Reviewed-by: Richard Coles <torne@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#749973} > > TBR=torne@chromium.org,agrieve@chromium.org > > Bug: 1051358 > Change-Id: Iecccefbbfdaa14c91a8d8b1a50543f4929912704 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101978 > Reviewed-by: Clark DuVall <cduvall@chromium.org> > Commit-Queue: Clark DuVall <cduvall@chromium.org> > Cr-Commit-Position: refs/heads/master@{#750056} TBR=torne@chromium.org,agrieve@chromium.org Bug: 1051358 Change-Id: If9eb267c6e33cb76370bb19783d8cbf4b1834429 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2102772Reviewed-by:
Clark DuVall <cduvall@chromium.org> Commit-Queue: Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#750212}
-
Daniel Cheng authored
Allowing arbitrary amounts of shared memory to be mapped can make it easier for an attacker to bypass ASLR as documented in https://googleprojectzero.blogspot.com/2019/04/virtually-unlimited-memory-escaping.html Bug: 1056572 Change-Id: I812542e2b3d9e7842a7ae54bdd837fa956a99177 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2083447 Commit-Queue: Daniel Cheng <dcheng@chromium.org> Auto-Submit: Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#750211}
-
Garrett Beaty authored
Bug: 1024644, 1061482 Change-Id: I0b523d9b8b0cd1f73de084190236f1b968772736 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2098857 Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Reviewed-by:
Aaron Gable <agable@chromium.org> Cr-Commit-Position: refs/heads/master@{#750210}
-
Yao Xiao authored
LGTMs to ship: https://groups.google.com/a/chromium.org/g/blink-dev/c/JdAQ6HNoZvk/m/B1aMS33oAAAJ whatwg/html spec: https://github.com/whatwg/html/pull/4293 Bug: 539938 Change-Id: Ib875fe971ff8ab93ed733f6a0c1d4dd3ee5c7489 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095602Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Commit-Queue: Yao Xiao <yaoxia@chromium.org> Cr-Commit-Position: refs/heads/master@{#750209}
-