- 10 Dec, 2020 40 commits
-
-
http://crrev.com/835582Eugene Zemtsov authored
Change-Id: Id48ff016d5162417624988478c693408bb9f4e4f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583865Reviewed-by:
Hirokazu Honda <hiroh@chromium.org> Commit-Queue: Eugene Zemtsov <eugene@chromium.org> Cr-Commit-Position: refs/heads/master@{#835601}
-
Antonio Sartori authored
This change fixes a few blink unittests so that they work with the feature PolicyContainer enabled. This is a preparatory CL to enable that feature by default. Bug: 1130587 Change-Id: I9ac10a4c1c06b77721aebf0b983992adebf0c4de Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2582221Reviewed-by:
Mike West <mkwst@chromium.org> Commit-Queue: Antonio Sartori <antoniosartori@chromium.org> Cr-Commit-Position: refs/heads/master@{#835600}
-
Swapnil authored
This CL adds a new flag |override_update_url| to the ExtensionSettings policy. If the flag is set to true, update URL from the ExtensionInstallForceList or ExtensionSettings policy will be used for updates, not only for the first install. The flag is taken into consideration in these 2 cases: 1) Extension is listed in ExtensionInstallForcelist policy, and installation mode is not set in ExtensionSettings policy. 2) Extension is marked as 'force_installed' or 'normal_installed' in ExtensionSettings policy. We also ignore the extension ids if the update URL of the extension is a Chrome Web Store URL. This CL only adds the flag, the main logic is implemented in https://crrev.com/c/2510992. Bug: b/168097360 Change-Id: Id4e77669baf495b33b5887d6f4d68abc68b682f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485936 Commit-Queue: Swapnil Gupta <swapnilgupta@google.com> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Saurabh Nijhara <snijhara@google.com> Reviewed-by:
Oleg Davydov <burunduk@chromium.org> Reviewed-by:
Sergey Poromov <poromov@chromium.org> Cr-Commit-Position: refs/heads/master@{#835599}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/45a63bacb6df..6520135abe88 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 msramek@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: msramek@google.com Change-Id: I9adf1c0def851cf76f2d7774f7e62fcd082e48b8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583863Reviewed-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@{#835598}
-
Alice Wang authored
This CL moves two confirm sync data dialogs to signin.ui target. Bug: 1155131, 1155132 Change-Id: I26a78b7f44ca073ef7bb6192f69d359c9fae0c1d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577228 Commit-Queue: Alice Wang <aliceywang@chromium.org> Reviewed-by:
David Trainor <dtrainor@chromium.org> Cr-Commit-Position: refs/heads/master@{#835597}
-
Fredrik Söderqvist authored
This method shouldn't need to mutate the buffer. Clean up by adding some local variables for the document and the associated parser while here. Change-Id: Ic0f4541d557a07da833637906c01a1aa7dc37473 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2582220Reviewed-by:
Nate Chapin <japhet@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#835596}
-
Yuzu Saijo authored
This CL allows renderer to specify eviction reason, which is currently by default set to JavaScript execution. This CL also adds new reasons for eviction: kNetworkRequestRedirected, kNetworkRequestDatapipeDrained kNetworkRequestTimeout, kNetworkExceedsBufferLimit. Bug: 1137682 Change-Id: Iac59f98afd837a4876cb63a74c714a12d58c04c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567016 Commit-Queue: Yuzu Saijo <yuzus@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Alexander Timin <altimin@chromium.org> Reviewed-by:
Hajime Hoshi <hajimehoshi@chromium.org> Cr-Commit-Position: refs/heads/master@{#835595}
-
chromium-autoroll authored
Roll Chrome Win32 PGO profile from chrome-win32-master-1607450253-e5743bc31deb2e7a7a12ff155c587ac00d61c43d.profdata to chrome-win32-master-1607547301-1c0b0723d82aa4adb619c24bc9fd155c854d2040.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win32-chromium Please CC pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:win-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: If072d16c2df852c8e1534ce110e9c8c5b4382ac8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2582964Reviewed-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@{#835594}
-
Internal Frameworks Autoroller authored
TBR=bling-team@google.com Change-Id: I2f1f82efe5b4c83eca00f86a76b0cae7e1650177 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2582932Reviewed-by:
Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#835593}
-
Pavol Marko authored
Verify authentication passed as DMAuth or in query parameters. Remove related unused arguments. Bug: 1150887 Change-Id: I4500f05b890fbc751a360747b40a28edfa6d8498 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2563847 Commit-Queue: Pavol Marko <pmarko@chromium.org> Reviewed-by:
Michael Ershov <miersh@google.com> Cr-Commit-Position: refs/heads/master@{#835592}
-
Alice Wang authored
This CL cleans up the unused class SigninInvestigator. Bug: 1153022 Change-Id: I5bdf590191570048c54fecd3fb6d063906c076fd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2581479 Commit-Queue: Alice Wang <aliceywang@chromium.org> Reviewed-by:
Mihai Sardarescu <msarda@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#835591}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/dd9c4208af2e..81356f4bf38c If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-win-chromium Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Tbr: perfetto-bugs@google.com Change-Id: I3da86f86f080f027930c871266d7edcbc5e924f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583844Reviewed-by:
-
Alice Wang authored
This CL moves ProfileDataCache and its tests to signin.services target. Bug: 1153049 Change-Id: Ifb301649f8ad6dc4a496cbc93edac0b69f33ac6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2571301Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Commit-Queue: Alice Wang <aliceywang@chromium.org> Cr-Commit-Position: refs/heads/master@{#835589}
-
Friedrich Horschig authored
This CL removes the dialog warning to prevent accidental reuse. The dialog allows to crash Chrome if the filling sheet is used in an Incognito tab that is closed by tapping the Android notification (see issue 1154595). It's harder to fix that than to remove the dialog entirely which is an orthogonal goal (see issue 1153660). Since this crash fix needs merging, the warning string will keep being on two lines which prevents a new translation or a risky concatenation that might not work in all languages. Screenshot in the first bug. Bug: 1153660, 1154595 Change-Id: Iaa4aad18e8508087f10600ad14fc1b038b06d1c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577469 Commit-Queue: Friedrich [CET] <fhorschig@chromium.org> Reviewed-by:
Ioana Pandele <ioanap@chromium.org> Reviewed-by:
Caitlin Fischer <caitlinfischer@google.com> Cr-Commit-Position: refs/heads/master@{#835588}
-
Martin Šrámek authored
This reverts commit 2db43e77. Reason for revert: Failure on the linux-bfcache-rel bot. See https://ci.chromium.org/ui/p/chromium/builders/ci/linux-bfcache-rel/12034/overview Original change's description: > BackForwardCache: Add a flag parameter supported_features > > This CL adds a new flag parameter supported_features to BackForwardCache > feature. This parameter can specify the set of the features to be > allowed with back-forward cache. This enables us to enable the feature > remotely. > > Bug: 1155449 > Change-Id: Idb7eb55b114af688533ba2e069a9334714be725c > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2573850 > Reviewed-by: Kentaro Hara <haraken@chromium.org> > Reviewed-by: Alexander Timin <altimin@chromium.org> > Reviewed-by: Fergal Daly <fergal@chromium.org> > Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org> > Cr-Commit-Position: refs/heads/master@{#835571} TBR=hajimehoshi@chromium.org,haraken@chromium.org,altimin@chromium.org,fergal@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com Change-Id: Ie806efc5caecaa1b66c125e9e90c1a1edc0bdd5f No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1155449 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2582122Reviewed-by:
Martin Šrámek <msramek@chromium.org> Commit-Queue: Martin Šrámek <msramek@chromium.org> Cr-Commit-Position: refs/heads/master@{#835587}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1607558393-ecfec5cb12c3793b6b05707a914c348608cba34b.profdata to chrome-mac-master-1607579988-85272d8bbf93007898b77e84b51d31a40000a6a1.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-mac-chromium Please CC pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:mac-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I17dad9bda10bd9bb045570bc9c1d9d66aa178106 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2582839Reviewed-by:
-
Martin Šrámek authored
This reverts commit e16309d9. Reason for revert: This landed in the same build batch where the TwoClientEventSyncTest broke. Looking at the CL description, this seems related. See https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8861341071397738112/+/steps/sync_integration_tests_on__none__GPU_on_Mac_on_Mac-10.13.6/0/logs/Deterministic_failure:_TwoClientUserEventsSyncTest.SetPassphraseAndRecordEventAndThenSetupSync__status_FAILURE_/0 Original change's description: > [floc] Remove the EventTrigger field in the FlocIdComputed event > > Why: That field is never used & not useful for the server side analysis. > > This CL also removes a workaround that disables the initial floc > loggings when permission disallows > (in FlocIdProviderImpl::LogFlocComputedEvent). We had this workaround > because otherwise the logging would mess up with the user event > expectations in SingleClientUserEventsSyncTest, but that workaround is > not ideal. This CL fixes it by disabling kFlocIdComputedEventLogging for > the test suite, and adds a new test for the enabled case. The impact > of this fix is it will cause additional events to be logged. > > > Bug: 1148358 > Change-Id: I70cef531b89b434b5572b419acc8dd2412888498 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2572733 > Reviewed-by: Josh Karlin <jkarlin@chromium.org> > Reviewed-by: Marc Treib <treib@chromium.org> > Commit-Queue: Yao Xiao <yaoxia@chromium.org> > Cr-Commit-Position: refs/heads/master@{#835468} TBR=treib@chromium.org,jkarlin@chromium.org,yaoxia@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com Change-Id: I1095984a9a38063e0d722d7c78fb9f83538977eb No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1148358 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2582222Reviewed-by:
-
Javier Ernesto Flores Robles authored
This will cause the buttons to dim when touched instead of looking darker Bug: 1100887 Change-Id: I0ed01c9844e23623fc44f3cbb4002ac557bfe297 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583147 Auto-Submit: Javier Flores <javierrobles@chromium.org> Commit-Queue: David Jean <djean@chromium.org> Reviewed-by:
David Jean <djean@chromium.org> Cr-Commit-Position: refs/heads/master@{#835584}
-
chromium-autoroll authored
Roll Chrome Linux PGO profile from chrome-linux-master-1607558393-7b448dadc25433e8ca3294be917bb2299ab3dcfb.profdata to chrome-linux-master-1607579988-31aafc9e6ecd14c47d53bc6af437bfedef1daa8a.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-linux-chromium Please CC pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I9b58d950a0f77dbc2b56d3d227101e8c4597009a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583413Reviewed-by:
-
Eugene Zemtsov authored
NV12Scale has been recently added to libyuv, so there is no reason to use a self-written version. Change-Id: I6b207788e964c7ee21697eab9931fa2854031718 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580916Reviewed-by:
Thomas Guilbert <tguilbert@chromium.org> Reviewed-by:
Matthew Wolenetz <wolenetz@chromium.org> Commit-Queue: Eugene Zemtsov <eugene@chromium.org> Cr-Commit-Position: refs/heads/master@{#835582}
-
Xianzhu Wang authored
This reverts commit 7f72fc62. Reason for revert: Caused P0 crbug.com/1155271. Original change's description: > Use composited scrolling if resizer needs to be above descendants > > A resizer on an element containing composited stacked descendants > needs to be painted after the descendants. In pre-CompositeAfterPaint > this can only be achieved by using composited scrolling for the element > so that we'll composite the resizer even if the element is not > scrollable. > > In CompositeAfterPaint everything is good because we always use the > correct paint order. > > Bug: 1135676 > Change-Id: Ic69b830ae3d71cd9f6b8f55deca591b485b189a5 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523748 > Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> > Reviewed-by: Chris Harrelson <chrishtr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#825613} TBR=wangxianzhu@chromium.org,chrishtr@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1135676 Change-Id: Ie47558d1e9cbb1ed8f29e21286128899085be338 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583603Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#835581}
-
Clark DuVall authored
WebLayer relro sharing in the browser process has likely always been broken in WebView compatibility mode because the ClassLoader created does not have a class loader namespace, see here: https://cs.android.com/android/platform/superproject/+/master:frameworks/base/native/webview/loader/loader.cpp;l=129-132;drc=master Unfortunately, this is difficult to fix since sharing relro in WebLayer when it is loaded in the same process as WebView causes crashes. This will be investigated more in a follow up. Relro sharing was never implemented for the WebLayer GPU process, and this change adds support to do that. In addition, library loading is kicked off on a separate thread much earlier in startup, which allows it to finish before it is needed on the UI thread. Pinpoint runs: startup.mobile: https://pinpoint-dot-chromeperf.appspot.com/job/169ab7ef520000 -18.4% messageloop_start_time -3.4% navigation_commit_time -1.8% first_contentful_paint_time weblayer_startup: https://pinpoint-dot-chromeperf.appspot.com/job/17959d48d20000 -6.4% weblayer_startup_wall_time system_health.memory_mobile: https://pinpoint-dot-chromeperf.appspot.com/job/16d61b37520000 -10.0% (3.9MiB) all_processes private_dirty_size -29.8% (3.7Mib) gpu_process private_dirty_size Bug: 1146438 Change-Id: I52292f0472f18397b0a900307649e6f1b54bd5c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2581007 Commit-Queue: Clark DuVall <cduvall@chromium.org> Reviewed-by:
Richard Coles <torne@chromium.org> Cr-Commit-Position: refs/heads/master@{#835580}
-
Christopher Cameron authored
Serialization code for ImageBitmap goes through CanvasColorParams. This constrains unrelated canvas code, and isn't a good fit. This changes serialization to use SkImageInfo instead of CanvasColorParams. The serialization code still uses the CanvasColorSpace enums, though that should eventually be made more flexible. Bug: 1121448, 1150969 Change-Id: I33189ac40ae923e921473cfea41c2b6dcb9aa3cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569211 Commit-Queue: ccameron <ccameron@chromium.org> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#835579}
-
Joe Downing authored
This functionality has been requested by the CrOS Enterprise team. The goal is to allow users within a managed network to use CRD for remote support (potentially limiting the allowed users via the domain policy list) but prevent those users from setting up a remote access host. This CL adds a new policy which will cause the CRD remote access host to shut down if connections are disabled. This policy is read when the host starts up (meaning it should not come online if the policy disables the functionality) and is also triggered if the policy changes while the host is running. I decided not to update the native message host because I think it is OK if a user tries to set up CRD only to have the host shut itself down (if the policy is set on a managed network) as long as the error reason is noted in the client UI. My plan is to use the host error reason for that purpose and will update the client UI once this CL lands. Change-Id: I8ac8a3778971d5c79c5ed0f734efe1bfe43864cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580698 Commit-Queue: Joe Downing <joedow@chromium.org> Reviewed-by:
Jamie Walch <jamiewalch@chromium.org> Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Cr-Commit-Position: refs/heads/master@{#835578}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/a6fc821995dc..45a63bacb6df If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC meredithl@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: meredithl@google.com Change-Id: I136c417c0a9070077fd794540288d83f2000fd6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583782Reviewed-by:
-
Ramin Halavati authored
Ephemeral Guest profiles will have the same new tab page as the off-the- record Guest profiles in the first experiments. Please see go/ephemeral-guest-profiles for more context. Bug: 1134111 Change-Id: I5682db9576abb7575b09903a8c2633cdccdd5f87 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580784 Commit-Queue: Ramin Halavati <rhalavati@chromium.org> Reviewed-by:
Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#835576}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/32e1d74200bc..7f5478d8ceb7 2020-12-10 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools Chromium DEPS. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Ie72d6dd8e79d88b7cd632a5fbf0ca93f5bf76aa2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583746Reviewed-by:
-
Frédéric Wang authored
This change replaces network::IsUrlPotentiallyTrustworthy with network::IsOriginPotentiallyTrustworthy in the Insecure Input Tab Helper. The difference is that "potentially trustworthy origin" does not include "data:" and "about:" schemes [1]. [1] https://w3c.github.io/webappsec-secure-contexts/#potentially-trustworthy-url Bug: 1119740, 1153336 Change-Id: Ib817eee3a8460b1f99669b6dc77c92f0e7ed2743 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580067 Commit-Queue: Frédéric Wang <fwang@igalia.com> Reviewed-by:
Emily Stark <estark@chromium.org> Cr-Commit-Position: refs/heads/master@{#835574}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/dd9c4208af2e..81356f4bf38c If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-mac-chromium Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Tbr: perfetto-bugs@google.com Change-Id: Idb5302bfd5b40c6f47095f02d6c80b5325fea792 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2582517Reviewed-by:
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/af11a00f7849..22f80a60b17f 2020-12-10 skia-autoroll@skia-public.iam.gserviceaccount.com Roll ANGLE from 27e52ca05dc7 to 067a12f05951 (10 revisions) 2020-12-10 skia-autoroll@skia-public.iam.gserviceaccount.com Roll SwiftShader from 84b9bb6621c7 to d94a77b304f4 (9 revisions) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC jmbetancourt@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Cq-Do-Not-Cancel-Tryjobs: true Bug: None Tbr: jmbetancourt@google.com Change-Id: I72a65449e2e5d76af152a001fc5e159b5fc26fde Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2583744Reviewed-by:
-
Hajime Hoshi authored
This CL adds a new flag parameter supported_features to BackForwardCache feature. This parameter can specify the set of the features to be allowed with back-forward cache. This enables us to enable the feature remotely. Bug: 1155449 Change-Id: Idb7eb55b114af688533ba2e069a9334714be725c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2573850Reviewed-by:
Fergal Daly <fergal@chromium.org> Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org> Cr-Commit-Position: refs/heads/master@{#835571}
-
Leo Lai authored
we are migrating tpm status calls to TpmManagerClient. BUG=b:172748724 TEST=unit_tests. Change-Id: I8638acb35dc21e2a1103d377fd9c4b328383a25e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2579934Reviewed-by:
-
Kyle Williams authored
Adds the boilerplate code for integrating with the meet devices mojom binder service for chromium. BUG=b:174846892 TEST='autoninja -C ~/chromium/src/out_${SDK_BOARD}/Release chrome chrome_sandbox nacl_helper' Change-Id: Ib0171f58e272128a4d5469f2c0bffd082d2bb30d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575758 Commit-Queue: Kyle Williams <kdgwill@chromium.org> Reviewed-by:Dominick Ng <dominickn@chromium.org> Reviewed-by:
Alexander Alekseev <alemate@chromium.org> Cr-Commit-Position: refs/heads/master@{#835569}
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1607536746-29bce53663c3c2f323cb6f75c47555236b300f05.profdata to chrome-win64-master-1607547301-0ddf36656043436fe87b3dfd771fe4fe3bc2c5ce.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win64-chromium Please CC pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: Iaeea76dd6f39aaeb41facb9ec61c83e908821d41 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2582952Reviewed-by:
-
Luciano Pacheco authored
In the SWA Data Source register all the resources from the file_manager extension so we can use the same relative paths from the main.html used in the extension. With this change we can stop inlining the CSS via flattenhtml GRD option. Bug: 1113981 Change-Id: I3eb00b8ae3b0dc79273e1cdea00b5abc1426812a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580670 Commit-Queue: Luciano Pacheco <lucmult@chromium.org> Auto-Submit: Luciano Pacheco <lucmult@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#835567}
-
David Dorwin authored
Also replace initialization of deprecated log_service_channel member with new members log_sink_channel and log_sink_socket. Bug: 1136681, fuchsia:63529 Change-Id: I0bf1e785c17829eb19b193c7544cdd8d4e51542c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2581020 Commit-Queue: David Dorwin <ddorwin@chromium.org> Auto-Submit: David Dorwin <ddorwin@chromium.org> Reviewed-by:
Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#835566}
-
Glen Robertson authored
Also update outdated doc comment. Change-Id: I1c5161c11f3f5727b191f2fea55563c4596167cb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580964Reviewed-by:
Varun Khaneja <vakh@chromium.org> Reviewed-by:
Alan Cutter <alancutter@chromium.org> Reviewed-by:
Ryan Sleevi <rsleevi@chromium.org> Reviewed-by:
Trent Apted <tapted@chromium.org> Commit-Queue: Glen Robertson <glenrob@chromium.org> Cr-Commit-Position: refs/heads/master@{#835565}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/83498ed6d228..d94a77b304f4 2020-12-10 natsu@google.com Set prefersDedicatedAllocation for AHB If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Please CC swiftshader-team+autoroll@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: I63954a6a6059761e7a9bdb0d7e013824de8f8af7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2582956Reviewed-by:
-
Frédéric Wang authored
This CL removes host names and "localhost6" and "localhost6.localdomain6" from the list of known IPv6-only localhost. This means they will be resolved using the native DNS resolver rather than Chrome's internal one and that they won't be treated as "potentially trustworthy" origins [1] [2]. This aligns with the behavior of WebKit and Firefox, is expected to have low backward compatibility risk and one can configure things to preserve existing support [3] [4]. [1] https://tools.ietf.org/html/draft-west-let-localhost-be-localhost-06 [2] https://w3c.github.io/webappsec-secure-contexts/#is-origin-trustworthy [3] https://chromestatus.com/feature/5698580851458048 [4] https://groups.google.com/a/chromium.org/g/blink-dev/c/bmdcI_q2yWQ Bug: 1153337 Change-Id: I344e4aebe4caebc30c70f8dcda1ce87ee0937bda Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570568Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Commit-Queue: Frédéric Wang <fwang@igalia.com> Cr-Commit-Position: refs/heads/master@{#835563}
-
Frank Liberato authored
This CL adds an off-by-default option to use media::DecoderStream as WebRTC's external decoder, rather than a media::VideoDecoder directly. This allows: - Chrome's decoder selection algorithm can choose between hw and software video decoders based on resolution, and any other criteria that we use for non-rtc playback. - Chrome can fall back and forward between HW and SW decoders. - All of Chrome's SW decoder stack is available, rather than only those decoders which also have HW implementations (AV1). Design doc: https://docs.google.com/document/d/1UIkqHucVttNjiMk9wAaoFUJcZ2PQSDZmLleXQutMVZQ/edit?usp=sharing Change-Id: I59ade0b4e5a482f28bbb52ffb522bf6c50eaad2a Bug: 1132903,1136495, 1157227 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2495515Reviewed-by:Henrik Boström <hbos@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Frank Liberato <liberato@chromium.org> Cr-Commit-Position: refs/heads/master@{#835562}
-
