- 10 Aug, 2020 40 commits
-
-
Ella Ge authored
This CL adds the TWA quality enforcement for http error 5xx and for page unavailable offline. The offline one is mostly same as 404 one, but failed when navigation finish with errorCode -106 (internet disconnected) Also, changes to use different error string that use for the toast and the message send to TWA client app. For the toast we use the localized string since it's showing in the UI. For the message to TWA client app, since it's used in a crash message, we do not localize it. Bug: 1109609 Change-Id: Ic314eeb6fdfacf6e066a6e8dbb5e72334f021e63 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2336996 Commit-Queue: Ella Ge <eirage@chromium.org> Reviewed-by:
Peter Conn <peconn@chromium.org> Cr-Commit-Position: refs/heads/master@{#796395}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/d44592935782..32d36b08379e 2020-08-10 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: Ifd3c3d341b075c3358b27095895b4eff638cd805 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346704Reviewed-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@{#796394}
-
Gauthier Ambard authored
This is a reland of ee4eb865 The original CL was reverted because some tests were broken when the flag was enabled. CL fixing the tests: https://crrev.com/c/2330052 Original change's description: > [iOS] Add fieldtrial config for IOSRequestDesktopByDefault > > Bug: None > Change-Id: Iea882e82e5573edaf917d8f3d976d876e2120de9 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317789 > Commit-Queue: Gauthier Ambard <gambard@chromium.org> > Reviewed-by: Mark Pearson <mpearson@chromium.org> > Cr-Commit-Position: refs/heads/master@{#792621} Bug: None Change-Id: I0ce43d62cf33bc52321b2584a548308fce4227db Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2329325 Commit-Queue: Gauthier Ambard <gambard@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Cr-Commit-Position: refs/heads/master@{#796393}
-
Andy Paicu authored
Bug: 1114675 Change-Id: I10ff8b750702a7644e13c450f493106093ff993f TBR: jhawkins@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346346 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Reviewed-by:
Andy Paicu <andypaicu@chromium.org> Cr-Commit-Position: refs/heads/master@{#796392}
-
Charlie Hu authored
This CL removes dead function |blink::PolicyValue::Combine|. Change-Id: I7f2e95129efc58c73d845a3662ee8e52c78a253d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2342643 Commit-Queue: Ian Clelland <iclelland@chromium.org> Reviewed-by:
Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#796391}
-
Rakesh Soma authored
2) Consider all characters as being valid for cloud directory serial mapping. Bug: 1114454 Change-Id: I9cef10c11b07f21295a6fda4ca46fdd723f04153 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2344814 Commit-Queue: Yusuf Sengul <yusufsn@google.com> Reviewed-by:
Yusuf Sengul <yusufsn@google.com> Cr-Commit-Position: refs/heads/master@{#796390}
-
sauski authored
To determine whether records should be cleared on shutdown a reference to the HostContentsSettingMap is retained for use in a TaskRunner. This causes a race between the service shutdown in the UI thread, and the audit database clearing session only records. This CL changes behavior such that the content settings at the time of shutdown are copied from the HostContentSettingsMap for local use in the TaskRunner. Bug: 1113376 Change-Id: I4c259a69dbc1eff9f1e85b48f05da886e5f63957 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339662 Commit-Queue: Theodore Olsauskas-Warren <sauski@google.com> Reviewed-by:
Martin Šrámek <msramek@chromium.org> Cr-Commit-Position: refs/heads/master@{#796389}
-
Carlos Caballero authored
Explicitly wait for the browser to close instead of flushing the run-loop. Bug: 852697 Change-Id: I788367506187b215fb6cc1a7a6f284db94609382 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1541244 Commit-Queue: Carlos Caballero <carlscab@google.com> Reviewed-by:
Peter Boström <pbos@chromium.org> Reviewed-by:
Leonard Grey <lgrey@chromium.org> Cr-Commit-Position: refs/heads/master@{#796388}
-
Ben Mason authored
This reverts commit 6e002e1f. Reason for revert: Official build failure crbug.com/1114609 Original change's description: > build_vars.txt: Changed to build_vars.json > > And moved helper function into gn_helpers.py > > It was only ever in .properties format so that it > could be easily parsed by bash, but we no longer need > that. > > Also fixes default_android_sdk_version to be a string. > -next builds need it to be a string. > > Bug: None > Change-Id: I99541f18510de93dae4c0d68b734638564f74ee2 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2340673 > Commit-Queue: Andrew Grieve <agrieve@chromium.org> > Reviewed-by: Mohamed Heikal <mheikal@chromium.org> > Reviewed-by: Dirk Pranke <dpranke@google.com> > Cr-Commit-Position: refs/heads/master@{#796020} TBR=dpranke@google.com,agrieve@chromium.org,mheikal@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: None Change-Id: Iad8597f6af00c534245fd1a40d1809d952758f47 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2344626Reviewed-by:
Ben Mason <benmason@chromium.org> Commit-Queue: Ben Mason <benmason@chromium.org> Cr-Commit-Position: refs/heads/master@{#796387}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/0bb27fe504d2..582102c9b7f4 2020-08-10 nisse@webrtc.org Add a VideoCoding::RegisterReceiveCodec method with payload_type 2020-08-10 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision cfbe56f1..8cce5f81 (796058:796325) 2020-08-10 asapersson@webrtc.org Update settings for balanced degradation. 2020-08-10 danilchap@webrtc.org Reland "Stop using RTPFragmentationHeader in sdk/android as unneeded" 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/+doc/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I6ed34f633a93a54793092c9395779a262c9bca3a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346524Reviewed-by:
-
Alice Wang authored
This CL fixes crash in the method getNumSignedIn in omaha.RequestGenerator. Since this method requires native setup, we should use same try-catch like in the method getNumGoogleAccountsOnDevice of the same class. Bug: 1049609 Change-Id: I68358f07299c2c7260ad39583a8f0498db29643d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2341638Reviewed-by:
Joshua Pawlicki <waffles@chromium.org> Commit-Queue: Alice Wang <aliceywang@chromium.org> Cr-Commit-Position: refs/heads/master@{#796385}
-
Naomi Musgrave authored
Track share targets as they are (un)registered, and start scanning. Only handles surfaces registered to the foreground for now. Bug: 1084644 Change-Id: I852388f8dd1d355263979d94f2959cc79f905929 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2292214 Commit-Queue: Naomi Musgrave <nmusgrave@chromium.org> Reviewed-by:
Richard Knoll <knollr@chromium.org> Reviewed-by:
Alex Chau <alexchau@chromium.org> Cr-Commit-Position: refs/heads/master@{#796384}
-
Carlos Caballero authored
Bug: 998171 Change-Id: Ida384d597f6a79e8e6eb70351d67aaf8a4595e5c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2332578 Commit-Queue: Carlos Caballero <carlscab@google.com> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Balazs Engedy <engedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#796383}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/a4cba6578f09..577cc158d1e2 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-mac-chromium Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Tbr: perfetto-bugs@google.com Change-Id: I043faf7cf84c30a64dfedfac403d2647ecc28d1d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2345947Reviewed-by:
-
Ben Mason authored
TBR=pkotwicz@chromium.org Bug: 1112352 Change-Id: Id84ed61c92c2250b76dcf5e693afc64db2434d45 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346584Reviewed-by:
-
Victor Fei authored
This is a reland of 4856b612 The original changed was reverted due to 'win-asan' bot flaky test for IA2_EVENT_TEXT_INSERTED/REMOVED and EVENT_OBJECT_REORDER for my newly added test 'aria-hidden-descendants-already-ignored.html'. It was only flaky for 'win-asan' bot and not flaky on normal win10 bot. This reland suppresses these flaky events since the tests do not require them. Original change's description: > Fire WIN HIDE event only on ignored ancestor > > Google drive expand/collapse state is not being announced due to > excessive HIDE/SHOW/REORDER events flooding NVDA, and NVDA end up > discarding most events. > > For example, if aria-hidden="true" is set on an ancestor node, which > would cause that node many of its descendants to be set to IGNORED > state which triggering too many EVENT_OBJECT_HIDE and causes NVDA > to drop the events. In reality, we only want EVENT_OBJECT_HIDE to be > generated on the ancestor node where aria-hidden="true" is set, so > not to flood and confuse NVDA with excessive events. > > This change fixes the above issue by firing EVENT_OBJECT_HIDE on the > root should the entire subtree changes to IGNORED state. > > Suppressing excessive SHOW/REORDER events will be addressed in follow up > patches. > > AX-RelNotes: NVDA can now announce Google drive "My Drive" expand/ > collapse state. > > Bug: 1019420 > Change-Id: I4fdabd6740630a149c1b22cdb3180d2f75807b10 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2309450 > Commit-Queue: Victor Fei <vicfei@microsoft.com> > Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org> > Reviewed-by: Adam Ettenberger <Adam.Ettenberger@microsoft.com> > Cr-Commit-Position: refs/heads/master@{#795017} Bug: 1019420 Change-Id: Iae15521bb69645eef9e3fc4aad4b6bd64345c0f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2340282 Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Reviewed-by:
Aaron Leventhal <aleventhal@chromium.org> Cr-Commit-Position: refs/heads/master@{#796380}
-
Sebastien Lalancette authored
Bug: 1093302 Change-Id: I443f9ed3817c2c7e7df5a93c0c1f8545fa593afd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2343576Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Commit-Queue: Sebastien Lalancette <seblalancette@chromium.org> Cr-Commit-Position: refs/heads/master@{#796379}
-
Antonio Sartori authored
This change implements a mechanism for the AncestorThrottle to send additional Content Security Policies to be enforced by blink. This is needed in case the AncestorThrottle allows a frame to be embedded after checking the Allow-CSP-From header for CSPEE. Bug: 1094909 Change-Id: Ib4c9e7cc0b1a620d648b8ef415cc04b77dfb4251 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2260772 Commit-Queue: Antonio Sartori <antoniosartori@chromium.org> Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Camille Lamy <clamy@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#796378}
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC cr-fuchsia+bot@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast Tbr: cr-fuchsia+bot@chromium.org Change-Id: I3f9bdb8d34b69bc820068caf3b1d87e45fa46304 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346491Reviewed-by:
-
Clemens Arbesser authored
This CL allows the header to support a full carousel. What it does: - Move header chip logic into native. - Use RecyclerView instead of hard-coded single chip view. - Potentially fixes an issue where the status message does not stretch across the whole available width. - Chips in the header now support change animations. There is an issue caused by a layout resize when switching between PEEK and non-PEEK mode. This is further discussed in the linked bug. The workaround is to delay the layout resize until the sheet state has settled. Bug: b/160856358 Change-Id: Id7617ed41119b85fdaa00ebaff7e856984b74b0a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2288567 Commit-Queue: Clemens Arbesser <arbesser@google.com> Reviewed-by:
Mathias Carlen <mcarlen@chromium.org> Cr-Commit-Position: refs/heads/master@{#796376}
-
Trevor Perrier authored
This CL adds the strings that will be used for the initial Android language decouple UI. Bug: 1113303 Change-Id: I62552adb641ec821ceef06be3fa62cb137aa009d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339340Reviewed-by:
Peter Wen <wnwen@chromium.org> Reviewed-by:
Megan Jablonski <megjablon@chromium.org> Commit-Queue: Peter Wen <wnwen@chromium.org> Auto-Submit: Trevor Perrier <perrier@chromium.org> Cr-Commit-Position: refs/heads/master@{#796375}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/c7ca0c496689..d44592935782 2020-08-10 kprokopenko@google.com [issues] Expand affected resources in case of a single resource 2020-08-10 sigurds@chromium.org Fix styling and focusing issues of the issue banner console message 2020-08-10 jacktfranklin@chromium.org getStyleSheets helper for components 2020-08-10 szuend@chromium.org [issues] Enable TypeScript type-checking for all 'issues' files 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:1011811,chromium:1068116,chromium:1072335,chromium:1096481 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I120a41d85749c952593b3b214cccf7e24e68918a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346237Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/e9cc27752c42..d5099cc1545f 2020-08-10 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Vulkan-Loader from aba3ab0ce72f to 61bf3be73c1e (1 revision) 2020-08-10 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Vulkan-Tools from a1c21580f50b to 1590d46aaaeb (3 revisions) 2020-08-10 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Vulkan-ValidationLayers from 9ba1bc28d878 to b399fb08896a (2 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 ynovikov@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: ynovikov@google.com Change-Id: Idf683dd632545cb011538850925a31bec2396fd7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346239Reviewed-by:
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/530fc3bb4cba..cac176496829 2020-08-10 robertphillips@google.com Add a GrSmallPathAtlasMgr class 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 fmalita@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: fmalita@google.com Change-Id: I7853eed72f4da329549c42d68455fd5c8de433cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346242Reviewed-by:
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1597037945-c748d93b7b3b8df201950e67d57a776238968dea.profdata to chrome-mac-master-1597060771-94a7300bd1819f6d10eaf4c394bfbc10cebf8f71.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 sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@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: chrome/try:mac-chrome Tbr: sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@google.com Change-Id: Ied4ae6e59305c6586ffc650fd658aa0742106778 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346489Reviewed-by:
-
Fred Mello authored
https://docs.google.com/document/d/1q7MxrwLlI7EOeKDap3ubrGjGUlKAcHq7pWn9G6pRXE4/ Bug: 1112872 Change-Id: I80c79343dd32b9fe38967c476584e92a228d4e50 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339797Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Commit-Queue: Yaron Friedman <yfriedman@chromium.org> Auto-Submit: Fred Mello <fredmello@chromium.org> Cr-Commit-Position: refs/heads/master@{#796370}
-
Peter Kasting authored
It already had *, and the underlying TimeDelta has long had /(T), so this just makes the API a little less asymmetric. This simplifies one callsite. Bug: none Change-Id: I49fe5f69a36c53c7857e623f17f7c5b4e66346f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2344815 Auto-Submit: Peter Kasting <pkasting@chromium.org> Commit-Queue: Kevin Ellis <kevers@chromium.org> Reviewed-by:
Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#796369}
-
Gauthier Ambard authored
The TabGridAdaptor was used for the migration from the old TabSwitcher. Bug: none Change-Id: I9d5991bdbcbafad70da6dc856627b738aa1fd885 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2341645 Commit-Queue: Gauthier Ambard <gambard@chromium.org> Reviewed-by:
Mark Cogan <marq@chromium.org> Cr-Commit-Position: refs/heads/master@{#796368}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/a4cba6578f09..577cc158d1e2 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-linux-chromium Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Tbr: perfetto-bugs@google.com Change-Id: I15b42ae3bc02ff495db088562127736d9fe27585 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2345946Reviewed-by:
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/577cc158d1e2..01e0ccdc9b8b 2020-08-10 lalitm@google.com Merge "perfetto: add unit and description for GpuMemTotal events" If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:linux-perfetto-rel Bug: None Tbr: perfetto-bugs@google.com Change-Id: I8de476aa0efed4dc106bc4b89b8ed47e996da7a6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346240Reviewed-by:
-
Alexander Dunaev authored
The selection clipboard is available on Linux/X11 but Ozone hides the platform so it is only known at run time what is it. Because of that, Ozone/X11 could not use the selection clipboard. This CL introduces a new call into the ClipboardHost Mojo interface so the renderer can query the host for whether the selection clipboard is available. Change-Id: I64fc8ca66509c2b12f3d03fb53aad3e986772153 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307234 Commit-Queue: Alexander Dunaev <adunaev@igalia.com> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Darwin Huang <huangdarwin@chromium.org> Cr-Commit-Position: refs/heads/master@{#796365}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/0fd4513a30ec..623cf68b45ca 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 andypaicu@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: andypaicu@google.com Change-Id: Ifeeaaa7157dc3b1a720a3b4bc435805120339f79 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346231Reviewed-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@{#796364}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/4c2f9c90f425..0bb27fe504d2 2020-08-10 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 61491ae4..cfbe56f1 (795944:796058) 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/+doc/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: Ie7f7d736245c358e12558e8a0a7b7c61ff020a8b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346238Reviewed-by:
-
Xi Han authored
Bug: 1103838, 1092642 Change-Id: Ic2aeceb824c7fb39dc475c72fbe0f897f6dcbf59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2325248Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Commit-Queue: Xi Han <hanxi@chromium.org> Cr-Commit-Position: refs/heads/master@{#796362}
-
Christian Dullweber authored
Use CookieControlsMode and simplify some code paths. Bug: 1104836 Change-Id: I67f893bf8eb6dcfc1d39eb7a1f2b5942ab28eeb5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339415Reviewed-by:
Theodore Olsauskas-Warren <sauski@google.com> Reviewed-by:
-
Antonio Sartori authored
This change adds logic to the AncestorThrottle and the RenderFrameHostImpl for: - validating the parsed content of the frame 'csp' attribute as stored in the FrameTreeNode; - setting the Sec-Required-CSP header accordingly on outgoing requests; - store the validated required csp context in the RenderFrameHost after the navigation is committed. Bug: 1094909 Change-Id: Iaf2c733047b4a153f0dfaccf1d5d018f83d7cc8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2330051 Commit-Queue: Antonio Sartori <antoniosartori@chromium.org> Reviewed-by: -
Xi Han authored
Bug: 1103838, 1092642, 1076274 Change-Id: Ia44be7834b698bd37f0d6bd80de31257ea38eecf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2325249Reviewed-by:
-
Alex Ilin authored
The flag is no longer needed since the Gaia endpoint has been rolled out to prod. The only consumer of Reauth feature is backed by its own feature flag. Bug: 1045515 Change-Id: Ia12aa2abfc064a431c1a24ab85de231c07e8ebfa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339530 Commit-Queue: Alex Ilin <alexilin@chromium.org> Auto-Submit: Alex Ilin <alexilin@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#796358}
-
Renato Silva authored
Add strings and screenshots for the upcoming switch button on the login/lock screen. Bug: 1075994 Change-Id: Ic5aa9b083dc2251edda7ad7a634bf93f17f1981b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346264 Commit-Queue: Renato Silva <rrsilva@google.com> Auto-Submit: Renato Silva <rrsilva@google.com> Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Cr-Commit-Position: refs/heads/master@{#796357}
-
Maksim Sisov (GMT+3) authored
This reverts commit 81dab1d6. Reason for revert: Found a better solution Original change's description: > X11 and Ozone: Fix screen initialization for Ozone config > > The tests that use ClientHintsBrowserTest override FeatureList > during ::SetUp call, which results in erasing UseOzonePlatform > from that, and InProcessBrowserTest::SetScreenInstance cannot > check the status of the feature flag during ::SetUp call. And, > as a consequence, fail to decide what path it must use. Append > the UseOzonePlatform feature flag back to the scoped feature list > so that initialization happens properly. > > ----- > > PS: Please note that this is a temp solution that will help to choose > between ozone and non-ozone X11 build. The switch that will be used > to choose the path is --enable-features=UseOzonePlatform. Once > non-Ozone X11 path is removed (hopefully by Q1 2021 depending on how > the finch trial goes), the wrapper will be removed. > > Please also note that it's impossible to build use_x11 && use_ozone > without some hacks in PlatformCursor code. The changes to that are > on their way to upstream. > > ---- > > Bug: 1085700 > Change-Id: I995a434a25b6e1a0db3d16bb516184c0d3bc87de > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2333843 > Reviewed-by: Scott Violet <sky@chromium.org> > Commit-Queue: Maksim Sisov (GMT+3) <msisov@igalia.com> > Cr-Commit-Position: refs/heads/master@{#796341} TBR=sky@chromium.org,msisov@igalia.com Change-Id: I2f04fc98b373303ee5ea131f3c79550cfa3c0e8f No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1085700 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346427Reviewed-by:
Maksim Sisov (GMT+3) <msisov@igalia.com> Commit-Queue: Maksim Sisov (GMT+3) <msisov@igalia.com> Cr-Commit-Position: refs/heads/master@{#796356}
-
