- 10 Jan, 2020 40 commits
-
-
Reilly Grant authored
This change implements support for filtering serial ports based on a USB vendor and product ID. The naming of the filter properties comes from the Serial API polyfill library where I felt it was important to be specific that this filter will only apply to USB devices and so also implies that the device being requested by the page will be a USB device. This is useful for applications which are targeting a particular model of serial device that is known to be connected over USB and advertises a recognizable vendor ID/product ID pair. Bug: 884928 Change-Id: Ie6a2674911c449ed48d58ea82175fe03bc14c572 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994262Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org> Commit-Queue: Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#730218}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/2076b04d153f..504032e57526 git log 2076b04d153f..504032e57526 --date=short --first-parent --format='%ad %ae %s' 2020-01-10 brianosman@google.com SkRuntimeEffect: Fix 'in' variables in CPU backend 2020-01-10 nifong@google.com Add vis of android device clip restriction, fix regular clip vis on gpu 2020-01-10 jlavrova@google.com Ellipsis attached to cluster, not word 2020-01-10 reed@google.com Revert "new virtuals for canvas ctm" Created with: gclient setdep -r src/third_party/skia@504032e57526 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 jvanverth@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: jvanverth@google.com Change-Id: I0e998c35838db7f9739c1bed8feb63fb8038af5c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995423Reviewed-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@{#730217}
-
Joe Mason authored
Reland "Re-enable EngineRequestsNoBlockingTest on Win8 by initializing TaskEnvironment with COM disabled" This is a reland of 2dd4658f with a fixed unit test. The original was using CHECK_DEATH to test a code path that called DCHECK. Original change's description: > Re-enable EngineRequestsNoBlockingTest on Win8 by initializing TaskEnvironment with COM disabled > > R=fdoray > > Bug: 947576 > Change-Id: I1f901367e6fcc5243f34f50e5704b68727a40731 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1990135 > Commit-Queue: Joe Mason <joenotcharles@chromium.org> > Reviewed-by: François Doray <fdoray@chromium.org> > Cr-Commit-Position: refs/heads/master@{#729802} R=fdoray Bug: 947576 Change-Id: If83301ccc260f5ca6911c7ee787eb7719ef2c064 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993842Reviewed-by:
François Doray <fdoray@chromium.org> Commit-Queue: Joe Mason <joenotcharles@chromium.org> Cr-Commit-Position: refs/heads/master@{#730216}
-
Xianzhu Wang authored
We have been correctly ignoring occlusion from outside of the subtree of a pixel-moving filter in the stack of OcclusionTracker (which leads to correct occlusion inside of the subtree), but when we get the occlusion of a render surface, previously we returned the current occlusion of the parent render surface even if the current render surface has pixel-moving filter, causing the render surface incorrectly occluded. Now add a flag in the stack indicating that the render surface doesn't inherit parent occlusion, and OcclusionTracker::GetCurrentOcclusionForContributingSurface() should not return the parent occlusion when the flag is set. Bug: 1040288 Change-Id: I505b079d62186a404b1be1c83c6cbccc89c10b8f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994102Reviewed-by:
weiliangc <weiliangc@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#730215}
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC cr-fuchsia+bot@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 Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast Tbr: cr-fuchsia+bot@chromium.org Change-Id: I919bee18e72049473723bbbf42783e4213dee7c3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995424Reviewed-by:
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/a19e6092..d2cad713 Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I94a9189f5f5559c5d0bdfbfcf5fbee0872103a2d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995214Reviewed-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@{#730213}
-
Henrique Nakashima authored
Register them in ChromePreferenceKeys and use SharedPreferencesManager consistently instead of SharedPreferences directly. Bug: 1022108 Change-Id: Iadffe6c5d4a91ad5fde9cc481aaf9048e132d217 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992912 Commit-Queue: Henrique Nakashima <hnakashima@chromium.org> Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Cr-Commit-Position: refs/heads/master@{#730212}
-
Raymond Toy authored
Update the histograms to expire after 2021-01-06, 6 mo after the current expiration; these were set to expire after M81. These histograms still contain useful information on how people use WebAudio. Bug: 1037364, 1037365, 1037366, 1037367, 1037368, 1037369, 1037370, 1037371 Change-Id: I83d7254187d5ec2c60d00513fb54561f83ad60fa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993432 Commit-Queue: Raymond Toy <rtoy@chromium.org> Reviewed-by:
Hongchan Choi <hongchan@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Cr-Commit-Position: refs/heads/master@{#730211}
-
Nicolás Peña Moreno authored
LargestContentfulPaint (aggregating both image and text) is the one we will be using, so we remove the image/text versions from UKM. Change-Id: I0bcca50da7ffb3338ec4f73bf89a9179f4c2b51e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1988594 Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Reviewed-by:
Bryan McQuade <bmcquade@chromium.org> Cr-Commit-Position: refs/heads/master@{#730210}
-
Mohamed Amir Yosef authored
Before this patch: ShouldRecoverPasswordsDuringMerge() checked the feature kDeleteCorruptedPasswords on all platforms to decide whether to try to delete undecryptable passwords during merge. After this patch: The feature is checked only on MacOS. On other platforms, the method always returns false. Change-Id: Icdc621c2b45e91541a088ce2db6f0b32c968a552 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995382 Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org> Commit-Queue: Vasilii Sukhanov <vasilii@chromium.org> Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Auto-Submit: Mohamed Amir Yosef <mamir@chromium.org> Cr-Commit-Position: refs/heads/master@{#730209}
-
John Budorick authored
This bot has been flaky for a while, and it's been excluded from sheriffing since October. Note that this CL does not attempt to switch mastername property values, as that's mostly an implementation detail at this point. Bug: 1014673 Change-Id: I5c01644e4728a407d9679c76d4ccdf9e9d107f5b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994119 Commit-Queue: John Budorick <jbudorick@chromium.org> Commit-Queue: Avi Drissman <avi@chromium.org> Auto-Submit: John Budorick <jbudorick@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#730208}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/110236f3ce70..f6d3cbb28303 git log 110236f3ce70..f6d3cbb28303 --date=short --first-parent --format='%ad %ae %s' 2020-01-10 srisser@google.com Add the PowerVR SDK as a git submodule Created with: gclient setdep -r src/third_party/swiftshader@f6d3cbb28303 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/+/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 Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: I52936bb3560bd8e8b29d744cc193097758c78e53 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995237Reviewed-by:
-
Nicolás Peña Moreno authored
This CL uses the computed timing_allow_passed_ from CORSUrlLoader to determine the Timing-Allow-Origin checks for the ElementTiming and the LargestContentfulPaint APIs. This works since OOR-CORS is now enabled by default. Bug: 1003943 Change-Id: Id571c5a39b2ef7c7565d3a1560a4b66a03ba7fdd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992590 Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/master@{#730206}
-
Xida Chen authored
While debugging, we found that a ReportBeginImpl(Main)Frame could happen before ScheduleTerminate, and then that main/impl frame is never processed (meaning that it didn't report no damage and didn't submit the frame). This CL handles the impl case, main frame handling will be in a separate CL. Bug: 1021963 Change-Id: Ib9a1bd7b894bba3018f120590511c6dba22d1d00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994086Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#730205}
-
Michael Thiessen authored
In order to migrate java.net.URI to GURL the junit tests that rely on java.net.URI need to be moved to a test apk that supports the native library. This change moves the NotificationPlatformBridgeUnitTest unittests from junit to unit_tests (Android only). These tests should be just as fast as they were as junit tests (and much faster than chrome_test_apk unit tests). Bug: 783819 Change-Id: Ia64a3bbd630bb4861c9a405d28582bd97f5ad167 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1991725Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Commit-Queue: Michael Thiessen <mthiesse@chromium.org> Cr-Commit-Position: refs/heads/master@{#730204}
-
Patrick Monette authored
This CL introduces a new class for generating IdType values and makes use of that class where applicable. Bug: 1040280 Change-Id: I88901a12e194def4a6894ad1ecde93549aa62924 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1988831 Commit-Queue: Patrick Monette <pmonette@chromium.org> Reviewed-by:
Fernando Serboncini <fserb@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Victor Miura <vmiura@chromium.org> Reviewed-by:
Łukasz Anforowicz <lukasza@chromium.org> Cr-Commit-Position: refs/heads/master@{#730203}
-
Francois Doray authored
We should minimize the amount of work done when the system is under memory pressure, to allow it to exit that state. Since the "Tab Discards Memory details" log is only used on ChromeOS, this CL removes it on other platforms. Collecting memory details is the culprit for 3% of IO thread hangs, so we shouldn't do it for no reason. Bug: 1040522 Change-Id: Ie4fff140a7024d9372a3888a515466885cce68da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1980282Reviewed-by:
Chris Hamilton <chrisha@chromium.org> Commit-Queue: François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#730202}
-
Maksim Ivanov authored
Add a browser test for the scenario when the sign-in screen extension is first installed at some version, and then the server starts announcing a newer version, so that Chrome eventually fetches, installs and runs it. Bug: 1012892 Change-Id: Iad3537236d56d7c86e02478bd2ff46fea6c0d112 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992420 Commit-Queue: Maksim Ivanov <emaxx@chromium.org> Reviewed-by:
Oleg Davydov <burunduk@chromium.org> Cr-Commit-Position: refs/heads/master@{#730201}
-
Scott Violet authored
And puts the implementation in the single place that needs it. SessionTabHelper is really intended to forward WebContentsObserver related calls to SessionService. SetTabExtensionAppID() isn't that. As SetTabExtensionAppID() was called in a single place, I moved the implementation there. This is part of a larger refactoring I'm doing in hopes of moving SessionTabHelper to a shared location. BUG=1033924 TEST=none Change-Id: Ia70af33908593839d4a22b4ebbc5f9f48c8abc30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994527 Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:
Finnur Thorarinsson <finnur@chromium.org> Cr-Commit-Position: refs/heads/master@{#730200}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/6ddbe2c5b003..4b0705913917 git log 6ddbe2c5b003..4b0705913917 --date=short --first-parent --format='%ad %ae %s' 2020-01-10 yura.yaroshevich@gmail.com [iOS] Reset VT session when H264 encoder malfunction error happen Created with: gclient setdep -r src/third_party/webrtc@4b0705913917 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@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: webrtc-chromium-sheriffs-robots@google.com Change-Id: Id53429d1e8752b1c9904bb5c61485a22c35acee4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995231Reviewed-by:
-
Patrick Monette authored
Bug: 1040794 Change-Id: Iaeffc745b01009500352d2b4be1a907cbbf10a8a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1990211Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Commit-Queue: Patrick Monette <pmonette@chromium.org> Cr-Commit-Position: refs/heads/master@{#730198}
-
Lei Zhang authored
In browser_prefs.cc, both RegisterLocalState() and RegisterProfilePrefs() have lists of registration functions to call. Over time, these pile up so there are now repeated #if cond blocks. Consolidate those and also alphabetize some of the lists that are clearly unsorted. Fix a lint error as well. Change-Id: Ifef2f127fe59e9571bf693efa0421789b0a2cfb4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994670Reviewed-by:
Dominic Battré <battre@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#730197}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/c80b27e14b36..d911a9f90cdf git log c80b27e14b36..d911a9f90cdf --date=short --first-parent --format='%ad %ae %s' 2020-01-10 moragues@google.com mushu: disable hw tests 2020-01-09 saklein@chromium.org Packages controller: Add logging to version endpoint 2020-01-09 jacobraz@google.com flash_ap: add support for Zork and Volteer. 2020-01-09 chrome-bot@chromium.org Update config settings by config-updater. 2020-01-09 mmortensen@google.com Set default field_limit for query_build_logs to show relevant result. 2020-01-09 engeg@google.com paygen: delta_generator runs inside squawking thread 2020-01-09 cjmcdonald@chromium.org Build API: Add GetToolchainPaths endpoint 2020-01-09 cjmcdonald@chromium.org yapf formatting 2020-01-09 cjmcdonald@chromium.org portage_util: Add equery output parser 2020-01-09 cjmcdonald@chromium.org Update generated proto files to ToT Created with: gclient setdep -r src/third_party/chromite@d911a9f90cdf 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: I8114e4f33ac05cf3f3ec27a456b87732b9503d1b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995236Reviewed-by:
-
Eric Stevenson authored
This is a reland of 77bc3255. The original CL had issues for both Chrome and WebView; bundle status wasn't being set early enough. Original change's description: > Android: Make BundleUtils bundle status work with Trichrome. > > This is necessary for Trichrome synchronized ProGuard where we need to > support different values for Chrome and WebView (so we can't use the > same class). > > Right now, BuildConfig.java isn't generated by TrichromeLibrary and so > the version from the main APK will be used. > > Bug: 901465 > Change-Id: I40a4d31b545bdb564a90babf4e49f3df0a597090 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1954934 > Commit-Queue: Eric Stevenson <estevenson@chromium.org> > Auto-Submit: Eric Stevenson <estevenson@chromium.org> > Reviewed-by: Richard Coles <torne@chromium.org> > Reviewed-by: Andrew Grieve <agrieve@chromium.org> > Cr-Commit-Position: refs/heads/master@{#724341} Tbr: agrieve@chromium.org Bug: 901465 Change-Id: Ifcc652c6064052b3c7241c27f43c0bd1dd027b4f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989243Reviewed-by:
Eric Stevenson <estevenson@chromium.org> Reviewed-by:
Richard Coles <torne@chromium.org> Commit-Queue: Eric Stevenson <estevenson@chromium.org> Auto-Submit: Eric Stevenson <estevenson@chromium.org> Cr-Commit-Position: refs/heads/master@{#730195}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/7ba39a0c2e40..920683437e19 git log 7ba39a0c2e40..920683437e19 --date=short --first-parent --format='%ad %ae %s' 2020-01-10 primiano@google.com Merge "Limit the number of sessions per uid to 5" 2020-01-10 fmayer@google.com Merge "Do not use uninitialized Variadic." Created with: gclient setdep -r src/third_party/perfetto@920683437e19 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: I911bafd66d18acdeb3418b5da95195f90041bb57 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995234Reviewed-by:
-
Christian Dullweber authored
Bug: 1027931 Change-Id: Ib3f19724c4241c8f80db4b917c9f510a4ad5534b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993809 Commit-Queue: Christian Dullweber <dullweber@chromium.org> Reviewed-by:
Martin Šrámek <msramek@chromium.org> Cr-Commit-Position: refs/heads/master@{#730193}
-
Vladimir Levin authored
This patch only affects the CSS version of render-subtree. Right now, we keep size containment if the invisible token is present, even if the lock is activated. I don't think this was ever the intent, although the spec language suggests that if 'invisible' is present, we should have size containment. The language is speaking about the attribute version though, so I think we should reword that for CSS. See https://github.com/WICG/display-locking/issues/104 for more discussion. R=chrishtr@chromium.org, rakina@chromium.org Change-Id: Iaf03c234aa27024a76908ef2e14b11a17426703e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993389Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Commit-Queue: vmpstr <vmpstr@chromium.org> Cr-Commit-Position: refs/heads/master@{#730192}
-
Stephen Chenney authored
The previous code disabled the shader fast path whenever respecting image orientation, even when the orientation would not make any different (i.e. for non bitmaps or the default orientation). Fix this by adding Image::HasDefaultOrientation and using it where possible. Bug: 1036181 Change-Id: Ifb8f9163caf6a4352b0c1516664427c5b49d48a0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993840 Commit-Queue: Stephen Chenney <schenney@chromium.org> Reviewed-by:
Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#730191}
-
Chase Phillips authored
Bug: 999001 Change-Id: If3ec271dcec5b479a183c8a3a1da822e86f4e976 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994415 Auto-Submit: Chase Phillips <cmp@chromium.org> Commit-Queue: Victor Costan <pwnall@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#730190}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/google/shaderc/+log/0b9a2992c73d..3f24b6829b3e git log 0b9a2992c73d..3f24b6829b3e --date=short --first-parent --format='%ad %ae %s' 2020-01-10 rharrison@google.com Add reference to Go bindings in README.md (#949) 2020-01-10 dneto@google.com Fix spelling of -finvert-y in doc (#947) Created with: gclient setdep -r src/third_party/shaderc/src@3f24b6829b3e If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/shaderc-chromium-autoroll Please CC radial-bots+chrome-roll@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: radial-bots+chrome-roll@google.com Change-Id: Ibdceaac0814ef138ce828b50d6d6788ef3f4a53f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995232Reviewed-by:
-
Torne (Richard Coles) authored
This was removed from the declare_args section some time ago, but for AOSP system implementors it may be desirable to manually control it. Re-add it as an argument, and document how to use it in the WebView AOSP build guide. Fixed: 1034192 Change-Id: Ic5f890f2ad3677bb76ce87951ee0d7d3f20551b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1976331Reviewed-by:
Nico Weber <thakis@chromium.org> Reviewed-by:
Nate Fischer <ntfschr@chromium.org> Commit-Queue: Richard Coles <torne@chromium.org> Cr-Commit-Position: refs/heads/master@{#730188}
-
Christian Dullweber authored
Test that deleting cache data with a whitelist does not remove TransportSecurityState. Bug: 1040065 Change-Id: I41763b4d9034b8fe4eba7e37e9b03cfe575b2fd0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992083 Commit-Queue: Christian Dullweber <dullweber@chromium.org> Reviewed-by:
-
Olivier Li authored
Set browser state builder dir to avoid file leaks in ios tests in /ios/chrome/browser/ui/activity_services This cl is generated with 'git cl split' This CL was uploaded by git cl split. R=pkl@chromium.org Bug: 546640 Change-Id: I4569f1f4ba2fb24928c14b8640cf97123bff8129 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1991755Reviewed-by:
Peter Lee <pkl@chromium.org> Commit-Queue: Peter Lee <pkl@chromium.org> Auto-Submit: Oliver Li <olivierli@chromium.org> Cr-Commit-Position: refs/heads/master@{#730186}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/ef05f96d6de1..eaacb72383ba git log ef05f96d6de1..eaacb72383ba --date=short --first-parent --format='%ad %ae %s' 2020-01-10 tvanderlippe@chromium.org Migrate console/ to ESM internally 2020-01-10 tvanderlippe@chromium.org Migrate formatter_worker/ to ESM internally 2020-01-10 tvanderlippe@chromium.org Migrate extensions/ to ESM internally 2020-01-10 tvanderlippe@chromium.org Migrate event_listeners/ to ESM internally 2020-01-10 tvanderlippe@chromium.org Migrate components/ to ESM internally 2020-01-10 tvanderlippe@chromium.org Migrate har_importer/ to ESM internally 2020-01-10 aerotwist@chromium.org Migrates changes/ to ESM internally 2020-01-10 aerotwist@chromium.org Migrates browser_sdk/ to ESM internally Created with: gclient setdep -r src/third_party/devtools-frontend/src@eaacb72383ba 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: chromium:1006759 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I84e03b639da6c344f596f824cf9d2279f2f7a3eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994644Reviewed-by:
-
Charlie Reis authored
Filtering IPCs from swapped out RenderViewHosts is no longer necessary now that we have fully shifted to RenderFrameProxyHosts and cleaned up the old dependencies. This CL removes the old filtering logic, along with the RenderViewHostImpl::is_swapped_out_ state, which was only being used for filtering decisions. Bug: 1015882, 745091 Change-Id: I7f30139812684b0ade80d05923f8f237d5454151 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989701Reviewed-by:
Bo <boliu@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Commit-Queue: Charlie Reis <creis@chromium.org> Cr-Commit-Position: refs/heads/master@{#730184}
-
Vincent Boisselle authored
This is a reland of 34d462f6 Original change's description: > Add end-to-end tests for demographic metrics in UMA and UKM > > Bug: 992573 > Change-Id: I5a27682828538c72fbe8fc71c78cbadc8fdef23e > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872643 > Commit-Queue: Roger McFarlane <rogerm@chromium.org> > Reviewed-by: Alexei Svitkine <asvitkine@chromium.org> > Reviewed-by: Robert Kaplow <rkaplow@chromium.org> > Cr-Commit-Position: refs/heads/master@{#728621} Bug: 992573 Change-Id: Ib6cf80256a8adbcb15a23814f6431d7ea600a1b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994003Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Commit-Queue: Vincent Boisselle <vincb@google.com> Cr-Commit-Position: refs/heads/master@{#730183}
-
Sylvain Defresne authored
The target //third_party/test_fonts copy the files to the same location for all toolchains, so when using multiple toolchains (which is common when targeting iOS) and multiple toolchains depends on that target (it can happen when building cronet), ninja presents a warning because some files are copied to the same location. Change the target to copy the files to $root_out_dir instead of $root_build_dir which correspond to the same directory for the default toolchain but to a toolchain specific directory for the secondary toolchains (this is consistent with the other target that copy fonts defined in //skia). Also fix iOS build to also use a bundle for the fonts (since iOS apps cannot access file outside of the application bundle). Bug: none Change-Id: Ic5e3290a495f67744f9d676800e16612ffefcbc9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992428Reviewed-by:
Dominik Röttsches <drott@chromium.org> Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Stephen White <senorblanco@chromium.org> Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Commit-Queue: Sylvain Defresne <sdefresne@chromium.org> Cr-Commit-Position: refs/heads/master@{#730182}
-
Luke Zielinski authored
TBR=robertma Change-Id: Ie2e46a32932b19544eb15d1b2f8080c75aab3e87 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994602Reviewed-by:
Luke Z <lpz@chromium.org> Reviewed-by:
Robert Ma <robertma@chromium.org> Commit-Queue: Luke Z <lpz@chromium.org> Cr-Commit-Position: refs/heads/master@{#730181}
-
Manuel Rego Casasnovas authored
In r729750 we added a regression test as an internal test but it's better to move the test into WPT. BUG=1036644 Change-Id: I16bcfc99ef2faff90bd03020a8cc4809689d2d5c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994299Reviewed-by:
Philip Rogers <pdr@chromium.org> Commit-Queue: Manuel Rego <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#730180}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/f72e48dd2ff0..2076b04d153f git log f72e48dd2ff0..2076b04d153f --date=short --first-parent --format='%ad %ae %s' 2020-01-10 reed@google.com new virtuals for canvas ctm Created with: gclient setdep -r src/third_party/skia@2076b04d153f 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 jvanverth@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: jvanverth@google.com Change-Id: I4b3c5bd602e00fcbe3d5fc8cb3b760c8ae464ab7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995303Reviewed-by:
-
