- 07 Nov, 2020 21 commits
-
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/16036cf206f1..56af9cbd3f35 2020-11-06 dawn-autoroll@skia-public.iam.gserviceaccount.com Roll Tint from 795bf4c71637 to cc2305dd9537 (1 revision) 2020-11-06 cwallez@chromium.org Use IsSubset in more places. 2020-11-06 cwallez@chromium.org SwapChainVK: Handle transform, imageCount, alphaMode. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/dawn-chromium-autoroll Please CC cwallez@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel Bug: None Tbr: cwallez@google.com Change-Id: I2f5bd59405839dd18d110ec2231b5c2436f4ab60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523809Reviewed-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@{#825134}
-
James Cook authored
Use the zcr_cursor_shapes_v1 Wayland protocol extension to allow the exo server to set the cursor. Use this for standard cursors (pointer, hand) and animated cursors (progress, wait). Bitmap cursors continue to use the existing code path. Introduce a test API for WaylandConnection so we can mock out the WaylandZcrCursorShapes object. In addition to the automated tests, I tested manually on a Pixelbook (eve). High DPI cursors are sharp. Accessibility cursors work fine, including large cursor and cursor coloring. The cursor size is correct for multi-monitor window drags from high DPI to low DPI monitors and vice versa. All CSS cursors listed on the MDN CSS cursors page look correct: https://developer.mozilla.org/en-US/docs/Web/CSS/cursor Bug: 1143790 Test: added to ui_base_unittests and ozone_unittests Change-Id: Ic46fc083a0ec662edf40b370572e907a2877c59a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516972 Auto-Submit: James Cook <jamescook@chromium.org> Reviewed-by:
Michael Wasserman <msw@chromium.org> Reviewed-by:
Henrique Ferreiro <hferreiro@igalia.com> Reviewed-by:
Maksim Sisov (GMT+2) <msisov@igalia.com> Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Antonio Gomes <tonikitoo@igalia.com> Commit-Queue: James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#825133}
-
Yicheng Li authored
Make these changes according to UI review: 1. Have both shadow and rouned corner. This is done by using views::BubbleBorder so that it looks closer to other such widgets, e.g. sharesheet. 2. Change primary text color to GoogleGrey900, secondary text color to GoogleGrey700. 3. Adjust vertical spacing after title, origin name prompt and PIN input field to match start screen spec. Bug: b:156258540, b:144861739 Change-Id: Ie84ed82d6fed17c63d7dec49a18fa75f42599e25 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523520Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Yicheng Li <yichengli@chromium.org> Cr-Commit-Position: refs/heads/master@{#825132}
-
Sam Maier authored
Bug: 1139446 Change-Id: Ief7f51ce5a22644712bc2edb5fe33eaec61215f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522913 Auto-Submit: Sam Maier <smaier@chromium.org> Commit-Queue: Mohamed Heikal <mheikal@chromium.org> Reviewed-by:
Mohamed Heikal <mheikal@chromium.org> Cr-Commit-Position: refs/heads/master@{#825131}
-
Xiaocheng Hu authored
Bug: 1061171 Change-Id: I73b37320278e207df81553762c82e774dd7cd950 NoTry: True Tbr: drubery@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523763Reviewed-by:
Xiaocheng Hu <xiaochengh@chromium.org> Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> Cr-Commit-Position: refs/heads/master@{#825130}
-
Michael Thiessen authored
Updates imports in chrome/android/javatests/ to use the base/ CriteriaHelper Bug: 1134178 Change-Id: I01b35928f432153c7b6b74f23cd2b50b6dc83720 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2518038 Auto-Submit: Michael Thiessen <mthiesse@chromium.org> Commit-Queue: Theresa <twellington@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Cr-Commit-Position: refs/heads/master@{#825129}
-
John Abd-El-Malek authored
Bug: 1144209 Change-Id: Icef2ca844b3c0fb4e2704253890760d0fe5f36bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523357Reviewed-by:
Evan Stade <estade@chromium.org> Commit-Queue: John Abd-El-Malek <jam@chromium.org> Cr-Commit-Position: refs/heads/master@{#825128}
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1604674173-719d34785101ea4ac0ebaa67a34ad987e0ccbedb.profdata to chrome-win64-master-1604685414-e1e235adb1c3aa909026ef65a3bd85555a33e659.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win64-chromium Please CC pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I2121efe65ab60c7f895a9d335fc8f088d8e76dbf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523629Reviewed-by:
-
Bo Majewski authored
Bug: 1113981 Change-Id: I72e6c09a8c5e142bb85a1cea995c546aacd7d075 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522800 Commit-Queue: Bo Majewski <majewski@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Cr-Commit-Position: refs/heads/master@{#825126}
-
Michael Hansen authored
This moves the "downloading" and "error" states for contacts download on the contact visibility dialog to be siblings with the zero state to match the visual hierarchy in the spec and updates their strings. Spec: https://docs.google.com/document/d/1s-KjC1mM4ZPYeYAO7oI8lXltS_1FaYYfMMnNDdbfRag Screenshots: https://screenshot.googleplex.com/3eFV48bA2vLoMYW.png https://screenshot.googleplex.com/7fGRnhpS5zECRuU.png Bug: b:168841167 Change-Id: I669866edd3c114bf34d5c1c77ddf89d02e1e909a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2519364 Commit-Queue: Michael Hansen <hansenmichael@google.com> Reviewed-by:
James Vecore <vecore@google.com> Cr-Commit-Position: refs/heads/master@{#825125}
-
Chris Thompson authored
Update the histogram definition for the SCT auditing report success histogram to "Security.SCTAuditing.OptIn.ReportSucceeded" (as actually emitted by the code). Change-Id: I1562cb2b5c1a9c08904b0249960d664af6a4b720 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522333 Commit-Queue: Chris Thompson <cthomp@chromium.org> Commit-Queue: Emily Stark <estark@chromium.org> Auto-Submit: Chris Thompson <cthomp@chromium.org> Reviewed-by:
Emily Stark <estark@chromium.org> Cr-Commit-Position: refs/heads/master@{#825124}
-
Brandon Wylie authored
We need to prompt users for their permission before using Assistant for voice search. This is the initial implementation of a bottom sheet dialog which prompts the user before a voice search is performed. mocks: https://www.figma.com/file/b1CT6jM3mj0MdBvgQicy4b dd: https://docs.google.com/document/d/1ZnmJUYFBEiIx8TjQPxD18e7NAeJa6yIBamAJyR-ggOk Bug: 1117271 Change-Id: Ic03d72aeda38d99b765a648f13d16112ce39a4c4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2512384 Commit-Queue: Brandon Wylie <wylieb@chromium.org> Reviewed-by:
Matthew Jones <mdjones@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Cr-Commit-Position: refs/heads/master@{#825123}
-
Gayane Petrosyan authored
Bug: None Change-Id: Ida58b3dcb40a53ad358f9bac4d0b620f2e3b9997 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2519273Reviewed-by:
Jesse Doherty <jwd@chromium.org> Reviewed-by:
Gayane Petrosyan <gayane@chromium.org> Reviewed-by:
Caitlin Fischer <caitlinfischer@google.com> Commit-Queue: Gayane Petrosyan <gayane@chromium.org> Cr-Commit-Position: refs/heads/master@{#825122}
-
Chromium WPT Sync authored
Using wpt-import in Chromium 7ba1e052. Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md Directory owners for changes in this CL: foolip@chromium.org, lpz@chromium.org, robertma@chromium.org: external/wpt/tools jsbell@chromium.org: external/wpt/encoding yhirano@chromium.org, mkwst@chromium.org, japhet@chromium.org: external/wpt/fetch NOAUTOREVERT=true TBR=robertma@google.com No-Export: true Cq-Include-Trybots: luci.chromium.try:linux-wpt-identity-fyi-rel,linux-wpt-payments-fyi-rel Change-Id: Ieeabf3c5b019e9ff838d8cec61eaee3a14e748cb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523493Reviewed-by:
WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#825121}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/1e9cf1a8e1bd..31623e15a8a0 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: I8d9713d7fbfc11570bd8668521a10a733cc4933d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523677Reviewed-by:
-
Xiaocheng Hu authored
Bug: 1143311 Change-Id: I131bb5b58f8f403d2752288c6e2c4a8ec11e15a7 NoTry: True Tbr: joedow@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523302Reviewed-by:
-
Robert Sesek authored
Bug: 1064652 Change-Id: Ib352eb91dd6fe8d883fbbfbc63d87378510c1b3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523571 Commit-Queue: Nico Weber <thakis@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#825118}
-
Sammie Quon authored
ShouldApplyDimming was skipped in clamshell mode; instead overview itself would set opacity filter. This patch enables ShouldApplyDimming (now ShouldApplyColorFilter) for overview clamshell mode and mixes the shield layer color, which has opacity built in for both tablet and clamshell mode to match new spec. I also noticed we always blend with kDarken. So on real dark wallpapers, light mode black text will still be an issue. But I did notify UX and I think that is an overall wallpaper issue. With this change, WallpaperProperty opacity is now always 1.f, so we can remove WallpaperProperty in a follow up as it only contains blur now. Test: manual Bug: 1145342 Change-Id: Iea321602f577aa848722c6bb665a3de49aff129f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521852 Commit-Queue: Sammie Quon <sammiequon@chromium.org> Reviewed-by:
Xiaoqian Dai <xdai@chromium.org> Reviewed-by:
Min Chen <minch@chromium.org> Cr-Commit-Position: refs/heads/master@{#825117}
-
Xiaocheng Hu authored
Bug: 1146627 Change-Id: If63388da004cdd40d7cd3b777886893e9bf1facf NoTry: True Tbr: jdonnelly@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523760Reviewed-by:
-
rajendrant authored
This CL refactors the existing subresource redirect code to make the robots rules and login based image compression implementation easy. * Separate out the url loader throttle that does redirect and timeout handling from the public image hints decider logic. The robots decider can be subclassed and used. * Make public image hints agent as renderframeobserver. This reduces cluttter in ResourceLoadingHintsAgent. The upcoming robots checker agent could also observe renderframeobserver directly. No change in behavior is expected. Change-Id: Ic555a4402016a645b8820fa87dd5157c7112fb71 Bug: 1144836 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2514068 Commit-Queue: rajendrant <rajendrant@chromium.org> Reviewed-by:
Michael Crouse <mcrouse@chromium.org> Cr-Commit-Position: refs/heads/master@{#825115}
-
Kevin McNee authored
Currently, using --enable-blink-features=Portals or --enable-blink-test-features causes renderer kills because the renderer enables portals for itself with runtime_enabled_features, however the browser only considers the blink::features::kPortals feature. We have the renderer respect the value of blink::features::kPortals. We now ignore --enable-blink-features=Portals when the browser does not have portals enabled and only set portals' experimental/test status if the blink::features::kPortals default allows for it. Since now portals are not exposed for the blink testing config for web tests, we remove their interface listing expectations. Bug: None Change-Id: I02fe241e2ddd17d86eda896b2b2fa21c36bcb682 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2518427 Commit-Queue: Kevin McNee <mcnee@chromium.org> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#825114}
-
- 06 Nov, 2020 19 commits
-
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/876499b090ec..18bf81a444b8 2020-11-06 jalyn@microsoft.com Settings: Allow keyboard shortcut link to wrap 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:1142367,chromium:1144116 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I7a1154e5c2964c6d7e9f35b36050d22c942abdde Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523420Reviewed-by:
-
Stephen Chenney authored
The check for same-origin for image files with EXIF in canvas drawImage was crashing for SVG images because their security origin status is not available until the image has loaded. Change things to not check SVG images for canvas drawImage, which is safe because the image will be checked when drawing the SVG itself. Add a test for various uses of images in SVG. Bug: 1141412 Change-Id: I4bd39b6d10afec4c4134b24609aa02c53359361b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521049Reviewed-by:
Yi Xu <yiyix@chromium.org> Reviewed-by:
Fredrik Söderquist <fs@opera.com> Commit-Queue: Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#825112}
-
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-aemu-chromium-autoroll Please CC chrome-fuchsia-gardener@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 Tbr: chrome-fuchsia-gardener@grotations.appspotmail.com Change-Id: I14ae4ec8937729a260eb79d7b49f5ccce26850a4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523419Reviewed-by:
-
Side Yilmaz authored
Incognito profile is destroyed by IncognitoTabModelImpl, if there is no tab closing at that moment. However, setting mCountOfAddingOrClosingTabs was missing for |closeAllTabs|, |closeMultipleTabs| and |removeTab| functions. This CL adds this logic to the class. Bug: 1142341, 1143189 Change-Id: I8192ad2099cb26c822d9249bb9409a56cb1250e4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2517532 Commit-Queue: Side YILMAZ <sideyilmaz@chromium.org> Reviewed-by:
Mei Liang <meiliang@chromium.org> Cr-Commit-Position: refs/heads/master@{#825110}
-
Xiaocheng Hu authored
Bug: 1146302 Change-Id: I5b3535c0fb3676312670a41209dbff67fde3e6e1 NoTry: True Tbr: joedow@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523301Reviewed-by:
-
Kenneth Russell authored
Preliminary testing indicates that sufficient fixes for earlier graphics driver bugs are present on this Android version, so allow WebGL 2.0 to run on these configurations. Bug: 1042214 Change-Id: I2d308b500b5624a53bfaeee5455181d1b2efccc2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2519887Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Commit-Queue: Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#825108}
-
Xinghui Lu authored
Log Safe Browsing opt-in metrics every 24 hours or at startup, if the last logging time is more than 24 hours ago. Write the metrics last logging time in pref, so the browser knows the last logging time on startup. The old opt-in metrics are still in use, so they remain the same. If the new daily metrics work well, we can deprecate the old ones. Metrics added: SafeBrowsing.Pref.Daily.Extended SafeBrowsing.Pref.Daily.SafeBrowsingState Bug: 1099869 Change-Id: I797a9a2484f59f9e21f5295a3f665944282b671f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2520171Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Reviewed-by:
Daniel Rubery <drubery@chromium.org> Commit-Queue: Xinghui Lu <xinghuilu@chromium.org> Cr-Commit-Position: refs/heads/master@{#825107}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/df58b821059d..e9f2071d125a 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 xiaochengh@google.com,tinazwang@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: xiaochengh@google.com,tinazwang@google.com Change-Id: I9f7ff76e5e6e7ad568fbb4dd0e3e26a732d569b2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523631Reviewed-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@{#825106}
-
Xiaocheng Hu authored
Bug: 1145612 Change-Id: Ib47f3d9bb291e08328b5d2dc1fa9e65126433ef7 NoTry: True Tbr: dmazzoni@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523757Reviewed-by:
-
Frank Liberato authored
Change-Id: I3cc29edd1f2258348b07537909f86e4c9a1b69cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521168 Commit-Queue: Frank Liberato <liberato@chromium.org> Auto-Submit: Frank Liberato <liberato@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#825104}
-
David Van Cleve authored
Right now, a lot of the postcondition verification for the Trust Tokens browser tests covering request signing takes place in the test helper, network::test::TrustTokenRequestHandler. In particular, right now, the helper provides an interface that allows callers to extract the last signing request verification error, if any. This has a couple problems: 1. Callers can't distinguish cases where no signing request arrived in the handler from cases where a signing request was successfully processed 2. All of the postcondition checking takes place in the handler, so it's hard to modify the postcondition checking to reflect changes in test expectations. Right now, we do this by passing an options struct to the handler, but it woul be more readable if we could express the expectations in real time, after sending the request, in the main browser test code. This CL refactors the test handler to instead allow callers to extract a representation of the most recently received signed request, if any. Callers can then check postconditions directly against this data, using trust_tokens/test/ helper methods. Fixed: 1126276 Change-Id: Ic6d9f403c2175cc5bb7c2a3ff59ffc575252cda3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2520200 Commit-Queue: David Van Cleve <davidvc@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Reviewed-by:
Charlie Harrison <csharrison@chromium.org> Cr-Commit-Position: refs/heads/master@{#825103}
-
minch authored
Bug: 1145699 Change-Id: I5b9db0b6776b26ede2687cbc2d5d63702eb0bc70 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521831Reviewed-by:
-
David Schinazi authored
This CL is part of our investigation into internal bug b/167728915. It adds a workaround in our parsing code to ensure that we ignore obsolete Finch configs. This CL also removes the simulated crash that allowed us to demonstrate that obsolete Finch configs were being seen in the wild. We no longer need these simulated crashes because they didn't provide any useful information beyond proving that there is indeed an issue with Finch. R=nharper@chromium.org Bug: 1144986 Change-Id: I7b0d462d12e93018c05ae28467f6990efb8fa1b2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2520418 Commit-Queue: David Schinazi <dschinazi@chromium.org> Reviewed-by:
Nick Harper <nharper@chromium.org> Auto-Submit: David Schinazi <dschinazi@chromium.org> Cr-Commit-Position: refs/heads/master@{#825101}
-
Tom Anderson authored
This is a partial revert of 7e489781. It turns out removing GLX is not necessary since it's already dynamically loaded. Using GLX allows us to remove dependencies on dri2, present, and xf86vidmode. R=sunnyps Bug: 1066670 Change-Id: I44b79b06de76a043f38dfd9270eee980134a7816 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523661Reviewed-by:
Sunny Sachanandani <sunnyps@chromium.org> Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org> Auto-Submit: Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/master@{#825100}
-
Chris Lu authored
Bug: 1138603 Change-Id: I3872769228ae5d5f6088cbd662b76546a318cb4c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2518269 Auto-Submit: Chris Lu <thegreenfrog@chromium.org> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Commit-Queue: Chris Lu <thegreenfrog@chromium.org> Cr-Commit-Position: refs/heads/master@{#825099}
-
Yulun Wu authored
Dark/Classic shelf use light inkdrop highlights. Bug: 1144136 Change-Id: I5690f73458c623fc82e7f891bfb3bdda963cb386 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2515200Reviewed-by:
Yulun Wu <yulunwu@chromium.org> Commit-Queue: Yulun Wu <yulunwu@chromium.org> Cr-Commit-Position: refs/heads/master@{#825098}
-
Darwin Huang authored
Also, add some comments... Bug: 1145787 Change-Id: I64fc705e671f5534d523d2b9c1ec1d7f01b64c1b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522575 Commit-Queue: Darwin Huang <huangdarwin@chromium.org> Reviewed-by:
Jarryd Goodman <jarrydg@chromium.org> Auto-Submit: Darwin Huang <huangdarwin@chromium.org> Cr-Commit-Position: refs/heads/master@{#825097}
-
Nate Fischer authored
No change to production logic. This adds a tool for generating enums.xml from ProductionSupportedFlagList and uses it to update enums.xml. This also adds a new PRESUBMIT check run the script every time the flag list is modified to remind developers to update enums.xml. This makes some minor lint fixes to android_webview/tools/* which were blocking upload. Test: vpython android_webview/tools/generate_flag_labels_test.py Test: out/Desktop/unit_tests --gtest_filter=AboutFlagsHistogramTest.* Change-Id: Ib427e2bf1ff462766ec5671736cfc9be57db8528 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521468 Commit-Queue: Nate Fischer <ntfschr@chromium.org> Reviewed-by:
Richard Coles <torne@chromium.org> Cr-Commit-Position: refs/heads/master@{#825096}
-
Jeroen Dhollander authored
This forces us to remove all dependencies on //chromeos/services/assistant, which in turn will allow us to move the implementation to a different mojom service. I ended up choosing a pretty simple cut where I introduce a new |cros_libassistant| target that contains the interfaces that are currently used both by |AssistantProxy| and the Assistant service. Things in this target will eventually have to move over to the new mojom service. Bug: b/171748795 Test: compiled & deployed Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Change-Id: Idb58d45c59b97f3d906fa7e2e148198ec25813a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2518213Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Commit-Queue: Jeroen Dhollander <jeroendh@chromium.org> Cr-Commit-Position: refs/heads/master@{#825095}
-
