- 28 Feb, 2020 40 commits
-
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/4eca785b40e3..96c6bce9e4f3 git log 4eca785b40e3..96c6bce9e4f3 --date=short --first-parent --format='%ad %ae %s' 2020-02-28 szuend@chromium.org [utilities] Remove Array#select 2020-02-28 mathias@chromium.org Enable no-else-return lint rule with autofix Created with: gclient setdep -r src/third_party/devtools-frontend/src@96c6bce9e4f3 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Bug: chromium:1050549,chromium:1057042 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I862a67b16b0f7e7d04038c2abadb0c34a18d48d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080309Reviewed-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@{#745508}
-
Gabriel Charette authored
This CL is a logical no-op. It manually covers the use cases the script (https://crbug.com/1026641#c22) didn't cover in https://chromium-review.googlesource.com/c/chromium/src/+/2026350. A few of the affected files were also migrated to content::GetUIThreadTaskRunner() whenever surrounding code consistency was at stake (but the bulk of that migration is staged to happen after this one so this wasn't a priority in this batch). Most files intentionally kept base/task/post_task.h as an include. It is still required because of a cyclical dependency during the migration preventing base/task/thread_pool.h from implicitly providing base/task/task_traits.h to its users (callers that explicitly store TaskTraits and include task_traits.h don't have this problem). The post_task.h include will be cleaned up in a later phase. This CL was uploaded by git cl split. R=hashimoto@chromium.org Bug: 1026641 Change-Id: I6ea3c67e54a44bae1414f39ce1fb343cfb3a2c99 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079073 Commit-Queue: Gabriel Charette <gab@chromium.org> Auto-Submit: Gabriel Charette <gab@chromium.org> Reviewed-by:
Ryo Hashimoto <hashimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#745507}
-
Gabriel Charette authored
This CL is a logical no-op. It manually covers the use cases the script (https://crbug.com/1026641#c22) didn't cover in https://chromium-review.googlesource.com/c/chromium/src/+/2026350. A few of the affected files were also migrated to content::GetUIThreadTaskRunner() whenever surrounding code consistency was at stake (but the bulk of that migration is staged to happen after this one so this wasn't a priority in this batch). Most files intentionally kept base/task/post_task.h as an include. It is still required because of a cyclical dependency during the migration preventing base/task/thread_pool.h from implicitly providing base/task/task_traits.h to its users (callers that explicitly store TaskTraits and include task_traits.h don't have this problem). The post_task.h include will be cleaned up in a later phase. This CL was uploaded by git cl split. R=pastarmovj@chromium.org Bug: 1026641 Change-Id: I8d1d6f3c2d6da8d599078e727b0c27587f664017 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078661 Commit-Queue: Gabriel Charette <gab@chromium.org> Auto-Submit: Gabriel Charette <gab@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Cr-Commit-Position: refs/heads/master@{#745506}
-
Dan Harrington authored
The annotation was changed, but the XML file wasn't updated to correspond. See bug. TBR=msramek@chromium.org Bug: 1057089 Change-Id: Idaec65e76aa95741c45874131c6ca92d52ff37a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080456Reviewed-by:
Dan H <harringtond@chromium.org> Commit-Queue: Dan H <harringtond@chromium.org> Cr-Commit-Position: refs/heads/master@{#745505}
-
Gabriel Charette authored
Migrate off base::ThreadPool()-as-a-trait in /chrome/browser/media/webrtc/webrtc_event_log_manager.cc This CL is a logical no-op. It manually covers the use cases the script (https://crbug.com/1026641#c22) didn't cover in https://chromium-review.googlesource.com/c/chromium/src/+/2026350. A few of the affected files were also migrated to content::GetUIThreadTaskRunner() whenever surrounding code consistency was at stake (but the bulk of that migration is staged to happen after this one so this wasn't a priority in this batch). Most files intentionally kept base/task/post_task.h as an include. It is still required because of a cyclical dependency during the migration preventing base/task/thread_pool.h from implicitly providing base/task/task_traits.h to its users (callers that explicitly store TaskTraits and include task_traits.h don't have this problem). The post_task.h include will be cleaned up in a later phase. This CL was uploaded by git cl split. R=eladalon@chromium.org Bug: 1026641 Change-Id: I1a06918db9cf2e701dfd03e9d6455eecdfdb0d9f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079085 Commit-Queue: Gabriel Charette <gab@chromium.org> Auto-Submit: Gabriel Charette <gab@chromium.org> Reviewed-by:
Elad Alon <eladalon@chromium.org> Cr-Commit-Position: refs/heads/master@{#745504}
-
Gabriel Charette authored
This CL is a logical no-op. It manually covers the use cases the script (https://crbug.com/1026641#c22) didn't cover in https://chromium-review.googlesource.com/c/chromium/src/+/2026350. A few of the affected files were also migrated to content::GetUIThreadTaskRunner() whenever surrounding code consistency was at stake (but the bulk of that migration is staged to happen after this one so this wasn't a priority in this batch). Most files intentionally kept base/task/post_task.h as an include. It is still required because of a cyclical dependency during the migration preventing base/task/thread_pool.h from implicitly providing base/task/task_traits.h to its users (callers that explicitly store TaskTraits and include task_traits.h don't have this problem). The post_task.h include will be cleaned up in a later phase. This CL was uploaded by git cl split. R=steimel@chromium.org Bug: 1026641 Change-Id: I86672714403013e0c9cd53df3b9919b497e72552 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078423 Commit-Queue: Gabriel Charette <gab@chromium.org> Auto-Submit: Gabriel Charette <gab@chromium.org> Reviewed-by:
Tommy Steimel <steimel@chromium.org> Cr-Commit-Position: refs/heads/master@{#745503}
-
Gabriel Charette authored
This CL is a logical no-op. It manually covers the use cases the script (https://crbug.com/1026641#c22) didn't cover in https://chromium-review.googlesource.com/c/chromium/src/+/2026350. A few of the affected files were also migrated to content::GetUIThreadTaskRunner() whenever surrounding code consistency was at stake (but the bulk of that migration is staged to happen after this one so this wasn't a priority in this batch). Most files intentionally kept base/task/post_task.h as an include. It is still required because of a cyclical dependency during the migration preventing base/task/thread_pool.h from implicitly providing base/task/task_traits.h to its users (callers that explicitly store TaskTraits and include task_traits.h don't have this problem). The post_task.h include will be cleaned up in a later phase. This CL was uploaded by git cl split. R=asvitkine@chromium.org Bug: 1026641 Change-Id: I4ec15c2ebfc60e84bc8d8e2d7bdf6dc9f0f783b5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079079Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Commit-Queue: Alexei Svitkine <asvitkine@chromium.org> Auto-Submit: Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#745502}
-
Geoff Lang authored
TBR=zmo@chromium.org BUG=1056984 BUG=1030835 Change-Id: I491b8c1d38f9637d37a92cb6d4b84e7ff2a5d7e4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079463Reviewed-by:
Geoff Lang <geofflang@chromium.org> Commit-Queue: Geoff Lang <geofflang@chromium.org> Cr-Commit-Position: refs/heads/master@{#745501}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/3e5fe285a7ef..416d37452275 git log 3e5fe285a7ef..416d37452275 --date=short --first-parent --format='%ad %ae %s' 2020-02-28 jmadill@chromium.org PipelineCache: Handle nullptr mismatch of specialization info. 2020-02-28 sugoi@google.com Implement ASTC support Created with: gclient setdep -r src/third_party/swiftshader@416d37452275 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/+/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 Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: I365e26cfa261fbdb6f6ec34a9e7d2f982488785d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080452Reviewed-by:
-
Gabriel Charette authored
This CL is a logical no-op. It manually covers the use cases the script (https://crbug.com/1026641#c22) didn't cover in https://chromium-review.googlesource.com/c/chromium/src/+/2026350. A few of the affected files were also migrated to content::GetUIThreadTaskRunner() whenever surrounding code consistency was at stake (but the bulk of that migration is staged to happen after this one so this wasn't a priority in this batch). Most files intentionally kept base/task/post_task.h as an include. It is still required because of a cyclical dependency during the migration preventing base/task/thread_pool.h from implicitly providing base/task/task_traits.h to its users (callers that explicitly store TaskTraits and include task_traits.h don't have this problem). The post_task.h include will be cleaned up in a later phase. This CL was uploaded by git cl split. R=reillyg@chromium.org Bug: 1026641 Change-Id: I781bcf648308b5583f5d85308ee0383b7f69be02 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078420 Commit-Queue: Gabriel Charette <gab@chromium.org> Auto-Submit: Gabriel Charette <gab@chromium.org> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#745499}
-
Aaron Leventhal authored
When objects are only programmatically scrollable, e.g. overflow:hidden, as opposed to overflow:auto|scroll, do not mark them as scrollable. Bug: 1055344 Change-Id: Ib5ade11a7a92720d6571acf6d65112696f2a2535 Cq-Do-Not-Cancel-Tryjobs: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2070232Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Auto-Submit: Aaron Leventhal <aleventhal@chromium.org> Cr-Commit-Position: refs/heads/master@{#745498}
-
Toni Barzic authored
Updates how animating shelf background's drag handle layer bounds are calculated. Instead of directly using bounds from that the drag handle view has within the opaque shelf widget, calculate the animating drag handle bounds directly by centering the drag handle within the animating background bounds. Opaque background bounds are calculated based on the shelf widget size, which may differ from the animating (in-app) shelf size (e.g. on home screen). Using the opaque background drag handle bounds for animating background would displace the drag handle when that is the case. Change-Id: I51cb9a4d031286329784162193627bb09c608043 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079839Reviewed-by:
Manu Cornet <manucornet@chromium.org> Commit-Queue: Toni Baržić <tbarzic@chromium.org> Cr-Commit-Position: refs/heads/master@{#745497}
-
Ahmed Fakhry authored
This CL implements a new responsive layout for the desks bar in overview, which makes its height a function of the display height rather than constant (when the layout is not compact). This will be very useful for large screens, as well as in portrait mode (since will have more room for desks' editable names). Demo: https://bugs.chromium.org/p/chromium/issues/detail?id=1042981#c4 BUG=1042981 TEST=Manually. Change-Id: I7335766d699f081a62819bd77daa9c0a9e6021eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2076786Reviewed-by:
Sammie Quon <sammiequon@chromium.org> Commit-Queue: Ahmed Fakhry <afakhry@chromium.org> Cr-Commit-Position: refs/heads/master@{#745496}
-
Thomas Tellier authored
Bug: 993653 Change-Id: I21dc10859842208b355245137ba5d141e52c9b09 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080415Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Commit-Queue: Thomas Tellier <tellier@google.com> Cr-Commit-Position: refs/heads/master@{#745495}
-
Thomas Tellier authored
Bug: 993653 Change-Id: I4293b7f09d887a68911bfbf1c4e26cdf82c55304 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080248Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Commit-Queue: Thomas Tellier <tellier@google.com> Cr-Commit-Position: refs/heads/master@{#745494}
-
Gabriel Charette authored
This CL is a logical no-op. It manually covers the use cases the script (https://crbug.com/1026641#c22) didn't cover in https://chromium-review.googlesource.com/c/chromium/src/+/2026350. A few of the affected files were also migrated to content::GetUIThreadTaskRunner() whenever surrounding code consistency was at stake (but the bulk of that migration is staged to happen after this one so this wasn't a priority in this batch). Most files intentionally kept base/task/post_task.h as an include. It is still required because of a cyclical dependency during the migration preventing base/task/thread_pool.h from implicitly providing base/task/task_traits.h to its users (callers that explicitly store TaskTraits and include task_traits.h don't have this problem). The post_task.h include will be cleaned up in a later phase. This CL was uploaded by git cl split. R=rbpotter@chromium.org Bug: 1026641 Change-Id: I17edfca297131ab8f59d9f9391a401ec11b30ea9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079077 Commit-Queue: Gabriel Charette <gab@chromium.org> Auto-Submit: Gabriel Charette <gab@chromium.org> Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#745493}
-
Lei Zhang authored
The histogram data has been steady over time, so there is no new insight from collecting new data. Bug: 1037199 Change-Id: Ib429623bcc75a807e0fe7107b0f507d49b29c590 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2076848Reviewed-by:
Henrique Nakashima <hnakashima@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#745492}
-
Chris Lu authored
Fixed: 1056251 Change-Id: I531de3583a0877e1925f1a8c322c11610f3b4416 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078842Reviewed-by:
Sergio Collazos <sczs@chromium.org> Commit-Queue: Chris Lu <thegreenfrog@chromium.org> Cr-Commit-Position: refs/heads/master@{#745491}
-
Changwan Ryu authored
Extend the StartupTimeActivity to handle different intent options to measure different startup scenarios. Bug: 1055970 Change-Id: Ib0616ee40cc4d2833ab69f994faedf9abf6345c0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068646Reviewed-by:
Tao Bai <michaelbai@chromium.org> Reviewed-by:
Richard Coles <torne@chromium.org> Commit-Queue: Changwan Ryu <changwan@chromium.org> Cr-Commit-Position: refs/heads/master@{#745490}
-
Gabriel Charette authored
This CL is a logical no-op. It manually covers the use cases the script (https://crbug.com/1026641#c22) didn't cover in https://chromium-review.googlesource.com/c/chromium/src/+/2026350. A few of the affected files were also migrated to content::GetUIThreadTaskRunner() whenever surrounding code consistency was at stake (but the bulk of that migration is staged to happen after this one so this wasn't a priority in this batch). Most files intentionally kept base/task/post_task.h as an include. It is still required because of a cyclical dependency during the migration preventing base/task/thread_pool.h from implicitly providing base/task/task_traits.h to its users (callers that explicitly store TaskTraits and include task_traits.h don't have this problem). The post_task.h include will be cleaned up in a later phase. This CL was uploaded by git cl split. R=mark@chromium.org Bug: 1026641 Change-Id: I38da1f6c3416d9f3539129fcb0977d3edc5980e8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079151 Commit-Queue: Gabriel Charette <gab@chromium.org> Auto-Submit: Gabriel Charette <gab@chromium.org> Reviewed-by:
Mark Mentovai <mark@chromium.org> Cr-Commit-Position: refs/heads/master@{#745489}
-
Maks Orlovich authored
This previously inherited settings from the base profile even if they were configured not to, which e.g. made client hints in incognito be improperly influenced by the normal profile state, as noticed by Aaron Tagliaboschi (and originally started to fix in a different way in https://chromium-review.googlesource.com/c/chromium/src/+/2034051) This also appeared to cause some weirdness with important site computation (bug 993021) and with some device permissions. Bug: 1052406, 993021 Change-Id: Ieeaaf0d508161568455ed077be820fd03831afdc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2047446 Commit-Queue: Maksim Orlovich <morlovich@chromium.org> Reviewed-by:
Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org> Reviewed-by:
calamity <calamity@chromium.org> Reviewed-by:
Balazs Engedy <engedy@chromium.org> Reviewed-by:
Carlos IL <carlosil@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Reviewed-by:
Christian Dullweber <dullweber@chromium.org> Cr-Commit-Position: refs/heads/master@{#745488}
-
Henrique Nakashima authored
Use the generic way of checking if a feature flag is enabled in CachedFeatureFlags. There is a slight functional change: if the value is queried before native is loaded, and then a different value is cached when native is loaded, a second query will now give the same result returned in the first. Bug: 1012975 Change-Id: I314455b927d5f4a46aeb13de922682cc600e7056 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079532Reviewed-by:
Peter Kotwicz <pkotwicz@chromium.org> Commit-Queue: Henrique Nakashima <hnakashima@chromium.org> Cr-Commit-Position: refs/heads/master@{#745487}
-
Koji Ishii authored
This patch fixes painting floats in self-painting inline. To support this, this changes |PaintFloatingItems| to use |NGInlineCursor| to traverse descendants. Bug: 982194 Change-Id: I234ec7f32f895add62fe782aef133705fa7a7e61 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078379 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#745486}
-
Jan Wilken Dörrie authored
This change generalizes the SortKeyIdGenerator to take arbitrary types as keys, and allows customization of the id type and key comparator. This will be useful when we need to generate ids for compromised credentials as well. To make the name more generic the class is renamed to IdGenerator. TBR=schwering@google.com Bug: 1047726 Change-Id: I1b9e25aa4ccd0a732c810bde20163d46d5a46d67 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080430Reviewed-by:
Jan Wilken Dörrie <jdoerrie@chromium.org> Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org> Cr-Commit-Position: refs/heads/master@{#745485}
-
Gabriel Charette authored
This CL is a logical no-op. It manually covers the use cases the script (https://crbug.com/1026641#c22) didn't cover in https://chromium-review.googlesource.com/c/chromium/src/+/2026350. A few of the affected files were also migrated to content::GetUIThreadTaskRunner() whenever surrounding code consistency was at stake (but the bulk of that migration is staged to happen after this one so this wasn't a priority in this batch). Most files intentionally kept base/task/post_task.h as an include. It is still required because of a cyclical dependency during the migration preventing base/task/thread_pool.h from implicitly providing base/task/task_traits.h to its users (callers that explicitly store TaskTraits and include task_traits.h don't have this problem). The post_task.h include will be cleaned up in a later phase. This CL was uploaded by git cl split. R=boliu@chromium.org Bug: 1026641 Change-Id: I165a26f5d13f84d1f7ef03228e5faa34fe7c9a86 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078660 Commit-Queue: Gabriel Charette <gab@chromium.org> Auto-Submit: Gabriel Charette <gab@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#745484}
-
Chris Harrelson authored
Bug: 1045421 Change-Id: Ic152bb2d1c88e34e3de012b4da9164ca1ff822ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079304 Auto-Submit: Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#745483}
-
Manu Cornet authored
Change-Id: Icab080ad2cffd4b0e46c4075c2bb0c23beca9e2f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079254Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Manu Cornet <manucornet@chromium.org> Cr-Commit-Position: refs/heads/master@{#745482}
-
Gabriel Charette authored
This CL is a logical no-op. It manually covers the use cases the script (https://crbug.com/1026641#c22) didn't cover in https://chromium-review.googlesource.com/c/chromium/src/+/2026350. A few of the affected files were also migrated to content::GetUIThreadTaskRunner() whenever surrounding code consistency was at stake (but the bulk of that migration is staged to happen after this one so this wasn't a priority in this batch). Most files intentionally kept base/task/post_task.h as an include. It is still required because of a cyclical dependency during the migration preventing base/task/thread_pool.h from implicitly providing base/task/task_traits.h to its users (callers that explicitly store TaskTraits and include task_traits.h don't have this problem). The post_task.h include will be cleaned up in a later phase. This CL was uploaded by git cl split. R=poromov@chromium.org Bug: 1026641 Change-Id: Ie31be4a6fa7de7ffb33681dee388fde3bb97a911 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078663 Commit-Queue: Gabriel Charette <gab@chromium.org> Auto-Submit: Gabriel Charette <gab@chromium.org> Reviewed-by:
Sergey Poromov <poromov@chromium.org> Cr-Commit-Position: refs/heads/master@{#745481}
-
Gabriel Charette authored
This CL is a logical no-op. It manually covers the use cases the script (https://crbug.com/1026641#c22) didn't cover in https://chromium-review.googlesource.com/c/chromium/src/+/2026350. A few of the affected files were also migrated to content::GetUIThreadTaskRunner() whenever surrounding code consistency was at stake (but the bulk of that migration is staged to happen after this one so this wasn't a priority in this batch). Most files intentionally kept base/task/post_task.h as an include. It is still required because of a cyclical dependency during the migration preventing base/task/thread_pool.h from implicitly providing base/task/task_traits.h to its users (callers that explicitly store TaskTraits and include task_traits.h don't have this problem). The post_task.h include will be cleaned up in a later phase. This CL was uploaded by git cl split. R=ganesh@chromium.org Bug: 1026641 Change-Id: If0f5732e700bbf9cc8631d53913d3049bec345f1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078424 Commit-Queue: Gabriel Charette <gab@chromium.org> Auto-Submit: Gabriel Charette <gab@chromium.org> Reviewed-by:
S. Ganesh <ganesh@chromium.org> Cr-Commit-Position: refs/heads/master@{#745480}
-
Gabriel Charette authored
This CL is a logical no-op. It manually covers the use cases the script (https://crbug.com/1026641#c22) didn't cover in https://chromium-review.googlesource.com/c/chromium/src/+/2026350. A few of the affected files were also migrated to content::GetUIThreadTaskRunner() whenever surrounding code consistency was at stake (but the bulk of that migration is staged to happen after this one so this wasn't a priority in this batch). Most files intentionally kept base/task/post_task.h as an include. It is still required because of a cyclical dependency during the migration preventing base/task/thread_pool.h from implicitly providing base/task/task_traits.h to its users (callers that explicitly store TaskTraits and include task_traits.h don't have this problem). The post_task.h include will be cleaned up in a later phase. This CL was uploaded by git cl split. R=proberge@chromium.org Bug: 1026641 Change-Id: I16138ae911bc05fa34eec4bed07eef11eb1ee74c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078427 Commit-Queue: Gabriel Charette <gab@chromium.org> Auto-Submit: Gabriel Charette <gab@chromium.org> Reviewed-by:
proberge <proberge@chromium.org> Cr-Commit-Position: refs/heads/master@{#745479}
-
Olivier Robin authored
hang-report field was done asynchronously and too late to be consistently present in the crash reports. It seems that the flag was only present in case of a second freeze. Set the flag synchronously before generating the crash report. Bug: 1056178 Change-Id: Ia7958c61a01dd9ffa592f3ba6b86481b50e8c89d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2074220Reviewed-by:
Justin Cohen <justincohen@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Commit-Queue: Olivier Robin <olivierrobin@chromium.org> Cr-Commit-Position: refs/heads/master@{#745478}
-
Thomas Lukaszewicz authored
Fixed a visual artifact on ToolbarButton where the insets of the border may not have updated correctly, depending on how the animation timing ended up resolving. This was caused by not recomputing the border when the height of the ToolbarButton changed, resulting in incorrect border insets. Bug: 1053917 Change-Id: Ia15ffaf7a5d08f75b4d88bc61deb7bcc3382df2d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067384 Commit-Queue: Thomas Lukaszewicz <tluk@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#745477}
-
Gabriel Charette authored
This CL is a logical no-op. It manually covers the use cases the script (https://crbug.com/1026641#c22) didn't cover in https://chromium-review.googlesource.com/c/chromium/src/+/2026350. A few of the affected files were also migrated to content::GetUIThreadTaskRunner() whenever surrounding code consistency was at stake (but the bulk of that migration is staged to happen after this one so this wasn't a priority in this batch). Most files intentionally kept base/task/post_task.h as an include. It is still required because of a cyclical dependency during the migration preventing base/task/thread_pool.h from implicitly providing base/task/task_traits.h to its users (callers that explicitly store TaskTraits and include task_traits.h don't have this problem). The post_task.h include will be cleaned up in a later phase. This CL was uploaded by git cl split. R=zentaro@chromium.org Bug: 1026641 Change-Id: I020767964acaf25eb38bd90aac0352c8e835ee72 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079078 Commit-Queue: Gabriel Charette <gab@chromium.org> Auto-Submit: Gabriel Charette <gab@chromium.org> Reviewed-by:
Anand Mistry <amistry@chromium.org> Cr-Commit-Position: refs/heads/master@{#745476}
-
Renato Silva authored
Adds new strings and icons for the marketing opt in screen. Bug: 1023370 Change-Id: I45f5388862d5337432cab2beb1b253d2ebb93447 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080411 Auto-Submit: Renato Silva <rrsilva@google.com> Reviewed-by:
-
Yann Dago authored
Bug: 958893 Change-Id: If0cc3e0cd1e70a3b21c675b3979166f7aaba554d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2076438 Commit-Queue: Yann Dago <ydago@chromium.org> Reviewed-by:
Greg Thompson <grt@chromium.org> Cr-Commit-Position: refs/heads/master@{#745474}
-
Gabriel Charette authored
This CL is a logical no-op. It manually covers the use cases the script (https://crbug.com/1026641#c22) didn't cover in https://chromium-review.googlesource.com/c/chromium/src/+/2026350. A few of the affected files were also migrated to content::GetUIThreadTaskRunner() whenever surrounding code consistency was at stake (but the bulk of that migration is staged to happen after this one so this wasn't a priority in this batch). Most files intentionally kept base/task/post_task.h as an include. It is still required because of a cyclical dependency during the migration preventing base/task/thread_pool.h from implicitly providing base/task/task_traits.h to its users (callers that explicitly store TaskTraits and include task_traits.h don't have this problem). The post_task.h include will be cleaned up in a later phase. This CL was uploaded by git cl split. R=sky@chromium.org Bug: 1026641 Change-Id: If132c13d94dcca692a7f8a8fc32c34522ac4b33f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078779 Commit-Queue: Gabriel Charette <gab@chromium.org> Auto-Submit: Gabriel Charette <gab@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#745473}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/c1503990b2d3..ea63c21e644f Created with: gclient setdep -r src-internal@ea63c21e644f If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC jbudorick@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: jbudorick@google.com Change-Id: I79f56328cc8e15518cfc2154783c692eb6a4e7ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080306Reviewed-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@{#745472}
-
Josh Nohle authored
When a successful SyncMetadata response is received, cache the encrypted and unencrypted local device metadata, along with the encrypting group public key, that was sent in the SyncMetadata request. During the next SyncMetadata request, if the local device metadata and the encrypting group public key have not changed since they were last cached, reuse the cached encrypted local device metadata. Why are we doing this? Because the ECIES encryptor uses a different session key for each encryption, the blob could change even if the underlying metadata and group public key have not changed. We do not want the CryptAuth server to act as though device metadata has changed if the underlying data and encrypting key remain the same. Fixed: 1054654 Change-Id: Ie94247295c9d76d984a861ed934219a5496bf268 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079437 Commit-Queue: Josh Nohle <nohle@chromium.org> Reviewed-by:
James Vecore <vecore@google.com> Cr-Commit-Position: refs/heads/master@{#745471}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/6165cdcbe8fa..2998999dca23 git log 6165cdcbe8fa..2998999dca23 --date=short --first-parent --format='%ad %ae %s' 2020-02-28 vapier@chromium.org lib: restrict the strptime workaround to Python 2 2020-02-28 vapier@chromium.org portage_util: include ebuild/script version in fatal errors 2020-02-28 vapier@chromium.org cros_build_lib: RunCommand: drop old alias 2020-02-28 ahassani@chromium.org paygen: Add OWNERS.au as the new owners to include more people. 2020-02-27 ahassani@chromium.org auto_updater: use chromitized stateful_update 2020-02-27 ahassani@chromium.org stateful_updater: Chromitize stateful_update 2020-02-27 seanabraham@chromium.org chromeos_config: disable HW tests for heli Created with: gclient setdep -r src/third_party/chromite@2998999dca23 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/chromite-chromium-autoroll Please CC chrome-os-gardeners@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:chromeos-kevin-rel Bug: None Tbr: chrome-os-gardeners@google.com Change-Id: Ie8c36e6b63a870fdc82437234b3ae53bcc159f0b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080308Reviewed-by:
-
Stephen McGruer authored
This diff was generated by running: find . -type f -print0 | xargs -0 perl -pi -e "BEGIN { \$/ = undef; } s/assert_throws\(([ \n]*)\{ *[\"']?name[\"']? *: *(['\"](?:InvalidStateError|SyntaxError|NotSupportedError|DataError|SecurityError)[\"']) *\} *(, *.)/assert_throws_dom(\1\2\3/gs" Bug: 1051932 Change-Id: I44382930e4eee93daeb806acf4011ab0430965ad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078798 Commit-Queue: Luke Z <lpz@chromium.org> Auto-Submit: Stephen McGruer <smcgruer@chromium.org> Reviewed-by:Luke Z <lpz@chromium.org> Cr-Commit-Position: refs/heads/master@{#745469}
-
