- 18 Jan, 2021 40 commits
-
-
Mike Reed authored
Bug: skia:11188 Change-Id: I15ebdc464c12537d7c7a489b5b5ff6cb6b9a38a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633747 Commit-Queue: Mike Reed <reed@google.com> Reviewed-by:
Florin Malita <fmalita@chromium.org> Reviewed-by:
vmpstr <vmpstr@chromium.org> Reviewed-by:
Robert Flack <flackr@chromium.org> Cr-Commit-Position: refs/heads/master@{#844587}
-
Hans Wennborg authored
This rebuilds the current clang version, bootstrapped with the newer GCC version (see second bug) and libstdc++ version. Also add libstdc++ to isolates which use llvm-symbolizer. Otherwise llvm-symbolizer runs with libstdc++ from the host system rather than the clang package; this happened to work before but not anymore. Bug: 1166977, 1164952 Cq-Include-Trybots: chromium/try:chromeos-amd64-generic-cfi-thin-lto-rel Cq-Include-Trybots: chromium/try:dawn-win10-x86-deps-rel Cq-Include-Trybots: chromium/try:linux-chromeos-dbg Cq-Include-Trybots: chromium/try:linux_angle_deqp_rel_ng Cq-Include-Trybots: chromium/try:linux_chromium_cfi_rel_ng Cq-Include-Trybots: chromium/try:linux_chromium_chromeos_asan_rel_ng Cq-Include-Trybots: chromium/try:linux_chromium_chromeos_msan_rel_ng Cq-Include-Trybots: chromium/try:linux_chromium_compile_dbg_32_ng Cq-Include-Trybots: chromium/try:linux_chromium_msan_rel_ng Cq-Include-Trybots: chromium/try:mac-arm64-rel,mac_chromium_asan_rel_ng Cq-Include-Trybots: chromium/try:win-angle-deqp-rel-64 Cq-Include-Trybots: chromium/try:win-asan,win7-rel,win-angle-deqp-rel-32 Cq-Include-Trybots: chrome/try:iphone-device,ipad-device Cq-Include-Trybots: chrome/try:linux-chromeos-chrome Cq-Include-Trybots: chrome/try:win-chrome,win64-chrome,mac-chrome Change-Id: I739f94aaa3bdc4a0a1c858d0fbf08d1449d4c0ce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633051 Commit-Queue: Hans Wennborg <hans@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#844586}
-
Daniel Nicoara authored
This allows overriding the user agent if an override is set. NOTE: This does require the caller to override the user agent in order for it to happen. If the caller doesn't override, the default user agent is used. Bug: b:175857659 Test: cast_shell_browsertests Change-Id: I713f01076baabe108b17e1d4934f7dc4259b7139 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633705Reviewed-by:
Sean Topping <seantopping@chromium.org> Commit-Queue: Daniel Nicoara <dnicoara@chromium.org> Cr-Commit-Position: refs/heads/master@{#844585}
-
Christoph Schwering authored
Bug: 1007974 Change-Id: Ia50bbdef505695f29b9c924dfa4c62ffbd156be2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2630806 Commit-Queue: Christoph Schwering <schwering@google.com> Reviewed-by:
Matthias Körber <koerber@google.com> Cr-Commit-Position: refs/heads/master@{#844584}
-
Guillaume Jenkins authored
Adds support for changing the value of the BrowserSignin policy to 0 while the browser is running. Adds a BrowserAgent that monitors the kSigninAllowed pref, which is controlled by the BrowserSignin policy. When kSigninAllowed changes to false, the BrowserAgent dispatches a command to SceneController to dismiss any in-progress sign-in UI and sign the user out. Bug: 1155745 Change-Id: Ifac4c785f73e098e94be8c3df35040ec60b489c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2616278Reviewed-by:
Mark Cogan <marq@chromium.org> Reviewed-by:
David Roger <droger@chromium.org> Reviewed-by:
Nohemi Fernandez <fernandex@chromium.org> Commit-Queue: Guillaume Jenkins <gujen@google.com> Cr-Commit-Position: refs/heads/master@{#844583}
-
Stephen McGruer authored
This reverts commit af9cb62a, as the hopeful fix for the WPT manifest hang problem in Python 3 has now been landed upstream and rolled into Blink's copy of WPT tooling. Bug: 1161274 Change-Id: I09add44c20931feba69321af70ceba4ac6f31d67 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2630866Reviewed-by:
Luke Z <lpz@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#844582}
-
Tommy Martino authored
Per discussion on team chat Change-Id: Ibb2747aadabce3b12204a02d4e4d8f39be0af5d3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2635182 Commit-Queue: Tommy Martino <tmartino@chromium.org> Commit-Queue: sebsg <sebsg@chromium.org> Auto-Submit: Tommy Martino <tmartino@chromium.org> Reviewed-by:
sebsg <sebsg@chromium.org> Cr-Commit-Position: refs/heads/master@{#844581}
-
Wez authored
Previously WebEngine bundled only the en-US versions of several sets of string resources, and included some resources PAKs which did not appear to be used. This also required WebEngine to use the ResourceBundle::InitSharedInstanceWithPakPath(), which is intended only for use in testing. WebEngine now uses ResourceBundle::InitSharedInstanceWithLocale(), and bundles the locale resources: - A Fuchsia implementation of LoadCommonResources() is provided, which mirrors the LoadChromeResources() implementation but loads from a "common_resources.pak" file in the bundle, rather than "chrome.pak". - //ui's DIR_LOCALES path is overridden in WebEngine to redirect to ${DIR_ASSETS}/locales/ - Locale-specific resources are placed in separate PAK files under ${DIR_ASSETS}/locales/. Additional some unused files are removed from the bundle: - Two unused sets of locale-specific resources. - The resource PAKs are moved from |data_deps| to |deps|, to prevent the associated "info" files from being implicitly pulled into the FAR. This will be changed back once the "web_engine" target is migrated off of the cr_package_fuchsia() template. Bug: 1092804, 1164990 Change-Id: I94bc1185e9005ba987b86a2ff39b921daf158858 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626443 Commit-Queue: Wez <wez@chromium.org> Reviewed-by:David Dorwin <ddorwin@chromium.org> Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Cr-Commit-Position: refs/heads/master@{#844580}
-
Peter Kotwicz authored
This CL makes android_lint_test use the android_nocompile_test_suite() template introduced in https://chromium-review.googlesource.com/c/chromium/src/+/2538313 This CL also modifies the android_nocompile_test_suite() template to: - Support pydeps - To rerun the tests when a "expected_compile_output" value is updated. BUG=1132014 Change-Id: Iee0480feb082a0afed4dbafa2c35d2b5d05851c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2620838Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Reviewed-by:
Dirk Pranke <dpranke@google.com> Reviewed-by:
Peter Wen <wnwen@chromium.org> Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org> Cr-Commit-Position: refs/heads/master@{#844579}
-
Gabriel Charette authored
R=etiennep@chromium.org, olivierli@chromium.org Bug: 1167247 Change-Id: I034b0b6e095b3b10c5cf4318c11e94f83424aba6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633365Reviewed-by:
Oliver Li <olivierli@google.com> Reviewed-by:
Etienne Pierre-Doray <etiennep@chromium.org> Reviewed-by:
Etienne Bergeron <etienneb@chromium.org> Commit-Queue: Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#844578}
-
Jarryd authored
* Extend expiry of PercentDiskAvailable * Extend expiry of AvailableDiskSpace * Add team list owner for each of the abovementioned histograms Bug: 1160830 Change-Id: I85db775d96d07b6a1370994ba496282dff6634ad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2600044Reviewed-by:
Jesse Doherty <jwd@chromium.org> Commit-Queue: Jarryd Goodman <jarrydg@chromium.org> Cr-Commit-Position: refs/heads/master@{#844577}
-
Luke Zielinski authored
TBR=smcgruer Bug: 1167318 Change-Id: I123f572db757ebadb275f82f0229eb08bec37478 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2635794Reviewed-by:
-
Roman Aleksandrov authored
Fixed: 1165222,1160906 Change-Id: Ib1de78e8b170c58add51cbbcf1dc7f28e3eaadbe Bug: 1165222 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632596 Commit-Queue: Roman Aleksandrov <raleksandrov@google.com> Reviewed-by:
Caitlin Fischer <caitlinfischer@google.com> Cr-Commit-Position: refs/heads/master@{#844575}
-
Victor-Gabriel Savu authored
Delay expiry of PolicyUpdatePeriod.Device and PolicyUpdatePeriod.User. Bug: chromium:1165053 Change-Id: I8b2d8cb4d009bbb7d0fce0c667f0d3eabf21e2ec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2635151Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/f572da65b858..9c423651c0fb 2021-01-18 alexrudenko@chromium.org UI to emulate the color-gamut media feature 2021-01-18 janscheffler@chromium.org [JSDOC2TS]: Migrate coverage 2021-01-18 jacktfranklin@chromium.org Lint inline CSS inside .ts components 2021-01-18 andoli@chromium.org [module.json extensions] resources views If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: chromium:1134103,chromium:1158760,chromium:1166108 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Ifebf9eda101d72d0a73a25818900f09852906431 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636342Reviewed-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@{#844573}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/68f15c734d5c..297e1ae19685 2021-01-18 angle-autoroll@skia-public.iam.gserviceaccount.com Roll SwiftShader from aedd133cd85f to 149733cead63 (2 revisions) 2021-01-18 angle-autoroll@skia-public.iam.gserviceaccount.com Roll vulkan-deps from 7b69f3d087b8 to 2bb77d70cc64 (4 revisions) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC cnorthrop@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_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;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: cnorthrop@google.com Change-Id: Ic9e06e84963842a98f194bd87cb9579c1757b43d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636176Reviewed-by:
-
Patrick Monette authored
At first, this class will own the performance_monitor::SystemMonitor. In the future, it will also own the ProcessMonitor when it no longer is a leaky singleton. Bug: 1166820 Change-Id: Ie47865c3b6e9afcae91be14c22342f3b27685426 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2630228Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Reviewed-by:
Sébastien Marchand <sebmarchand@chromium.org> Commit-Queue: Patrick Monette <pmonette@chromium.org> Cr-Commit-Position: refs/heads/master@{#844571}
-
Keishi Hattori authored
If GigaCage isn't enabled, this DCHECK gets triggered PartitionRoot()->PartitionRefCountPointer()->DCheckGetSlotOffsetsZero()->PartitionGetSlotOffset()->DCheckIfManagedByPartitionAllocNormalBuckets() We should check IsPartitionAllocGigaCageEnabled before calling IsManagedByPartitionAllocNormalBuckets. Also removed, PartitionRefCountPointerNoDCheck() as it would no longer be needed. Bug: 1073933 Change-Id: Ida270d718f0299837d1b506966d46512a8c60f24 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631980 Commit-Queue: Keishi Hattori <keishi@chromium.org> Reviewed-by:
Bartek Nowierski <bartekn@chromium.org> Cr-Commit-Position: refs/heads/master@{#844570}
-
Michael Ershov authored
* Replace `EXPECT_CALL(..., Func(_))` into `EXPECT_CALL(..., Func)` where checking arguments is not useful. (in most cases it expects a pointer to client object). * Expect specific arguments for function calls where it's not a pointer (just a couple of places with empty vector). Bug: 1150887 Test: CloudPolicyClientTest* Change-Id: I23dd01ad2d868e312d9bdc4135ff7a3b5e7249fa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2550919Reviewed-by:
Pavol Marko <pmarko@chromium.org> Commit-Queue: Michael Ershov <miersh@google.com> Cr-Commit-Position: refs/heads/master@{#844569}
-
Omar Morsi authored
In this CL, the 412 pending approval HTTP status error code is handled by the certificate provisioning client by trying the request after a different delay depending on the request that received this error. Bug: 1167055 Change-Id: Id92ea8f3bc47337144b3e81af2aa7c99a8aa465a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632687Reviewed-by:
Michael Ershov <miersh@google.com> Reviewed-by:
-
Caitlin Fischer authored
The server-side configs show that these studies have ended. Bug: 1126640 Change-Id: I4df424208d21cbfe4da72c51693185b6bc9910ce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631933Reviewed-by:
Tommy Martino <tmartino@chromium.org> Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Cr-Commit-Position: refs/heads/master@{#844567}
-
Miyoung Shin authored
This CL keep a swap promise as active when DidNotSwap is called with the commit fail to fix the problem that WebViewClient#onPageCommitVisible callback is not invoked or callbacks arrive at once. This problem was introduced since the CL[1] converted FrameMsg_VisualStateRequest to mojo because the CL missed the migration from the original code[2] which was being ported. [1] https://chromium-review.googlesource.com/c/chromium/src/+/2342532 [2] https://chromium.googlesource.com/chromium/src/+/c75c53f04b0207e654fd2f7f05e6b785988ea30e/content/renderer/frame_swap_message_queue.cc#124 Bug: 1148808 Change-Id: I935bee95332e775fd13fea15fedc856d34b37649 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636094Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Commit-Queue: Miyoung Shin <myid.shin@igalia.com> Cr-Commit-Position: refs/heads/master@{#844566}
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1610959165-ca87807bfba7d6db298cc69229704c835aeb25f8.profdata to chrome-win64-master-1610970273-10063fdcfa50f030104140b77891927983b7acbd.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: I53ea8f8a0e1ad61a4f44464c05d4c9bc7a4350a4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636255Reviewed-by:
-
Ella Ge authored
Pass the Supplier<ModalDialogManager> directly when creating CustomTabLocationBar, so that no need to get it from ChromeActivity. Bug: 1155353 Change-Id: Ibdea28fdd85cbda48cf6c9233afee00f862cdd86 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633685Reviewed-by:
Peter Conn <peconn@chromium.org> Reviewed-by:
Michael Thiessen <mthiesse@chromium.org> Commit-Queue: Ella Ge <eirage@chromium.org> Cr-Commit-Position: refs/heads/master@{#844564}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/5c20f1ec9ca9..4b316994ad01 2021-01-18 dawn-autoroll@skia-public.iam.gserviceaccount.com Roll Tint from c068cfc1397a to 4a110c2726e9 (1 revision) Also rolling transitive DEPS: https://dawn.googlesource.com/tint from c068cfc1397a to 4a110c2726e9 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/dawn-chromium-autoroll Please CC sarahmashay@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel Bug: None Tbr: sarahmashay@google.com Change-Id: I02d04afd2670999e81f1a8e6265d1d865d64ab04 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636337Reviewed-by:
-
chromium-autoroll authored
Roll Chrome Win32 PGO profile from chrome-win32-master-1610959165-8386a0e84f434425b7043e7053c588f46a3ee84d.profdata to chrome-win32-master-1610970273-d0f0048b36f7949e3d42c84fb209656aa5017f8c.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: I69fe2399215ad8d7487d258f257e0d33005688aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636293Reviewed-by:
-
Ella Ge authored
Cast the activity to a ModalDialogManagerHolder to get the ModalDialogManager. Bug: 1155804 Change-Id: Ieae4f796f3e7b93b670ff6e5b8e2a120f2da1c8e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633363Reviewed-by:
-
Colin Blundell authored
This CL changes the subresource filter to handle detected ad violations entirely within the component, rather than delegating to the embedder. This change concretely means that WebLayer now obtains this behavior for free. To test proper integration in WebLayer, this CL also adds browsertests of the expected behavior in //weblayer. These browsertests are straight ports of the tests in //chrome's ads_intervention_manager_browsertest.cc with one exception: those tests verify that ChromeSubresourceFilterClient::ShowNotification() is called on page activations via checking a histogram bucket that is updated in that method. //weblayer does not currently update this histogram (although I will shortly be componentizing that code), so I removed these checks from the //weblayer tests as other //weblayer tests verify directly that the infobar is shown on a page activation. I disabled these browsertests on Windows due to https://crbug.com/1152429. Bug: 1116095 Change-Id: Ieba4ac17988a711c658cdb2b731bdb952b669f4b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2612890 Commit-Queue: Colin Blundell <blundell@chromium.org> Reviewed-by:
Charlie Harrison <csharrison@chromium.org> Cr-Commit-Position: refs/heads/master@{#844560}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/a36b28c1..e02dfe6c Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I8929beb2a0d319bd5922c6acfb8cd1be8dcb173e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2635718Reviewed-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@{#844559}
-
Owen Min authored
Rename the policy to WindowOcclusionEnabled. The old policy is kept for backward compatibility. Bug: 1163293 Change-Id: I6ff1ebf56e6bb5ec02a449773e407e18c914aea9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2611675Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Commit-Queue: Owen Min <zmin@chromium.org> Cr-Commit-Position: refs/heads/master@{#844558}
-
chromium-internal-autoroll authored
Release_Notes: http://go/help_app-x20/relnotes/Main/help_app_nightly_202101180600_RC00.html https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/help_app/app/+/69VjTA0ZKwsJNTOyvk6Q68sahYC23kY9GOAyQSnd2wEC If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/help-app-chromium-autoroll Please CC help-app@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 Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: help-app@grotations.appspotmail.com Change-Id: If193403e5501af2d723d3a53acb2a984113700ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636253Reviewed-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@{#844557}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/149733cead63..765e4f6f0ef4 2021-01-18 swiftshader.regress@gmail.com Regres: Update test lists @ 149733ce 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: Ic4b4fbf9af3971cf847b6ca7db89d739a89c3f88 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636235Reviewed-by:
-
Ehimare Okoyomon authored
Change dialog result reporting system to have its own observers in order to prevent having to add ModalDialogManagerObserver workarounds. For example, when a secondary os-level prompt is created after the user accepts a site-level prompt. This way, we only trigger an update directly after the permission changes. Bug: 1158288 Change-Id: I496ceb8f35495e61dd4f161256e56cf40c172ea9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632756 Commit-Queue: Ehimare Okoyomon <eokoyomon@chromium.org> Reviewed-by:
Christian Dullweber <dullweber@chromium.org> Reviewed-by:
Balazs Engedy <engedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#844555}
-
Ossama Mahmoud authored
Migrate ArcToSScreen to multistep behavior. Get rid of display: none; and display: block; Bug: 1156667 Change-Id: I4c2fc425edd4883c5edfceb0a5a9f67a6227de7b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2603744 Commit-Queue: Ossama Mahmoud <osamafathy@google.com> Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#844554}
-
Nico Weber authored
Looks like response file support in ld64 might be less crashy in this release, so we can try turning that back on after this roll. (It's currently enabled for static libraries but not for shared libraries or executables. We should first disable it for static libraries to get a self-consistent state, and then try enabling it for everything.) Apparently `otool` now (sometimes?) calls `otool-classic`, so add that to xcode_binaries.yaml and to content_shell_crash_test data. Bug: 1147968 Change-Id: I90f45942e6f7d735b5fb3be242a517f002f2e072 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633748 Commit-Queue: Nico Weber <thakis@chromium.org> Reviewed-by:
Mark Mentovai <mark@chromium.org> Auto-Submit: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#844553}
-
chromium-internal-autoroll authored
Release_Notes: http://go/media_app-x20/relnotes/Main/media_app_202101180600_RC00.html https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/media_app/app/+/ASfyiPo0gQ5e7I8KW1f86nFK6CdK4HjdLqg4cLkv3VEC If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/media-app-chromium-autoroll Please CC media-app@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 Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: b/138543581,b/175532928,b/176035799,b/177381366,b/177472560,b/177604649,b/177784709 Tbr: media-app@grotations.appspotmail.com Change-Id: Ia5ed3f3a862fc0c59659b04630f8b36a15d1cfd0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636177Reviewed-by:
-
Caitlin Fischer authored
Bug: 1126640 Change-Id: Icaa62b40bd6d8041cde6e2bca8c72c1367e8cfcc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627884Reviewed-by:
Per Kjellander <perkj@chromium.org> Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Cr-Commit-Position: refs/heads/master@{#844551}
-
Sigurdur Asgeirsson authored
Bug: 1143281 Change-Id: Ibc54e560a2a2a5f38c6ef48c7352c40c1b82109c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636273 Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org> Commit-Queue: Patrick Monette <pmonette@chromium.org> Reviewed-by:
Patrick Monette <pmonette@chromium.org> Cr-Commit-Position: refs/heads/master@{#844550}
-
behdad authored
The interval of last frame in sliding window is used to calculate the total expected frames in window. Test are also updated to reflect this change in calculation of percent dropped frames. Bug: 1167213 Change-Id: I5dd7e608d35b33af90046867d70bc652cced0366 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633922Reviewed-by:
Jonathan Ross <jonross@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Behdad Bakhshinategh <behdadb@chromium.org> Cr-Commit-Position: refs/heads/master@{#844549}
-
Mustaq Ahmed authored
This CL adds fields to postMessage data structures that convey the sender Window's intention to delegate a capability to the receiver Window. The change is behind two runtime flags: one flag ("CapabilityDelegation") enables the parsing of a new postMessage option for delegation, while the other flag ("CapabilityDelegationPaymentRequest") enables transmission of payment request delegation information to the receiver Window. Bug: 1130558 Change-Id: Ifad482bc9629ea69b9bd802d5f0f7df7c24645f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568627 Commit-Queue: Mustaq Ahmed <mustaq@chromium.org> Reviewed-by:Daniel Cheng <dcheng@chromium.org> Reviewed-by:
-
