- 15 Jan, 2021 40 commits
-
-
Tim Sergeant authored
This changes the existing --arc-force-cache-app-icons switch into the more generic --arc-generate-play-auto-install, to be used by developers who want to generate new Play Auto Install rosters. The value of this new switch is also passed through to ARC as a system property, where it can be used to enable behavior inside ARC code. At the moment, this is used to force web app APKs to be visible in the app list. The existing switch (--arc-force-cache-app-icons) is not used for anything other than PAI generation, and can be safely renamed. BUG=b:177035416 TEST=Verify `adb shell getprop ro.boot.arc_generate_pai` prints `1` when flag is set. Change-Id: I5f626a36ad40a8ad35956e888dccbbbdb27dabaa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626610 Commit-Queue: Tim Sergeant <tsergeant@chromium.org> Commit-Queue: Dominick Ng <dominickn@chromium.org> Auto-Submit: Tim Sergeant <tsergeant@chromium.org> Reviewed-by:Dominick Ng <dominickn@chromium.org> Reviewed-by:
Yusuke Sato <yusukes@chromium.org> Reviewed-by:
Josh Horwich <jhorwich@chromium.org> Cr-Commit-Position: refs/heads/master@{#843950}
-
Koji Ishii authored
This patch removes |LayoutNGFragmentItem| runtime flag and |FragmentItem| feature. These flags are already on by default in stable. Bug: 1154531 Change-Id: I68bdd1e2cac5a32c69eba6d5cbff26b798ddab63 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2629331 Commit-Queue: Kent Tamura <tkent@chromium.org> Auto-Submit: Koji Ishii <kojii@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#843949}
-
Yuta Hijikata authored
This is a mechanical change adding BUILDFLAG(IS_CHROMEOS_LACROS) to defined(OS_LINUX) to ensure switching lacros' target_os from linux to chromeos does not affect the lacros binary. More detail on http://go/lacros-macros. Bug: 1052397 Change-Id: Ia047bcc761acac4773b8d62930771e89cb6d8c09 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628870 Commit-Queue: Yuta Hijikata <ythjkt@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#843948}
-
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/goldctl-mac-chromium-autoroll Please CC bsheedy@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: bsheedy@chromium.org Change-Id: I5dd6f36473a83bc37b9f49e4c32558313fce09bb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631472Reviewed-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@{#843947}
-
Jérémie Boulic authored
In //ui/file_manager/file_manager/foreground/js/: - crostini_controller.js - gear_menu_controller.js Bug: 1133186 Change-Id: Ie078a26ec4d4fd4b73f780061483e2c62600bab7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631387Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Commit-Queue: Jeremie Boulic <jboulic@chromium.org> Cr-Commit-Position: refs/heads/master@{#843946}
-
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/goldctl-linux-chromium-autoroll Please CC bsheedy@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: bsheedy@chromium.org Change-Id: I4727ced0f682072d613cf2bd1256208bb19149c8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631219Reviewed-by:
-
chrome://syncfs-internalsdpapad authored
In the process, removed flattenhtml=true to stop inlining main.css, and serving it from its own URL instead. Similarly for other <include> flags in main.html. Bug: 1132403,1152343 Change-Id: I6c367dd5361111124db4d2592fac67582c7db740 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2629108 Auto-Submit: dpapad <dpapad@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#843944}
-
Richard Chui authored
Add in a new settings button on the capture bar that is used to toggle a settings bar. This bar will start off only holding one setting, to toggle audio recording in video capture. Settings for the audio recording flag will persist between sessions. Bug: 1145273 Test: manual, added test Change-Id: I2ffbd3ac2971254c9c2227a42c64f511793ce795 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2606118 Commit-Queue: Richard Chui <richui@chromium.org> Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Reviewed-by:
Sammie Quon <sammiequon@chromium.org> Cr-Commit-Position: refs/heads/master@{#843943}
-
Yoshifumi Inoue authored
This patch changes |NGInlineCursor::PositionForPointInInlineBox()| to ignore pseudo element and layout generated text, e.g. ellipsis, and style generated text, "content" in ::before/::after, to handle clicking right of content of ::after correctly. Before this patch, |closest_child_before| (point) holds fragment item for value of CSS "content" in |PositionForPointInInlineBox()|, then |PositionForPointInInlineBox()| returns null position because style generated text is not DOM position. After this patch, |closest_child_because| (point) holds fragment item for last layout object having non-null |GetNode()| before pseudo element ::after. Bug: 1164974 Change-Id: Iaba2f0807c345b13463b956e009b730449121096 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627242 Commit-Queue: Koji Ishii <kojii@chromium.org> Auto-Submit: Yoshifumi Inoue <yosin@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#843942}
-
Jérémie Boulic authored
In //ui/file_manager/file_manager/foreground/js/: - file_manager_commands.js - file_manager_commands_unittest.m.js Import cr.ui.Command as CrUiCommand to avoid name conflict with Command class defined in file_manager_commands.js Bug: 1133186 Change-Id: Iae1c3d0cd6ef889293c01a3239c98289c2d16257 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2629150 Commit-Queue: Jeremie Boulic <jboulic@chromium.org> Commit-Queue: Luciano Pacheco <lucmult@chromium.org> Reviewed-by:
-
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/goldctl-win-chromium-autoroll Please CC bsheedy@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: bsheedy@chromium.org Change-Id: I404302e4ab6c80932296491e347edab2b20c7d57 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631909Reviewed-by:
-
Jiewei Qian authored
This CL implements a new LaunchSystemWebAppAsync API, which is for other chrome components to launch a SWA safely. This new API should be used for SWA launches. The new API uses AppService to record metrics, handle disabled apps, etc. The old LaunchSWA is deprecated (its logic now becomes LaunchSWAImpl). LaunchSWAImpl is publicly declared because certain browser tests need to know the browser that hosts the SWA. It shouldn't be used to launch the App (other than LaunchSWA and Web app implementations). Subsequent CLs will attempt to migrate these browsertests to work with the new API. Bug: 1154540 Change-Id: I648a3b0404067ba460f0174e975fae44b3a0001a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2592270Reviewed-by:
James Cook <jamescook@chromium.org> Reviewed-by:
Nancy Wang <nancylingwang@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Giovanni Ortuño Urquidi <ortuno@chromium.org> Commit-Queue: Jiewei Qian <qjw@chromium.org> Cr-Commit-Position: refs/heads/master@{#843939}
-
Anastasia Helfinstein authored
Per the bug filed by our UX designer, change the colors of the Switch Access focus rings. Note that these colors do not change, regardless of whether the device is in dark or light mode. Bug: 1152610 Change-Id: I4884b30d8a8cddaf3f0da3fb52276587a5ec8ef2 AX-Relnotes: Changes the colors of the Switch Access focus rings. Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623170 Commit-Queue: Anastasia Helfinstein <anastasi@google.com> Reviewed-by:
Josiah Krutz <josiahk@google.com> Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/c07ef602741b..50c82f42e33f 2021-01-14 geofflang@google.com Don't index into SystemInfo gpus if it's empty. 2021-01-14 timvp@google.com Tests: Add Magic Tile 3 trace If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC timvp@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: chromium:1166338 Tbr: timvp@google.com Test: Test: angle_perftests --gtest_filter=TracePerfTest.Run/*magic_tiles_3* Change-Id: I805c3ca6c3c27145654417abc6c466e057e2f0c8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631410Reviewed-by:
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=govind@chromium.org Change-Id: Ic0f32e8a2f23df7f7a194a19af8f2104ea7f7bc4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632285Reviewed-by:
Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#843936}
-
Kuo Jen Wei authored
The calculation of default window size is based on fixing width to 764px in all preview aspect ratio cases(3:4, 4:3, 9:16, 16:9) and deriving height from that fixed width so that after preserve space for left, right, bottom icons(--xxx-line*2), the |#preview-box| can fit in preview aspect ratio as close as possible. After these, the new default window size under different preview aspect ratio will be: 3:4 -> 764x888; 4:3 -> 764x552; 9:16 -> 764x1144; 16:9 -> 764x444. Also change the minimal window width x height to 486 x 444 accordingly. Bug: b/175324385 Test: Manually verify default window size under 3:4, 4:3, 9:16, 16:9 preview. Test: tast run <DUT> "camera.CCA*" Change-Id: Id77a4843cb264fbaecb839b6ab053778017a6d1e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632105 Commit-Queue: Inker Kuo <inker@chromium.org> Commit-Queue: Shik Chen <shik@chromium.org> Auto-Submit: Inker Kuo <inker@chromium.org> Reviewed-by:
Shik Chen <shik@chromium.org> Cr-Commit-Position: refs/heads/master@{#843935}
-
Michael Bai authored
This reverts commit bdb8bac7. Reason for revert: Disabled the tests on x86 emulates, all tests should pass now. Original change's description: > Revert "Autofill: Add fieldtrail testing for AndroidAutofillQueryServerFieldTypes" > > This reverts commit 7452904e. > > Reason for revert: AwAutofillTest failures, see https://ci.chromium.org/ui/p/chromium/builders/ci/android-pie-x86-rel/3610/overview > > Original change's description: > > Autofill: Add fieldtrail testing for AndroidAutofillQueryServerFieldTypes > > > > Bug: 1151542 > > Change-Id: I25545f36d588ca926ce1de9514ae919f3f441a64 > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628040 > > Commit-Queue: Weilun Shi <sweilun@chromium.org> > > Reviewed-by: Weilun Shi <sweilun@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#843427} > > TBR=michaelbai@chromium.org,sweilun@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com > > Change-Id: Id31bb7d9a0b420315d729b802c6634e5e9c59e71 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: 1151542 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2629971 > Reviewed-by: Sky Malice <skym@chromium.org> > Commit-Queue: Sky Malice <skym@chromium.org> > Cr-Commit-Position: refs/heads/master@{#843702} TBR=michaelbai@chromium.org,skym@chromium.org,sweilun@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com # Not skipping CQ checks because this is a reland. Bug: 1151542 Change-Id: I9b2d003be6aa41643ad6dd209f4e63a5be2158e4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631200Reviewed-by:
Michael Bai <michaelbai@chromium.org> Reviewed-by:
Sky Malice <skym@chromium.org> Commit-Queue: Michael Bai <michaelbai@chromium.org> Cr-Commit-Position: refs/heads/master@{#843934}
-
Gyuyoung Kim authored
The original CL has read default_encoding twice with a wrong value. Fix it. Bug: 1097943, 1166690 Change-Id: I50f2080d5b54893296202282855edfefa6742dc6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631705Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com> Cr-Commit-Position: refs/heads/master@{#843933}
-
Jeff Cyr authored
Add histograms to count the number enabled and disabled extensions that are not present in the Enhanced Safe Browsing CRX allowlist per profile. The metrics are separated for all users versus Enhanced Safe Browsing users. Bug: 1153873 Change-Id: I84f167042fe63299b8da0669c9d117bf136090e1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627827 Commit-Queue: Jeff Cyr <jeffcyr@google.com> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#843932}
-
Michael Thiessen authored
Implements LaunchCause.MAIN_LAUNCHER_ICON, and adds tests to ensure that Activity transitions within Chrome don't trigger additional Launch Metrics. Bug: 1163961 Change-Id: Idc23d799693750965364ca95073c084a7d4bf3c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627764 Commit-Queue: Michael Thiessen <mthiesse@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Cr-Commit-Position: refs/heads/master@{#843931}
-
Luciano Pacheco authored
Bug: 1133186 Change-Id: I28133b243490606169f24c6085f938e2fed2b320 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2629147 Commit-Queue: Luciano Pacheco <lucmult@chromium.org> Reviewed-by:
Jeremie Boulic <jboulic@chromium.org> Cr-Commit-Position: refs/heads/master@{#843930}
-
Joe DeBlasio authored
This CL removes OWNERS for lookalikes for //components/security_interstitials/OWNERS. As the purview of lookalike owners grows (e.g. crrev.com/c/2628137 ), we should probably manage this a little more closely. The existing list also included a bunch of folks who know a lot about security interstitials, but should really chat with us before they change lookalikes stuff. It also updates the component for chrome/browser/lookalikes, since we have something more specific now. Change-Id: I1ee4fd4fc6d551a458cad36563d1f1ce445ce2b5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2630744 Commit-Queue: Mustafa Emre Acer <meacer@chromium.org> Reviewed-by:
Mustafa Emre Acer <meacer@chromium.org> Cr-Commit-Position: refs/heads/master@{#843929}
-
Caitlin Fischer authored
The experiment has launched. Bug: 1126640 Change-Id: I0aa59d57fc6110337f0cdc183814ac779a0f231f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631430Reviewed-by:
-
chromium-autoroll authored
Roll Chrome Win32 PGO profile from chrome-win32-master-1610647094-29bf0a5bdecd41fe52f35b6c0534103ef2302651.profdata to chrome-win32-master-1610657917-c5f7c43f5defa75543fc37f687b27a8203dbe683.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win32-chromium Please CC pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:win-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I74b8a56d14e75fe59bac21a407a107941f9c503b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631152Reviewed-by:
-
Brandon Wylie authored
If the Assistant consent flow is launched through SearchActivity, BottomSheetController isn't available. When this happens, the consent is aborted and retried next time. Bug: 1166119 Change-Id: Id177cce7644d2a6819adc3a11bba427f4a6bef90 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627967 Commit-Queue: Brandon Wylie <wylieb@chromium.org> Reviewed-by:
Josh Simmons <jds@google.com> Reviewed-by:
Filip Gorski <fgorski@chromium.org> Cr-Commit-Position: refs/heads/master@{#843926}
-
Caitlin Fischer authored
The server-side config indicates that the study has ended. Bug: 1126640 Change-Id: I9c2a1cae37f7c1a01e729959e7d77d2de783b67f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631429Reviewed-by:
Rakina Zata Amni <rakina@chromium.org> Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Cr-Commit-Position: refs/heads/master@{#843925}
-
Minoru Chikamune authored
Before this CL, WebViewPlugin uses per-thread CompositorTaskRunner. After this CL, WebViewPlugin will use per-ASG CompositorTaskRunner. Bug: 1105403 Change-Id: Ie5480f35818e3821799a20785f2bde5b4cb62d17 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626679 Commit-Queue: Minoru Chikamune <chikamune@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Alexander Timin <altimin@chromium.org> Cr-Commit-Position: refs/heads/master@{#843924}
-
Xinghui Lu authored
If the size of the allowlist is too small, the allowlist check will be skipped and Chrome will fall back to hash-based check. We'd like to know how often that happens. Metrics added: SafeBrowsing.RT.AllowlistSizeTooSmall Bug: 1164555 Change-Id: Ibd29ebfccab72eacdd0fb0b5a45f9a8ebc3eff05 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2622335 Commit-Queue: Xinghui Lu <xinghuilu@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Daniel Rubery <drubery@chromium.org> Cr-Commit-Position: refs/heads/master@{#843923}
-
Cattalyya Nuengsigkapian authored
- Support independent alt-tab mode selection for multi-profile. - Save alt-tab mode to active user prefs and restore after a re-login and a crash. Bug: 1157105 Test: Manual test, `ash_unittests --gtest_filter=MultiUserWindowCycleControllerTest.*` Change-Id: I59208f3f9726e776a10f0761c8aa431bf11b2080 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2616320Reviewed-by:
Xiaoqian Dai <xdai@chromium.org> Commit-Queue: Cattalyya Nuengsigkapian <cattalyya@chromium.org> Cr-Commit-Position: refs/heads/master@{#843922}
-
Xiaodan Zhu authored
This CL disables the tab navigation when there is a desk being dragged. Bug: 1154038 Change-Id: I744a28fc07c2a5005e940afb03741dbc22c88216 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2622952 Commit-Queue: Xiaodan Zhu <zxdan@chromium.org> Reviewed-by:
-
Evan Stade authored
Bug: none Change-Id: I9950f22a076ed0b5df43010c878d18372d5a6c69 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2629402Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Commit-Queue: Andrew Grieve <agrieve@chromium.org> Auto-Submit: Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#843920}
-
Hirokazu Honda authored
This reverts commit 276dd2ba. Reason for revert: The root cause of the synchronization is fixed. Removes this workaround. Original change's description: > media/gpu/test/VFValidator: Workaround the buffer synchronization problem on intel 3.18 > > There is a synchronization problem on the mapped buffer on intel > skylake devices. This is due to some missing 9165 patches in kernel > 3.18, and thus will be fixed if the kernel is upreved to 4.4 or > newer. This bug causes a decoded content validation failure in > video_decode_accelerator_tests. > This is a workaround to this bug; usleep() is added after the > buffer is mapped and before the frame validation if the kernel > version is 3.18 and the processor is Skylake. > > Bug: b:149808895 > Test: video_decode_accelerator_tests on sentry > Change-Id: Ib77ebe0b83834e4d91bc994cbe6912348862e021 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2371724 > Commit-Queue: Hirokazu Honda <hiroh@chromium.org> > Reviewed-by: Miguel Casas <mcasas@chromium.org> > Cr-Commit-Position: refs/heads/master@{#801614} TBR=mcasas@chromium.org,hiroh@chromium.org,andrescj@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: b:149808895 Change-Id: Id0f1bdcc486effef2c6d3fd64275d71051020028 Test: None Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631645Reviewed-by:
Hirokazu Honda <hiroh@chromium.org> Commit-Queue: Hirokazu Honda <hiroh@chromium.org> Cr-Commit-Position: refs/heads/master@{#843919}
-
Ken Rockot authored
This migrates all geolocation-api js-test web tests to the newer testharness, in preparation for further migration to internal WPT. They will move to WPT for the sake of modernization, but also primarily so that they can be HTTP tests that load ES6 modules for modern Mojo JS bindings. Bug: 1004256 Change-Id: I4c20c09fb3e10c8a35a3121f2e6df881e126d19f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628257Reviewed-by:
Reilly Grant <reillyg@chromium.org> Commit-Queue: Ken Rockot <rockot@google.com> Cr-Commit-Position: refs/heads/master@{#843918}
-
Richard Chui authored
CL #1 of 2 for chromevox announcements (second part is for tab navigation). Add the following announcements: -Entering capture mode -Exiting capture mode -Selecting the type (image/video) -Selecting the source (window/region/fullscreen) -Screenshot captured -Recording starting -Recording stopped Bug: 1140597 Test: manual Change-Id: I17c8d62de27507dfd4a9711201525fbd76b993cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2598056 Commit-Queue: Richard Chui <richui@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/7231b2e72311..b2af2da3481c 2021-01-15 bsheedy@chromium.org [Devil] Fix ArCore system path on Q If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/catapult-autoroll Please CC oysteine@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:chromeos-kevin-rel;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: oysteine@google.com Change-Id: If91c1ff43003c459faf80c4b54afd20556a6df73 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631586Reviewed-by:
-
Minoru Chikamune authored
Before this CL, ScrollableArea uses per-thread CompositorTaskRunner. After this CL, ScrollableArea will use per-ASG CompositorTaskRunner. Bug: 1105403 Change-Id: Iee3a7a9894918f5276d1110e50778e6523d2396f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626818 Commit-Queue: Minoru Chikamune <chikamune@chromium.org> Reviewed-by:
-
Taylor Bergquist authored
Adds a mechanism for customizing the overflow indicators to ScrollView to support this. Also note that the overflow indicator added here is just a starting point for iteration with UX, not a final design. Bug: 1116119 Change-Id: If6eae1e244f6bce65f10e10d964c2ae2af9ee86c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2611652 Commit-Queue: Taylor Bergquist <tbergquist@chromium.org> Reviewed-by:
Michael Wasserman <msw@chromium.org> Cr-Commit-Position: refs/heads/master@{#843914}
-
chromium-autoroll authored
Roll Chrome Linux PGO profile from chrome-linux-master-1610647094-405a32bcf15e5a84949640f99f84a5b9f61e2f2e.profdata to chrome-linux-master-1610668478-7d09cc584bcf96e72cb1514828da986e69ab213c.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-linux-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:linux-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: Ifb708c0149949bc5adf4a12566fda3eb650ad3fa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631785Reviewed-by:
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1610647094-3e6a9456ec2a4877d37636e99663c09557aba29f.profdata to chrome-mac-master-1610668478-7094d9e47d32a574227817d5f93a8aaa3dc9b368.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-mac-chromium Please CC pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:mac-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: Ia6540ce6ce0140b882460854ee99cae021153964 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631210Reviewed-by:
-
David Black authored
Previously a ui::Layer was directly owned which doesn't handle the case of layer recreation which is handled by ui::LayerOwner. Bug: 1166959 Change-Id: I92efce13e7a8a48423547cf134214d6b23b5c371 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631298Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Commit-Queue: David Black <dmblack@google.com> Cr-Commit-Position: refs/heads/master@{#843911}
-
