- 28 Feb, 2020 40 commits
-
-
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:
Roman Sorokin [CET] <rsorokin@chromium.org> Commit-Queue: Roman Sorokin [CET] <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#745475}
-
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:
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@{#745470}
-
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}
-
Shuangshuang Zhou authored
This modification changes two trace operations for "GetDecodedImageForDraw()" and "DrawWithImageFinished()" from "cc"to "cc.debug" category. While running Canvas 2D workloads with quite a lot canvas elements to be drawn, excessive trace operations introduce expensive performance overheads, especially for those hardware platforms with integrated graphics cards or old graphics drivers. Bug: 1051385 Change-Id: I7cb1b7a3afcb207ac6b7791f21dc621a20e42864 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2059771Reviewed-by:
vmpstr <vmpstr@chromium.org> Commit-Queue: vmpstr <vmpstr@chromium.org> Cr-Commit-Position: refs/heads/master@{#745468}
-
Oriol Brufau authored
LayoutObject::AnonymousHasStylePropagationOverride is only called from LayoutObject::PropagateStyleToAnonymousChildren, but only for anonymous layout objects with a kPseudoIdNone style type. However, LayoutListMarkers are no longer anonymous and they have a kPseudoIdMarker style type. So the override is not used. BUG=457718 Change-Id: Iae2bee6e9f68cdba1cd17529ecae73938f162c8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080264Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Commit-Queue: Oriol Brufau <obrufau@igalia.com> Cr-Commit-Position: refs/heads/master@{#745467}
-
Peter Kasting authored
Bug: none Change-Id: Ieb7be7b5f7f257d1bc9631153d5cf8f0b5d8f482 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079939 Auto-Submit: Peter Kasting <pkasting@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:
-
Justin Cohen authored
Change-Id: I2cd296f3a8b4e0af505331200ef9cbb531ada878 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079171 Auto-Submit: Justin Cohen <justincohen@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Commit-Queue: Justin Cohen <justincohen@chromium.org> Cr-Commit-Position: refs/heads/master@{#745465}
-
Thomas Tellier authored
Change-Id: I178594815e130a335ee2f23d420556cd7e1a14ce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080426Reviewed-by:
-
Toni Barzic authored
On certain devices, the user will have an option to swipe from the shelf on the last OOBE/first user run screen to end OOBE and enter the session. This adds a hook to login_screen interface that OOBE screen implementation can use to enable gesture detection on login shelf, and through which to get notified when the user swipes up. Also, implements upward fling detection for login shelf (done by login_shelf_gesture_controller, owned by shelf_widget) - when the gesture detection is active, login shelf shows a drag handle with a "contextual nudge" text above it. Updates DragHandle API to support color/opacity changes, so the drag handle appearance can be updated to match the login shelf controls on OOBE and login screen. BUG=976949 Change-Id: I670358c97de58c3f75ada9103df8098cc5074908 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2073541Reviewed-by:
-
Henrique Nakashima authored
CachedFeatureFlags deals with caching generic flags to SharedPrefs. Bug: 1012975 Change-Id: Ibe5912622a73e7a6b984b1dc3746dd775a0b711b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079341Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Henrique Nakashima <hnakashima@chromium.org> Cr-Commit-Position: refs/heads/master@{#745462}
-
Miguel Casas authored
This CL adds code for populating the necessary gfx::DisplayColorSpaces in CreateManagedDisplayInfo for supporting SDR and HDR target color spaces (depending on the monitor capabilities and the big hdr flag). It needs a sibling CL to allow AR/B30 FBs on CrOs crrev.com/c/2078655, Tested with that CL and by playing an HDR video: the primary framebuffer format in /sys/kernel/debug/dri/0//state correctly changes to XB30, whereas when there are not HDR quads in the BufferQueue, it's XR24. Bug: 958166 Change-Id: I94638436c079b03ef9f6200b77697b1d3da9337e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2072621Reviewed-by:
ccameron <ccameron@chromium.org> Commit-Queue: Miguel Casas <mcasas@chromium.org> Cr-Commit-Position: refs/heads/master@{#745461}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/bfa4dadb..6045fb83 Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: Ie15452d9c38f5bd0b006e9879d23c177969de8e4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079634Reviewed-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@{#745460}
-
Liviu Tinta authored
When there is text that overflows an input element, the scroll event is not fired when the text scrolls into view. The input element never receives the scroll event from the user agent shadow DOM internal editor element. The fix is to change the scroll event's target to the shadow host element when the event is generated. Bug: 989937 Change-Id: Iff4aeae6adb931d681a2ade72eb8032c5a23067c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2064818 Commit-Queue: Liviu Tinta <liviutinta@chromium.org> Reviewed-by:
Navid Zolghadr <nzolghadr@chromium.org> Reviewed-by:
David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#745459}
-
Henrique Nakashima authored
Bug: 1012975 Change-Id: Ic57e9d4aff392373c0ec9b5bf178b3e1701fea79 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079541Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Commit-Queue: Henrique Nakashima <hnakashima@chromium.org> Cr-Commit-Position: refs/heads/master@{#745458}
-
Juan Pablo de Lima authored
Change-Id: Ie9413eeba4879b97ac9493e7d4a7d7e1bb0a0ff8 Bug: b:132772120 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2047377 Commit-Queue: Juan Pablo De Lima <jpdelima@chromium.org> Reviewed-by:
Ben Wells <benwells@chromium.org> Reviewed-by:
Zachary Kuznia <zork@chromium.org> Auto-Submit: Juan Pablo De Lima <jpdelima@chromium.org> Cr-Commit-Position: refs/heads/master@{#745457}
-
Mark Cogan authored
Changes RecentTabsViewController to accept a Browser instead of separate WebStateList and BrowserState inputs. This will make future refactoring more straightforward. (There remains a great deal of work to do to fully refactor Recent Tabs to properly factor responsibilities into a mediator and coordinator). Bug: 845192 Change-Id: I068b0a343752dba602d2a2226cd0bcf327873446 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078452 Commit-Queue: Mark Cogan <marq@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/05f5e0b34ac8..3e5fe285a7ef git log 05f5e0b34ac8..3e5fe285a7ef --date=short --first-parent --format='%ad %ae %s' 2020-02-28 jonahr@google.com Add missing attribute to eglGetConfigAttrib Created with: gclient setdep -r src/third_party/swiftshader@3e5fe285a7ef 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: chromium:1015454 Tbr: swiftshader-team+autoroll@google.com Change-Id: Ie235d20c90ac5d35a4769566be6b2f1307a19a92 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080300Reviewed-by:
-
Peng Huang authored
Bug: None Change-Id: I78552786fa44682bea1b0e0f0d386aa582bc97f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2072926Reviewed-by:
Jonathan Backer <backer@chromium.org> Commit-Queue: Peng Huang <penghuang@chromium.org> Cr-Commit-Position: refs/heads/master@{#745454}
-
