- 21 Dec, 2020 40 commits
-
-
Aya ElAttar authored
Updated the strings of the clipboard notifications shown on block according to the latest update from UI review. Bug: 1158743 Change-Id: I21389225ed1fd83e9edfc753afc1a071a101d3e1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2595303 Commit-Queue: Aya Elsayed <ayaelattar@chromium.org> Reviewed-by:
Pavol Marko <pmarko@chromium.org> Cr-Commit-Position: refs/heads/master@{#838621}
-
Jason Lin authored
Bug: b/167491603 Change-Id: I8682f941ba8a3cd282991f62c73dffedf91e3030 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2598094 Commit-Queue: Jason Lin <lxj@google.com> Commit-Queue: Joel Hockey <joelhockey@chromium.org> Auto-Submit: Jason Lin <lxj@google.com> Reviewed-by:
Joel Hockey <joelhockey@chromium.org> Cr-Commit-Position: refs/heads/master@{#838620}
-
Hiroshige Hayashizaki authored
Bug: 1022182 Change-Id: I98d3897fdc99d42a0b6bb09461bfb228068ddd02 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2586206 Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Auto-Submit: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#838619}
-
Ghazale Hosseinabadi authored
When starting a service worker fails, we need better error reporting to //extensions. In case of script evaluation error, which is a user error, this CL enables //extensions to propagate such an error to the ErrorConsole to give developers a hint about the issue. Bug: 1151017 Change-Id: Iccf8ecd2562d8d443968f06ecef00080b41d2ded Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576587 Commit-Queue: Matt Falkenhagen <falken@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Reviewed-by:
François Doray <fdoray@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#838618}
-
Internal Frameworks Autoroller authored
TBR=bling-team@google.com Change-Id: I25d824ccaa12c96fc59e2e4b3ac5e7732f6354b2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2596077Reviewed-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@{#838617}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/c42f56dc3662..68649aff0ca8 2020-12-21 jegarc@microsoft.com This CL fixes the color for the css property names in high contrast 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:1159577 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Ib6959244dd43a8f92869ad2cc98394393e4a68fd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2599484Reviewed-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@{#838616}
-
Shakti Sahu authored
Bug: 1159557 Change-Id: I0c2e5d759b17620dcb1333002e80943da253e8c4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2595889 Commit-Queue: Shakti Sahu <shaktisahu@chromium.org> Reviewed-by:
Xing Liu <xingliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#838615}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/f4ad8c537982..88883c4ca259 2020-12-21 skia-autoroll@skia-public.iam.gserviceaccount.com Roll Dawn from 64c5d601f89b to 5d4fd88a7403 (1 revision) 2020-12-21 skia-autoroll@skia-public.iam.gserviceaccount.com Roll ANGLE from de703db564d6 to ed9213bca064 (7 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 bungeman@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: bungeman@google.com Change-Id: I40944984057b06c94fea0a420f8c02ad243972ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2599481Reviewed-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@{#838614}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1608508387-4c99c0c6e0807bf68be573ad8b3c8353e1fc0e76.profdata to chrome-mac-master-1608529993-82d6d40e289e60063d3bd5c2eebe97dc9bb53838.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: I7b9e879c5feed8fd4e01a04784017927555354c8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2599483Reviewed-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@{#838613}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/bec27c2c2a8e..07d993711f33 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 talp@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: talp@google.com Change-Id: I2111fe4dc30a594e7d9e78fcfdb2cb7f215b79ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2598024Reviewed-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@{#838612}
-
Tal Pressman authored
Bug: 1160616 Change-Id: I054dd1c1d8e0bf77f99b979ad12929f6f0d9af9c Tbr: hta@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2596478Reviewed-by:
Tal Pressman <talp@google.com> Commit-Queue: Tal Pressman <talp@google.com> Cr-Commit-Position: refs/heads/master@{#838611}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/2622d88609d1..c42f56dc3662 2020-12-21 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: I984bb74a9aa22ac185ec70925472e86a4620d0a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2599479Reviewed-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@{#838610}
-
chromium-autoroll authored
Roll Chrome Win32 PGO profile from chrome-win32-master-1608432581-ff55f7d7458123a29eec3ce7592821edeb11f86c.profdata to chrome-win32-master-1608508387-56780dae3832c65bafd36e4cfe96756ad3b86eef.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: Ibf13938de9afb2331feeba0a613cbe511229ac2e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2596555 Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Reviewed-by:
chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#838609}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/73bf5d7d..b96d7e2a 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: I3e8a2d8046df9afbfa49fd7fd433e862efa79336 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2599010Reviewed-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@{#838608}
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1608480487-d09244758c3f22256fe9146780e06c2aad82d633.profdata to chrome-win64-master-1608508387-093abbef3f1d2d94b454a0cdd869bb44780245e6.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: I7bbe09c58473c5f1e77bbe26eb3ac4047cef1b49 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2596646Reviewed-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@{#838607}
-
Yunke Zhou authored
Issue is due to there's a small time difference between StatsReportingController::SetWithService and pref is properly set. We should only propagate the value from service until it is correctly set. Bug: 1154947 Change-Id: I977249dd25e1402246b383401c9deef4ea8ebc56 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587065Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Commit-Queue: Yunke Zhou <yunkez@google.com> Cr-Commit-Position: refs/heads/master@{#838606}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/2d44549a1f3a..f4ad8c537982 2020-12-21 skia-autoroll@skia-public.iam.gserviceaccount.com Roll Chromium from a51698b2 to fc46ab79 (188 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 bungeman@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: bungeman@google.com Change-Id: Iee72021fb7ad340758d86e1cddfb61e300ed0795 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2599459Reviewed-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@{#838605}
-
Anupam Snigdha authored
According to the explainer[1] we should be firing the geometrychange event to the main frame and not to the focused frame. We changed this on android, but forgot to make this change on Windows. This patch fixes the bug on Windows. 1. https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/VirtualKeyboardAPI/explainer.md#api-availability-in-iframe-context Bug: 1160388 Change-Id: I5c7a577592e815dba36034bf020e05bab0d62d63 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2598725Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Anupam Snigdha <snianu@microsoft.com> Cr-Commit-Position: refs/heads/master@{#838604}
-
Makoto Shimazu authored
Event timeouts set the idle timeout to zero so that the service worker is tereminated as soon as possible. However, when the DevTools is attached in that case, OnRequestTermination() rejects to terminate the service worker and that results in repeated calls of RequestTermination. This CL fixes it by setting the idle delay to the default value in that situation. Bug: 1152793 Change-Id: Ifef7f16a7c308f24766ea8593d2fb4f412becf40 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2592235 Commit-Queue: Makoto Shimazu <shimazu@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#838603}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/d63a6aaf6fb4..bec27c2c2a8e 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 talp@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: talp@google.com Change-Id: I254780c4c884a47c52c71bf6ddee03425c277113 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2599436Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Reviewed-by:
Tal Pressman <talp@google.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#838602}
-
Makoto Shimazu authored
Previously ResponseCallback was not discarded even if the waitUntil() hits the timeout. This ends up with keeping a request stored in `ServiceWorkerVersion::inflight_requests_` until respondWith() is settled even if the waitUntil() hits the timeout. This CL changes the behavior by closing the Mojo endpoint for ResponseCallback on timeout. In addition, another bug was revealed by the fix where `is_endpoint_ready_` was not updated correctly. This caused an issue of dispatching a fetch event while it's still in stopping state. This CL updates the flag in OnStopping() which is called synchronously from EmbeddedWorkerInstance::Stop(). Bug: 1156091, 1156081, 1156626, 1152793 Change-Id: Iaa227b0dbfa7cd6046e441a1c73c18e15757172a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2586645Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Reviewed-by:
Asami Doi <asamidoi@chromium.org> Commit-Queue: Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#838601}
-
Giovanni Ortuño Urquidi authored
Adds a WebUIConfig and a UntrustedWebUIController for Terminal. Bug: 1080384 Change-Id: If43a0b9f778ad6bedf35f2e484627c8fa41ac321 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2592246 Commit-Queue: Giovanni Ortuño Urquidi <ortuno@chromium.org> Reviewed-by:
Joel Hockey <joelhockey@chromium.org> Reviewed-by:
calamity <calamity@chromium.org> Cr-Commit-Position: refs/heads/master@{#838600}
-
Nidhi Jaju authored
Following https://chromium-review.googlesource.com/c/chromium/src/+/2570755, this CL updates the interface object WPT expectations to remove Streams API interface classes that have already been exposed. Bug: 1093862 Change-Id: Ibdce3585a8b34b3aeef40e3fae610af733ebdc79 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2595553Reviewed-by:
Adam Rice <ricea@chromium.org> Commit-Queue: Nidhi Jaju <nidhijaju@google.com> Cr-Commit-Position: refs/heads/master@{#838599}
-
Yutaka Hirano authored
It seems in some cases network::URLLoader gets a request with a streaming upload body, but the ChunkedDataPipeGetter for the body is invalid. Reject such requests gracefully. Bug: 1156550 Change-Id: Ic8f21cc00044efd839802279126095a681da811c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2584640Reviewed-by:
Jesse Doherty <jwd@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#838598}
-
Tal Pressman authored
This reverts commit 2ecb8d17. Reason for revert: Seems to cause TSan failures in interactive_ui_tests (Autofill*Test). Sample failure: ci.chromium.org/ui/p/chromium/builders/ci/Linux%20TSan%20Tests/61802/test-results?expected=false&exonerated=true&flaky=true The affected tests pass when enabling the trybot manually on this CL. (See linux_chromium_tsan_rel_ng results below.) Original change's description: > [base] Fix trace events and blocking types when blocked on modal dialogs > > Sheriff notes: This is expected to artificially reduce IOJank* metrics. > > Modal dialogs launched via GetAppOutputInternal in launch_posix.cc > are guaranteed to block and thus should use WILL_BLOCK semantics > (as opposed to MAY_BLOCK like it did). > > However, Process::WaitForExit can't use WILL_BLOCK semantics because > of an existing workaround for TestLauncher to not use > ScopedBlockingCallWithBaseSyncPrimitives when waiting on processes or > TestLauncher ends up creating or TestLauncher ends up flooding > the pool to 256 workers regardless of --test-launcher-jobs > (it posts each test as a task right off the bat and expects the > pool to cap the parallelism...). > > The best solution to get proper tracing and thread restrictions > right is thus to add custom trace events and keep assertions > that waiting is allowed when launching the process. > > Each platform was doing something slightly different here, this > CL brings all platforms inline with annotations that are visible > in tracing but ignored by IOJank metrics. > > Example broken trace showing up in IOJank slow reports on Linux: > https://goto.google.com/btbzu (SS: https://snipboard.io/7sDO1r.jpg) > > R=fdoray@chromium.org > > Bug: 1064645, 1144161, 899897 > Change-Id: Id087f91df8c2201ca10db5438456c638f9b791e9 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2233299 > Commit-Queue: Gabriel Charette <gab@chromium.org> > Reviewed-by: Wez <wez@chromium.org> > Reviewed-by: François Doray <fdoray@chromium.org> > Reviewed-by: Joe Downing <joedow@chromium.org> > Cr-Commit-Position: refs/heads/master@{#837874} TBR=wez@chromium.org,gab@chromium.org,fdoray@chromium.org,joedow@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1064645 Bug: 1144161 Bug: 899897 Change-Id: If5117fec4f71342259e479341ad3e3da6425e7b0 Tbr: gab@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2597521 Commit-Queue: Tal Pressman <talp@google.com> Reviewed-by:
Tal Pressman <talp@google.com> Cr-Commit-Position: refs/heads/master@{#838597}
-
Tal Pressman authored
This reverts commit 1af362f4. Reason for revert: The rollback did not fix bots, so I am relanding the CL. Original change's description: > Revert "Wait until safe time to create web document" > > This reverts commit 593304b4. > > Reason for revert: Suspect it caused failures in content_browsertests > Accessibility tests. > > Original change's description: > > Wait until safe time to create web document > > > > TBR=kinuko@chromium.org > > > > Bug: 1156939 > > Change-Id: I23443fc4461dc61223fef249bac109a8b7e8183e > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2586233 > > Reviewed-by: Aaron Leventhal <aleventhal@chromium.org> > > Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org> > > Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#838244} > > TBR=dmazzoni@chromium.org,aleventhal@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com > > # Not skipping CQ checks because original CL landed > 1 day ago. > > Bug: 1156939 > Change-Id: Iac0282f6e1a24119a67dacf81c5e1c33ed303d33 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2596292 > Reviewed-by: Tal Pressman <talp@google.com> > Commit-Queue: Tal Pressman <talp@google.com> > Cr-Commit-Position: refs/heads/master@{#838585} TBR=dmazzoni@chromium.org,aleventhal@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com,talp@google.com # Not skipping CQ checks because this is a reland. Bug: 1156939 Change-Id: Ib7571aa00acc5c1202abdbebfb40e2180aba36e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2598303Reviewed-by:
Tal Pressman <talp@google.com> Commit-Queue: Tal Pressman <talp@google.com> Cr-Commit-Position: refs/heads/master@{#838596}
-
John Palmer authored
BUG=b/175820571 BUG=b/175820584 Change-Id: Ia143818e70d325c03c9e0b8b8c04de5de41d4de0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2595561Reviewed-by:
Darren Shen <shend@chromium.org> Reviewed-by:
My Nguyen <myy@chromium.org> Commit-Queue: John Palmer <jopalmer@chromium.org> Cr-Commit-Position: refs/heads/master@{#838595}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/e9f7d2179637..2622d88609d1 2020-12-21 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools 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: I8622b47e8bf9f35c98c19ab9cfaa4ee55f84b43f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2599456Reviewed-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@{#838594}
-
Bao-Duy Tran authored
Bug: 1159297 Change-Id: I7f940cc3403c52e1cb2fe3eaf1f5f99d4284bd74 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2592851 Commit-Queue: Bao-Duy Tran <tranbaoduy@chromium.org> Reviewed-by:
My Nguyen <myy@chromium.org> Reviewed-by:
Darren Shen <shend@chromium.org> Reviewed-by:
Keith Lee <keithlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#838593}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=kariah@chromium.org Change-Id: I57ae09e0f083b7b6dd3617a2a6f971f1e04677ae Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2597649Reviewed-by:
Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#838592}
-
Kinuko Yasuda authored
The change https://crrev.com/c/2577150 missed to set this value. This also adds a unittest to check this (which fails without the fix). R=rbpotter@chromium.org, thakis@chromium.org Bug: 862175 Change-Id: I6548804749de242d6ccf1ec4b4c20547dfba2d9c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2597249Reviewed-by:
Nico Weber <thakis@chromium.org> Commit-Queue: Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#838591}
-
Tal Pressman authored
This reverts commit ef97c140. Reason for revert: Suspect this is causing various AssistantBrowserTest tests to fail. Sample failure: ci.chromium.org/ui/p/chrome/builders/ci/linux-chromeos-chrome/10788/overview Manually adding the failing bot (linux-chromeos-chrome) shows that the tests pass. Original change's description: > Simplify Libassistant startup (and fix crashes) > > Currently starting Libassistant happens in 2 steps: > 1. (On background thread) ServiceController::Start() creates the > |AssistantManager|. > 2. (On main thread) ServiceControllerProxy::FinishAssistantStart() > sets some extra fields on |AssistantManager| and calls > AssistantManager::Start(). > > This causes a race condition if Libassistant is immediately stopped, > as that happens on the background thread and can collide with step 2 > above. > > To prevent this from happening, this CL collapses both starting steps in > a single step that runs on the background thread. We do this by > registering a callback which is called by the background thread in step > 1 above. > > This callback is temporary but necessary as some parts of the > initialization code still use objects that have not been migrated to the > Libassistant mojom service yet. > > Bug: 1157177, b/171748795, 1128032 > Test: chromeos_unittests "Assistant*:ServiceController*" > Change-Id: Ifab9705839ad5d3e5c9f2b7f7fba4c336b9f7c9d > Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2594090 > Commit-Queue: Jeroen Dhollander <jeroendh@chromium.org> > Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org> > Cr-Commit-Position: refs/heads/master@{#838277} TBR=xiaohuic@chromium.org,wutao@chromium.org,meilinw@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com,jeroendh@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1157177 Bug: b/171748795 Bug: 1128032 Change-Id: I252bd0f14d662eadfd9fb61b8972e34a460fb040 Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Tbr: jeroendh@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2597250 Commit-Queue: Tal Pressman <talp@google.com> Reviewed-by:
Tal Pressman <talp@google.com> Cr-Commit-Position: refs/heads/master@{#838590}
-
Bao-Duy Tran authored
This field is never used anywhere, other than asserting that it must always carry value "ime" (!). All parsing and validation is unnecessary. The field's existence is unnecessary and may hinder the flexibility for future work. It'd better be gone in the spirit of YAGNI "you aren't gonna need it". Note that the specs for these manifests have never been formally specified or published anywhere. Also, this cleanup is fully backward compat even for 3P, because the field is never really used. Bug: 1134465 Change-Id: Ied6e1ad30a9ab6f08091a7d31a9c3f3124989a8f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2592072 Commit-Queue: Bao-Duy Tran <tranbaoduy@chromium.org> Reviewed-by:
Darren Shen <shend@chromium.org> Reviewed-by:
Alice Boxhall <aboxhall@chromium.org> Reviewed-by:
Keith Lee <keithlee@chromium.org> Reviewed-by:
Ben Wells <benwells@chromium.org> Cr-Commit-Position: refs/heads/master@{#838589}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1608480487-c8d6a020311436cdd2559a40dfb31e24c333522a.profdata to chrome-mac-master-1608508387-4c99c0c6e0807bf68be573ad8b3c8353e1fc0e76.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: Iaee829f920eea9f0d55b7e3d8edc3395c58b3528 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2596553Reviewed-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@{#838588}
-
Joel Hockey authored
If a path is already shared, we can avoid the extra seneschal dbus call. This code was originally written before GuestOsSharePath::IsPathShared() was available. Change-Id: Ia92dcad3e3202f40606a0e8b7620e0ea76847c58 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2596472 Auto-Submit: Joel Hockey <joelhockey@chromium.org> Commit-Queue: Nicholas Verne <nverne@chromium.org> Commit-Queue: Jason Lin <lxj@google.com> Reviewed-by:
Nicholas Verne <nverne@chromium.org> Reviewed-by:
Jason Lin <lxj@google.com> Cr-Commit-Position: refs/heads/master@{#838587}
-
Tal Pressman authored
Change-Id: I10cd12f9b6356254acaa66639dfaec8b8a0465b2 Bug: 1160594 Tbr: dom-dev@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2596946Reviewed-by:
Tal Pressman <talp@google.com> Commit-Queue: Tal Pressman <talp@google.com> Cr-Commit-Position: refs/heads/master@{#838586}
-
Tal Pressman authored
This reverts commit 593304b4. Reason for revert: Suspect it caused failures in content_browsertests Accessibility tests. Original change's description: > Wait until safe time to create web document > > TBR=kinuko@chromium.org > > Bug: 1156939 > Change-Id: I23443fc4461dc61223fef249bac109a8b7e8183e > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2586233 > Reviewed-by: Aaron Leventhal <aleventhal@chromium.org> > Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org> > Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> > Cr-Commit-Position: refs/heads/master@{#838244} TBR=dmazzoni@chromium.org,aleventhal@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1156939 Change-Id: Iac0282f6e1a24119a67dacf81c5e1c33ed303d33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2596292Reviewed-by:
Tal Pressman <talp@google.com> Commit-Queue: Tal Pressman <talp@google.com> Cr-Commit-Position: refs/heads/master@{#838585}
-
Yuichiro Hanada authored
WindowEventDispatcher can defer the processing of mouse/touch events until a non-mouse/touch events comes or it's explicitly released. If a target window of the deferred window destroys another window in their event handler, the destruction is also deferred. It can cause use-after-free if the following non-mouse/touch event's target is the window being destroyed because searching of the target window happens before the release of the deferred mouse events. Bug: 1099985 Test: aura_unittests Change-Id: Ia386bb99edd1374d1d39038ff44b3bfc73c26fa5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576983Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Yuichiro Hanada <yhanada@chromium.org> Cr-Commit-Position: refs/heads/master@{#838584}
-
Thanh Nguyen authored
Since LSS has been sandboxed and clients are using new sandboxed LSS, we need to clean up the code. This CL cleans the unused sync code. Design doc: go/lss-sandboxing Implementation plan: go/lss-sandboxing-impl Bug: 1137560 Change-Id: If8347e621b0169ff15062deb7a8953c1c76bf6f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2594747Reviewed-by:
Jia Meng <jiameng@chromium.org> Reviewed-by:
Sam McNally <sammc@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Commit-Queue: Thanh Nguyen <thanhdng@chromium.org> Cr-Commit-Position: refs/heads/master@{#838583}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/02a278d97bec..d63a6aaf6fb4 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 talp@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: talp@google.com Change-Id: Id8a3ff01d823e825bd5131e9f64909dbd39202d7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2599004Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Reviewed-by:
Tal Pressman <talp@google.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#838582}
-