- 17 Jan, 2020 40 commits
-
-
Hui Wang authored
Bug: None Signed-off-by:
Hui Wang <wanghui210@huawei.com> Change-Id: Ie8395d6e72a7193f000afe03c15218d7c7bb36b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2006446Reviewed-by:
Bo <boliu@chromium.org> Commit-Queue: Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#732886}
-
Vadym Doroshenko authored
Addressing one TODO and removed several already addressed TODOs. Change-Id: I8b4e1f96fb67e47d97c5eced35992c237e6043fe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007690Reviewed-by:
Matthias Körber <koerber@google.com> Commit-Queue: Vadym Doroshenko <dvadym@chromium.org> Auto-Submit: Vadym Doroshenko <dvadym@chromium.org> Cr-Commit-Position: refs/heads/master@{#732885}
-
Nico Weber authored
`gn format` recently changed its formatting behavior for deps, source, and a few other elements when they are assigned (with =) single-element lists to be consistent with the formatting of updates (with +=) with single-element. Now that we've rolled in a GN binary with the change, reformat all files so that people don't get presubmit warnings due to this. This CL was uploaded by me. Bug: 1041419 Change-Id: If28253fb33fc1e42c6ae6f0d83f0c1c529bf7f45 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007650Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#732884}
-
Charlie Hu authored
This CL adds initialization of document policy on browser side. A DocumentPolicy instance is now available in RenderFrameHostImpl. Bug: 993790 Change-Id: I990a39d219179dd9254060a7488eab4f991e44ad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1988156 Commit-Queue: Charlie Hu <chenleihu@google.com> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Reviewed-by:
Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#732883}
-
Fritz Koenig authored
When using low latency MSAA resolve was gated by swap chains. ChromeOS does not use swap chains. Move the resolve to before checking for swap chains. Test: https://codepen.io/miguelao/pen/WKZaqd Bug: 1025747 Change-Id: I344c8576c16277348950836a3fc28a58f787a256 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003073 Auto-Submit: Fritz Koenig <frkoenig@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Fritz Koenig <frkoenig@chromium.org> Cr-Commit-Position: refs/heads/master@{#732882}
-
Nohemi Fernandez authored
Bug: 1005509 Change-Id: I7eab2ad6ad082daadff0ab38aafe9ea57d655ccb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007450 Commit-Queue: Nohemi Fernandez <fernandex@chromium.org> Reviewed-by:
Stepan Khapugin <stkhapugin@chromium.org> Cr-Commit-Position: refs/heads/master@{#732881}
-
Stepan Khapugin authored
This just makes _browserViewWrangler a property and updates calls. This will allow for cleaner CLs moving code to SceneController. Bug: none Change-Id: Ic3118c54ac0799a0089a0e5a159d68d672b899c8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003854Reviewed-by:
Mark Cogan <marq@chromium.org> Commit-Queue: Stepan Khapugin <stkhapugin@chromium.org> Cr-Commit-Position: refs/heads/master@{#732880}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/d8628858c150..9293af72309e git log d8628858c150..9293af72309e --date=short --first-parent --format='%ad %ae %s' 2020-01-17 tvanderlippe@chromium.org Migrate sdk/ to ESM internally Created with: gclient setdep -r src/third_party/devtools-frontend/src@9293af72309e 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: Ifc5dacd874ff6cf492874b38f293e2cfe6fb8d8a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007908Reviewed-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@{#732879}
-
Scott Violet authored
As a last file doesn't make sense for WebLayer this is structuring the code in such a way that the last file related code is not in the base class. This does the following: renames BaseSessionService* to CommandStorageManager* Next step is to move the functions related to a 'last file' out of CommandStorageManagerinto CommandStorageManagerWithBackup. Specifically the functions: MoveCurrentSessionToLastSession, DeleteLastSession, ScheduleGetLastSessionCommands. CommandStorageManagerWithBackup will subclass CommandStorageManager. SessionBackend will be similarly split such that functions related to last session are moved into SessionBackendWithBackup, which will extend SessionBackend. I'm not dead set on the 'WithBackup' suffix. It's not really a backup, so much as the last session. I considered the prefix 'MultiFile' but that's a bit too generic and obscure. I'm certainly open to other suggestions. BUG=112512 TEST=none Change-Id: I33d2c9be43bbaea4336fa32bdb3fe750d39f543a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2005809Reviewed-by:
Evan Stade <estade@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#732878}
-
Leonard Grey authored
These fail deterministically See: https://test-results.appspot.com/data/layout_results/Mac10_10_Tests/50711/webkit_layout_tests/layout-test-results/results.html TBR=iopopesc@microsoft.com Bug: 1035582 Change-Id: Ie5d7937feb8edea4452894960ab5a7d76af3f4af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007868 Commit-Queue: Leonard Grey <lgrey@chromium.org> Reviewed-by:
Leonard Grey <lgrey@chromium.org> Cr-Commit-Position: refs/heads/master@{#732877}
-
Mike West authored
Leaning on Google Security's work defining Strict CSP (https://csp.withgoogle.com/docs/strict-csp.html), this patch considers a policy to be "reasonably secure" if it: 1. Asserts `object-src 'none'`. 2. Asserts `base-uri 'none'` or `base-uri 'self'`. 3. Avoids URL-based matching, in favor of hashes and nonces. It adds metrics for each of these independently for both enforced and report-only policies, as well as for the "reasonably secure" metric composing all three. Bug: 1040876 Change-Id: I4054e5abccd0966a30dcec01a3f8c04f6e3575a0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002587 Commit-Queue: Mike West <mkwst@chromium.org> Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#732876}
-
Nazerke authored
This CL updates StoreKitCoordinator to use the preferred init for coordinators, which provides a Browser instance, also updates the unit tests. Bug: 1029346 Change-Id: Ifa9d080eb4a0c1768e549d01c6282cfe7207a0c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007188 Commit-Queue: Nazerke Kalidolda <nazerke@google.com> Reviewed-by:
Mark Cogan <marq@chromium.org> Cr-Commit-Position: refs/heads/master@{#732875}
-
Christopher Cameron authored
The concept of "the color space of the display" falls apart on several platforms, because display (or OS) can be configured to handle multiple color spaces. Rather than sending a single color space, send a set of color spaces to use in various situations (sRGB-only content, SDR WCG content, and HDR content). Use this gfx::DisplayColorSpaces structure in display::Display, instead of using gfx::ColorSpace and sdr_white_point. Also communicate this via mojo, which had not been done in the past. For now, only use the "HDR transparent" color space. The next patch use this structure in ui::Compositor, viz::Display, and viz::SurfaceAggregator. This structure is added to gfx because it is imported from these several locations. Bug: 1037954, 1038770, 1038494, 958166 Change-Id: I677e3f5c4d01deeb95f76b6463541eec2163b48b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2006068Reviewed-by:
Dominick Ng <dominickn@chromium.org> Reviewed-by:
Miguel Casas <mcasas@chromium.org> Commit-Queue: ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#732874}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/1918d6d30029..486a2cf15526 Created with: gclient setdep -r src-internal@486a2cf15526 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC jbudorick@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: jbudorick@google.com Change-Id: I1200d259eaa6c4e94ac9d3e20cd5aa7acbf0d309 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007305Reviewed-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@{#732873}
-
Olga Gerchikov authored
This change reduces number of TIME_UPDATED events passed to main thread. When syncing time from compositor to main thread, only the last time value produced on the compositor thread is relevant. Passing all other values is unnecessary overhead. Bug: 1013654 Change-Id: Id950d48f2b36c6afb2d74cf26605c490767121b4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001260 Commit-Queue: Olga Gerchikov <gerchiko@microsoft.com> Reviewed-by:
Robert Flack <flackr@chromium.org> Cr-Commit-Position: refs/heads/master@{#732872}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/c9f42ad909c0..524417f3f7d0 git log c9f42ad909c0..524417f3f7d0 --date=short --first-parent --format='%ad %ae %s' 2020-01-17 titovartem@webrtc.org Move method to right place in the PC API Created with: gclient setdep -r src/third_party/webrtc@524417f3f7d0 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: Ied0683d49569f7ba35559b38e6d9bc7120251b04 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007848Reviewed-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@{#732871}
-
Leonard Grey authored
This reverts commit 561bf1af. Reason for revert: Strongly suspect this is causing failures on the debug builders: [29058:775:0117/070736.663833:ERROR:CONSOLE(49)] "Mocha test failed: PersonalizationOptionsTests_AllBuilds signinAllowedToggle Error: Uncaught TypeError: Cannot read property 'PRIVACY_CHROME_SIGN_IN' of undefined (chrome://settings/privacy_page/personalization_options.js:102) r732804 was reverted earlier for the same reasons, but there are still failures coming from the settings code, albeit less Original change's description: > More Settings Page Interaction UMA > > Move the settings enum and the call to uma to a separate browser proxy. > > Add UMA to all site settings subpage interactions and new toggles moved to the main settings card > > Bug: 1032584 > Change-Id: Icadd71d4511fa1f604f2d3acbda92c0e84700173 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1967651 > Commit-Queue: Sean Harrison <harrisonsean@chromium.org> > Reviewed-by: Dan Beam <dbeam@chromium.org> > Cr-Commit-Position: refs/heads/master@{#732785} TBR=dbeam@chromium.org,harrisonsean@chromium.org Change-Id: Id4ee78d89487ecf7e6d1935088d02b29de89c7c8 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1032584 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007829Reviewed-by:
Leonard Grey <lgrey@chromium.org> Commit-Queue: Leonard Grey <lgrey@chromium.org> Cr-Commit-Position: refs/heads/master@{#732870}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/ba0d9547be17..c33c078292af git log ba0d9547be17..c33c078292af --date=short --first-parent --format='%ad %ae %s' 2020-01-17 chrome-bot@chromium.org Update config settings by config-updater. 2020-01-16 chrome-bot@chromium.org Update config settings by config-updater. Created with: gclient setdep -r src/third_party/chromite@c33c078292af 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: I3357d7fc30c68f16a5561a8f9979abd2b3e51019 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007849Reviewed-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@{#732869}
-
Rouslan Solomakhin authored
Card class (debit, prepaid, credit, unknown) where used only for "supportedTypes" field of Payment Request, which has been removed. Bug: 981907 Change-Id: I4348f6d2e09975a3e5e4ec9aa5a0407916269a89 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2005091Reviewed-by:
Tim Schumann <tschumann@chromium.org> Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org> Cr-Commit-Position: refs/heads/master@{#732868}
-
Mike Reed authored
See https://skia-review.googlesource.com/c/skia/+/264997 Change-Id: Ibd6ce3367d8df772ef2ea8d83b1779428f82ab0b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007509Reviewed-by:
Florin Malita <fmalita@chromium.org> Commit-Queue: Mike Reed <reed@google.com> Cr-Commit-Position: refs/heads/master@{#732867}
-
sandromaggi authored
Before this change, the WebContents were read from the model. After this change they are passed directly, coming from the Client. Bug: b/144681042 Change-Id: I0588d89c7a00d5baa8cd4d96797d881395dd2fb3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002617 Commit-Queue: Sandro Maggi <sandromaggi@google.com> Reviewed-by:
Mathias Carlen <mcarlen@chromium.org> Cr-Commit-Position: refs/heads/master@{#732866}
-
Mikhail Khokhlov authored
This will allow running TBMv3 metrics on Windows. Bug: 990304 Change-Id: Id53fe61c931b36b386e6feea461447657ca24f58 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2005008 Commit-Queue: Mikhail Khokhlov <khokhlov@google.com> Reviewed-by:
Deepanjan Roy <dproy@chromium.org> Cr-Commit-Position: refs/heads/master@{#732865}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/9da16439..b7cd486d 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: Ifac5aa9f23b67382f51ba47f869178d1cc8dbe1e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007610Reviewed-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@{#732864}
-
Michael van Ouwerkerk authored
Bug: 1042707 Change-Id: I6243c8dc6fd151738aac5c23e90968ab53f7e6cb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002627Reviewed-by:
Richard Knoll <knollr@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Commit-Queue: Michael van Ouwerkerk <mvanouwerkerk@chromium.org> Cr-Commit-Position: refs/heads/master@{#732863}
-
arthursonzogni authored
The goal is to merge all the ContentSecurityPolicy structure defined in both content:: and network::mojom. This patch substitute the content:: ones by the network::mojom ones for IPCs. See UnifyCSP: https://docs.google.com/document/d/1v5mJnXJ5dSVXE_rgvJnNM9bzH0ni0YzdhPQ7GLqyhao Bug: 1021462 Change-Id: I43256dc304628ed715ba3b8206450cde0b2755aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2000640 Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Camille Lamy <clamy@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#732862}
-
Anna Malova authored
Bug: 989667 Change-Id: Ie1b407aaea377736f87f07560ad04b83f9fba901 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1942268 Commit-Queue: Anna Malova <amalova@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Reviewed-by:
Richard Coles <torne@chromium.org> Cr-Commit-Position: refs/heads/master@{#732861}
-
Nico Weber authored
`gn format` recently changed its formatting behavior for deps, source, and a few other elements when they are assigned (with =) single-element lists to be consistent with the formatting of updates (with +=) with single-element. Now that we've rolled in a GN binary with the change, reformat all files so that people don't get presubmit warnings due to this. This CL was uploaded by me. Bug: 1041419 Change-Id: I4dc096337fe543a8ff2d027d95323f521989000f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007768Reviewed-by:
Hans Wennborg <hans@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#732860}
-
Rouslan Solomakhin authored
Before this patch, a service worker on Android that declared support for "interledger", "basic-card", and one URL-based payment method would receive a "canmakepayment" event from a Payment Request for "interledger". This patch skips sending "canmakepayment" to the service worker on Android if the Payment Request is only for standardized payment methods. After this patch, "canmakepayment" events are sent only for URL-based payment methods (that have been explicitly verified). Bug: 1040994 Change-Id: I3d908e6b6e628b3ca7290adfed394a7be6041f6a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994305Reviewed-by:
Sahel Sharify <sahel@chromium.org> Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org> Cr-Commit-Position: refs/heads/master@{#732859}
-
Stepan Khapugin authored
Moves AppNavigation protocol implementation to SceneController. Bug: none Change-Id: I41732781203fae618ce5b5651a1f3be47576a816 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002521Reviewed-by:
Mark Cogan <marq@chromium.org> Commit-Queue: Stepan Khapugin <stkhapugin@chromium.org> Cr-Commit-Position: refs/heads/master@{#732858}
-
Owen Min authored
The callback will be invoked when the notification is closed. It also returns whether the notification is closed by user action or not. Bug: 1006899 Change-Id: I339fc43e32c1ab101957867a9d871b479fa9d060 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003339Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Commit-Queue: Owen Min <zmin@chromium.org> Cr-Commit-Position: refs/heads/master@{#732857}
-
dalyk authored
This is a reland of 778c2799 Tests that rely on configuring secure mode now either use the managed pref store or temporarily mark the environment as "not managed" to prevent the mode from being downgraded to off. Original change's description: > Have DNS prober diagnose secure DNS config issues. > > When the current DNS config is in secure mode, the corresponding DNS > runner will also use secure mode as well as the preconfigured DoH > servers. There is no change to the behavior when the current config > is in automatic mode. > > A new probe error code, DNS_PROBE_FINISHED_BAD_SECURE_CONFIG, is > returned in secure mode in cases where DNS_PROBE_FINISHED_BAD_CONFIG > would have previously been returned. > > Bug: 1037931 > Change-Id: I253963e86b309790e38959cda2c2e014ddceb9e4 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1981014 > Commit-Queue: Katharine Daly <dalyk@google.com> > Reviewed-by: Robert Sesek <rsesek@chromium.org> > Reviewed-by: Matt Menke <mmenke@chromium.org> > Cr-Commit-Position: refs/heads/master@{#730553} Bug: 1037931 Change-Id: I910080c0bc3cf759d04b060bd955fd86f29db156 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1998918Reviewed-by:
Matt Menke <mmenke@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Commit-Queue: Katharine Daly <dalyk@google.com> Cr-Commit-Position: refs/heads/master@{#732856}
-
Marc Treib authored
In some situations, PerUserTopicSubscriptionManager should (or should not!) invalidate an existing access token. This CL adds tests for this behavior, which also required some changes to the identity test code, to expose which access tokens were invalidated. Bug: 1020117 Change-Id: Iaef29cdcf3072064b476432ee3fc6bdcb8040388 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003136Reviewed-by:
David Roger <droger@chromium.org> Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Commit-Queue: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#732855}
-
Alexander Hendrich authored
This CL allows all login screen extension to specify a custom content security policy in their manifest. Bug: none Change-Id: I043e21c72c00326ffecb1b6b318249379a0aece5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2000917Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Commit-Queue: Alexander Hendrich <hendrich@chromium.org> Cr-Commit-Position: refs/heads/master@{#732854}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/d58b643f10f5..9b1ec5f072a5 git log d58b643f10f5..9b1ec5f072a5 --date=short --first-parent --format='%ad %ae %s' 2020-01-17 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/angle2 a7b91502cd7f..41f6150edb16 (20 commits) 2020-01-17 fmalita@chromium.org [skottie] Add custom props rendering GM Created with: gclient setdep -r src/third_party/skia@9b1ec5f072a5 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 mtklein@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: mtklein@google.com Change-Id: I20673c95f4ae9555fe8f7740a47ead5265624fe5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007594Reviewed-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@{#732853}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/fc8279d66c81..c9f42ad909c0 git log fc8279d66c81..c9f42ad909c0 --date=short --first-parent --format='%ad %ae %s' 2020-01-17 srte@webrtc.org Simplifies transport overhead mechanism in Scenario test framework. 2020-01-17 saza@webrtc.org Remove unused AEC delay offset API 2020-01-17 hbos@webrtc.org ResourceAdaptationModule HasInputVideo+DegradationPreference setters. 2020-01-17 peah@webrtc.org Reland "Replace the ExperimentalAgc config with the new config format" Created with: gclient setdep -r src/third_party/webrtc@c9f42ad909c0 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: I5157cea9673dd5979c29787204e5678963040bc5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007591Reviewed-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@{#732852}
-
Chromium WPT Sync authored
Using wpt-import in Chromium 8b49e5d8. With Chromium commits locally applied on WPT: 62f8d5f0 "Enable Scroll To Text by default" 363313c0 "Sort the registrations returned by getRegistrations() by registration ID." Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md NOAUTOREVERT=true TBR=robertma No-Export: true Change-Id: Ifff3aaace72b7afbaa5430e3d6495ef52f911f55 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007609Reviewed-by:
WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#732851}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/d4405431bad0..c6d670ac06ee git log d4405431bad0..c6d670ac06ee --date=short --first-parent --format='%ad %ae %s' 2020-01-17 khokhlov@google.com [Telemetry] Set a clock snapshot on Android Created with: gclient setdep -r src/third_party/catapult@c6d670ac06ee If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/catapult-autoroll Please CC rmhasan@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_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: chromium:990304 Tbr: rmhasan@google.com Change-Id: I590f9426897f503ff42cb28223df035304c6d926 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007593Reviewed-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@{#732850}
-
Jit Yao Yap authored
Currently, |login_screen_ui::UiHandler| only closes the login screen UI window when the extension is uninstalled, and not when it is unloaded. When an extension is updated, the old instance is unloaded and not uninstalled. This means when an update occurs when the old instance has a window open, this window will not be closed, and the new instance will not be able to open another window. This CL updates |UiHandler| to also close the window when the extension is unloaded. Bug: 957573 Change-Id: If586fa5cc83fca20d971e85080389d013b854e66 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002610 Commit-Queue: Jit Yao Yap <jityao@google.com> Reviewed-by:
Alexander Hendrich <hendrich@chromium.org> Cr-Commit-Position: refs/heads/master@{#732849}
-
Yifan Luo authored
This CL separates 'require-trusted-types-for' from 'trusted-typs' Content Security Policy directive, which currently has only one injection sink 'script'. https://w3c.github.io/webappsec-trusted-types/dist/spec/#require-trusted-types-for-csp-directive Bug: 1030257 Change-Id: I1c241c5b6be318aa195323178cf974df138d5788 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993351 Commit-Queue: Yifan Luo <lyf@google.com> Reviewed-by:
Mike West <mkwst@chromium.org> Reviewed-by:
Daniel Vogelheim <vogelheim@chromium.org> Cr-Commit-Position: refs/heads/master@{#732848}
-
Koji Ishii authored
This CHECK was added to investigate the dirty layout found at crbug.com/965976 <crrev.com/c/1626349>. This patch turns this to NOTREACHED to mitigate users. Bug: 1038735 Change-Id: Id544874fd5ec3c0805bd28fb615b8378351fd276 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2006832Reviewed-by:
Yoshifumi Inoue <yosin@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#732847}
-