- 27 Jul, 2020 40 commits
-
-
Katie D authored
In crrev.com/c/2303458 a bug was introduced which added sub-groupings within the Switch Access menu. This seems to be related to the change to use an EventHandler in switch_access.js which always acts on event.target, whereas previously it sometimes did an action on one of the children of event.target. Although I don't fully understand the logic, reverting this one file from that change does restore the correct behavior. AX-Relnotes: N/A Bug: 1109355 Change-Id: Id7feb1a2474e06a64d0b371beade6e33800d382c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318315 Commit-Queue: Anastasia Helfinstein <anastasi@google.com> Reviewed-by:
Anastasia Helfinstein <anastasi@google.com> Cr-Commit-Position: refs/heads/master@{#792027}
-
John Lee authored
Bug: 1084620 Change-Id: I90e303699df432f20ebb81d47587bff47419feb0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317824Reviewed-by:
Lei Zhang <thestig@chromium.org> Reviewed-by:
dpapad <dpapad@chromium.org> Commit-Queue: John Lee <johntlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#792026}
-
rbpotter authored
Make the PluginProxy follow the standard BrowserProxy pattern (i.e. define an interface and implement separately), and use addSingletonGetter(). This allows for better type coverage when using the stub in tests. Add closure compilation for: header_test invalid_settings_browsertest test_plugin_proxy (renamed from plugin_stub) Bug: 1000989 Change-Id: I6e0cf064a6789b2cdc87b617fd0fdd58d5039f48 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317165 Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Reviewed-by:
John Lee <johntlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#792025}
-
Miguel Casas authored
crrev.com/c/2276516 added kUseHDRTransferFunction to Chrome's list of flags upon restart. This is only needed for features that re disabled by default IIUC, and crrev.com/c/2317569 enabled that feature; adding a default-enabled-feature there breaks a few Guest mode browser_tests. This CL removes that propagation. Bug: 958166 Change-Id: Ic27fafb3ad88ca8ae3626f1c3ddf34bdcc6192b7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2321069Reviewed-by:
James Cook <jamescook@chromium.org> Commit-Queue: Miguel Casas <mcasas@chromium.org> Cr-Commit-Position: refs/heads/master@{#792024}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/2f54b1a2..ee995bcb 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,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I7829f99dde2db01cd29ed1d6b8c0a1fb8005f545 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2321148Reviewed-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@{#792023}
-
Ken Rockot authored
This eliminates the remaining .typemap files for Blink-variant bindings in favor of direct GN target configuration. This also effectively removes support for use for .typemap files for the Blink variant. Bug: 1059389 Change-Id: I4683dbd472151e6f3451476b7b04182a6048a31b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315446 Commit-Queue: Ken Rockot <rockot@google.com> Reviewed-by:
Clark DuVall <cduvall@chromium.org> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Reviewed-by:
Tom Sepez <tsepez@chromium.org> Cr-Commit-Position: refs/heads/master@{#792022}
-
Ken Rockot authored
This reverts commit e6d6e338. Reason for revert: Speculatively blaming for https://crbug.com/1110100 Will reland if the revert is ineffective. Original change's description: > PRESUBMIT.py: Replace checkteamtags with DIR_METADATA checks. > > checkteamtags is no longer necessary. > - Add a check to validate DIR_METADATA files. > This obviates the need fo checkteamtags, as `dirmd` validates metadata in > OWNERS files, and we no longer need to enforce a unique team email for all > (component, OS) pair. > - Add a check to enforce that OWNERS files contain no metadata if a > DIR_METADATA file is present in the same directory. > > Bug: 1102997 > Change-Id: I661f7a1958824e7d20642d65534c2502d1a050e2 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317838 > Reviewed-by: Nodir Turakulov <nodir@chromium.org> > Reviewed-by: Dirk Pranke <dpranke@google.com> > Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> > Cr-Commit-Position: refs/heads/master@{#791884} TBR=dpranke@google.com,nodir@chromium.org,ehmaldonado@chromium.org Change-Id: I483d4b50b18d1a901297801a524d79258ae9066c No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1102997 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2321246Reviewed-by:
Ken Rockot <rockot@google.com> Commit-Queue: Ken Rockot <rockot@google.com> Cr-Commit-Position: refs/heads/master@{#792021}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/1d5171690554..5408a4532748 2020-07-27 chrome-bot@chromium.org Update config settings by config-updater. 2020-07-27 rkolchmeyer@google.com chromeos-config: Clean up some lakitu builders 2020-07-25 vapier@chromium.org portage_utils: add sysroot support to all portageq helpers 2020-07-24 mmortensen@google.com cros_sdk_lib: Extract method for fuser/lsof/ps diagnostics. 2020-07-24 yueherngl@google.com shadowkeep: disable hw_tests for now 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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:chromeos-betty-pi-arc-chrome;luci.chromium.try:chromeos-kevin-rel Tbr: chrome-os-gardeners@google.com Change-Id: I70dd999b8426483ec6dd88a87818d8ccc8dfcd1e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318733 Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Reviewed-by:
chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#792020}
-
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/perfetto-trace-processor-linux-chromium Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Tbr: perfetto-bugs@google.com Change-Id: I3656b0b9da638ab465448b886e867442d49c22e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2320990Reviewed-by:
-
Corentin Wallez authored
Use "blocklist" for the concept of block certain GPU features based on the system's configuration. Bug: chromium:1101491 Change-Id: Idaeee39cb167705bb89327e70577eb3c7ca73dec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2302151Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org> Cr-Commit-Position: refs/heads/master@{#792018}
-
Kevin Ellis authored
A regression was introduced in: https://chromium-review.googlesource.com/c/chromium/src/+/2252642 The base computed style could get updated even when it should not be cached. A style that is computed in a hypothetical scenario (using non-default parent or matching rules) should not be cached. With this patch, the style resolver maintains a flag to block the update if the style should not be cached. Bug: 1100873,1109045 Change-Id: Iaca30b6b0043a8ca750624dbc2d557ef232f92ca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2310969 Commit-Queue: Kevin Ellis <kevers@chromium.org> Reviewed-by:
Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#792017}
-
Theresa Wellington authored
TBR=rouslan@chromium.org BUG=1108241 Change-Id: I2f7a02c87f28c17647a0e504d6888052544b0f58 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2319335Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Theresa <twellington@chromium.org> Cr-Commit-Position: refs/heads/master@{#792016}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/4fd830acab6f..0bb26390604e 2020-07-27 landrey@webrtc.org Add heavy metrics tests for default VQ analyzer 2020-07-27 saza@webrtc.org AEC3: Fix render delay buffer alignment issue at call start 2020-07-27 philipel@webrtc.org Revert "Removed VideoDecoderFactory::LegacyCreateVideoDecoder and VideoReceiveStream::Config::stream_id." 2020-07-27 philipel@webrtc.org Removed VideoDecoderFactory::LegacyCreateVideoDecoder and VideoReceiveStream::Config::stream_id. 2020-07-27 philipel@webrtc.org Replace individual encoder/decoder factories with a single encoder/decoder factory in MultiCodecReceiveTests. 2020-07-27 danilchap@webrtc.org Ignore RTPFragmentationHeader when rewriting H264 SPS 2020-07-27 titovartem@webrtc.org Add support for multiple peers in SingleProcessEncodedImageDataInjector If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: If91be7fe601202f7cb4dafa1d833db9bcacdf445 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2321013Reviewed-by:
-
Michael Thiessen authored
waitForIdleSync can easily block forever in the case of a running animation or similar, and is used throughout our test infrastructure. This can lead to shard timeouts, especially with batched tests that have longer timeouts, making issues hard to debug. This change limits how long we can wait for the MessageQueue to be idle. Bug: 1108566 Change-Id: I449da5e71a49bee3513fd47ca659662f16f41d3e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314989 Commit-Queue: Michael Thiessen <mthiesse@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Cr-Commit-Position: refs/heads/master@{#792014}
-
Sammie Quon authored
Bubbles are anchored to the app menu button by default. In immersive not revealed mode, the app menu button is drawn somewhere offscreen. To avoid the bubble being placed partially offscreen, return a null anchor view. This will cause the bubble to be drawn in the top left corner, just like regular fullscreen. Test: browser_tests ImmersiveModeControllerAshWebAppBrowserTest.PermissionsBubbleAnchor Change-Id: I1aeaea0da64d3a301a898ae5e7778d123eb2e433 Fixed: 1087143 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2311896Reviewed-by:
Peter Boström <pbos@chromium.org> Reviewed-by:
Wei Li <weili@chromium.org> Commit-Queue: Sammie Quon <sammiequon@chromium.org> Cr-Commit-Position: refs/heads/master@{#792013}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/e94b4e1b49a3..66d19211aa8f 2020-07-27 jmbetancourt@google.com remove skar_java from skia android projects If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC borenet@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: None Tbr: borenet@google.com Change-Id: I8c17082f3f57fc88a4d5260a14a100a628cbdbf2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318734Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/0bf389ba6cb5..478f7fed94ec 2020-07-27 zhin@chromium.org Import changes to wast mode in CodeMirror 2020-07-27 jacktfranklin@chromium.org Component bridges: support overriding fields 2020-07-27 aerotwist@chromium.org Migrate console_counters to devtools_entrypoint 2020-07-27 sigurds@chromium.org [bandaid] Let issue banner scroll out of view in console 2020-07-27 janscheffler@chromium.org Migrate `front_end/javascript_metadata` to `devtools_entrypoint` 2020-07-27 janscheffler@chromium.org Migrate `front_end/heap_snapshot_model` to `devtools_entrypoint` 2020-07-27 jacktfranklin@chromium.org Component bridges: support types that extend types 2020-07-27 aerotwist@chromium.org Migrate text_utils to devtools_entrypoint 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:1094596,chromium:1096481,chromium:1101738 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I2148a05d6b2835067ef6dbff7a0e470ca479a71c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318736Reviewed-by:
-
Chris Sharp authored
Currently this will just focus on getting product names referenced the same way in all policies. Change-Id: I53a2442c79f18f79c5c31d89c01e10c74a1e8e87 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2303528 Commit-Queue: Chris Sharp <csharp@chromium.org> Reviewed-by:
Owen Min <zmin@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Cr-Commit-Position: refs/heads/master@{#792010}
-
Daniel Murphy authored
This change adds MANIFEST_URL_CHANGED to InstallableStatusCodes, and adds support for InstallableManager reporting this error (as well as reporting when a navigation happens or when the renderer exists). Then it modifies the AppBannerManager class to listen for this result when it fetches the manifest or checks if a tab is installable. Finally, it modifies AppBannerManager to also listen for manifest url changes, and when the occur outside of calls to the InstallableManager (as these will be reported by the method above), it resets its state and restarts the request. Possible upgrades: * Add the rate limiter in AppBannerManager for retrying (or just count the number of retries & stop after X times) Design doc: https://docs.google.com/document/d/1HjN4JL9DCaTNuLj29ieqJEsexpfAzfJnoVrqY7SWvd8/edit R=dominickn@chromium.org Bug: 792299 Change-Id: Ia26c727d68d50ebee1966ed0e0318874e1843fe7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2300828 Commit-Queue: Daniel Murphy <dmurph@chromium.org> Auto-Submit: Daniel Murphy <dmurph@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#792009}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/f81afad16767..2ddb3ecf006e 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 mahmadi@google.com,adithyas@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: chromium:1085419,chromium:635745,chromium:912681 Tbr: mahmadi@google.com,adithyas@google.com Change-Id: I1de6964735d1b35c81966c4f7e96a78e4910ba10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2320202Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Reviewed-by:
Moe Ahmadi <mahmadi@chromium.org> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#792008}
-
Scott Violet authored
This moves all the favicon related functionality out of HistoryBackend into FaviconBackend. FaviconBackend is owned by HistoryBackend. FaviconBackend indirectly talks to HistoryBackend by way FaviconBackendDelegate. BUG=1076463 TEST=covered by tests Change-Id: If9927019b4539174d36daaf02597fcf1f1ad5c35 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314990Reviewed-by:
Peter Kotwicz <pkotwicz@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#792007}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/3b2cd31c7400..a681d12639f4 2020-07-27 caramelli.devel@gmail.com Add Wayland support for Vulkan WSI 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/+doc/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;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: I69dbd30ca9f70279eaa518975edc8471338b7e14 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318735Reviewed-by:
-
Adithya Srinivasan authored
Bug: 1108786 Change-Id: Ie498760184517698d3ef0346f996fa09a7c44960 No-Try: True Tbr: mahmadi@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2321305Reviewed-by:
Adithya Srinivasan <adithyas@chromium.org> Commit-Queue: Adithya Srinivasan <adithyas@chromium.org> Cr-Commit-Position: refs/heads/master@{#792005}
-
Marijn Kruisselbrink authored
This implements the changes from https://github.com/WICG/native-file-system/pull/200. Change-Id: I9702f9888c4f0fff2084143ac6077b8484dfce16 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2298296Reviewed-by:
Trent Apted <tapted@chromium.org> Reviewed-by:
Will Harris <wfh@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Cr-Commit-Position: refs/heads/master@{#792004}
-
Anders Hartvoll Ruud authored
This CL merges the function PseudoStyleForElementInternal with its non-internal wrapper PseudoStyleForElement. This is a step towards unifying the two very similar codepaths of StyleForElement and PseudoStyleForElement. There should be no behavior change. Change-Id: Iad0dfd59c8081de5ec68bbc5120e4cf28eee7954 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317960 Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by:
Oriol Brufau <obrufau@igalia.com> Cr-Commit-Position: refs/heads/master@{#792003}
-
Erik Jensen authored
This was originally postponed to make the branch deadline. Bug: 968640 Change-Id: I5066bd1f161e25428f872819bfc92bb16f4c7c35 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1668070 Commit-Queue: Erik Jensen <rkjnsn@chromium.org> Reviewed-by:
Yuwei Huang <yuweih@chromium.org> Reviewed-by:
Joe Downing <joedow@chromium.org> Cr-Commit-Position: refs/heads/master@{#792002}
-
Piotr Bialecki authored
Changes: - added one more recording including a tracking loss - added 3 test cases exercising anchors API - slightly tweaked XrTestFramework to allow for specifying timeouts explicitly so that the longest anchor test does not time out Bug: 992035 Change-Id: Ied3db9b459c72cbc1826d8a9e2e7edec90cbaae4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314663 Commit-Queue: Piotr Bialecki <bialpio@chromium.org> Reviewed-by:
Brian Sheedy <bsheedy@chromium.org> Reviewed-by:
Klaus Weidner <klausw@chromium.org> Cr-Commit-Position: refs/heads/master@{#792001}
-
Xiaocheng Hu authored
This patch adds two new @font-face descriptors to override the default font metrics. Though we don't have a stable spec at the moment, we land it behind a flag to make testing and discussion easier. Design doc: https://bit.ly/39qATQ4 Bug: 1098355 Change-Id: I2623a9385fe6e9fbfccf2e04cb5892f4aba37872 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316780Reviewed-by:
Koji Ishii <kojii@chromium.org> Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> Cr-Commit-Position: refs/heads/master@{#792000}
-
Sam Sebree authored
This change uses native_theme_base.cc to update the styling for the checkbox native controls in dark mode. Bug: 1099579 Change-Id: Iafb167aa2f24c304ac2292178beb4d6bdb24a451 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2311697Reviewed-by:
Mason Freed <masonfreed@chromium.org> Reviewed-by:
Yu Han <yuzhehan@chromium.org> Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Sam Sebree <sasebree@microsoft.com> Cr-Commit-Position: refs/heads/master@{#791999}
-
Ana Salazar authored
When the apps grid enters cardified state, all icons are scaled down 84%. We need to scale down the folder circle proportionally, to avoid clipping at the top edges. Bug: 1108644 Change-Id: I95b97d6d3db15c0313a92bbffbd5f70ffb4e071e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315094Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Commit-Queue: Ana Salazar <anasalazar@chromium.org> Cr-Commit-Position: refs/heads/master@{#791998}
-
Jia Li authored
Browser tests for the ML service is added to the Optimization Guide path where the service will be used first. Bug: 1108334 Change-Id: I5ec1845f9043546e89b49776e95ccdc391ea1e90 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2320748Reviewed-by:
Sophie Chang <sophiechang@chromium.org> Reviewed-by:
Michael Crouse <mcrouse@chromium.org> Commit-Queue: Jia Li <jiakl@google.com> Cr-Commit-Position: refs/heads/master@{#791997}
-
James Long authored
A new script has been added to count and optionally output cycles in package graphs. A limit to cycle size must be supplied, ideally around 5 or 6 to keep the script runtime low since the number of cycles is exponential. For more detailed usage, see `./count_cycles.py -h`. Bug: 1106484 Change-Id: I01923eaab24eb3c6641a23039c80f60a0bc0e212 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2303054 Commit-Queue: James Long <yjlong@google.com> Reviewed-by:
Samuel Huang <huangs@chromium.org> Reviewed-by:
Mohamed Heikal <mheikal@chromium.org> Cr-Commit-Position: refs/heads/master@{#791996}
-
Trent Begin authored
This is cleaning up uses of base::Unretained(this) in the cros_healthd service connection. There are cases where the service connection could be destroyed before the callback returns. Bug: chromium:1108065 Change-Id: I66639581e213cc088080de5ec407f06968b8559c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2311074 Commit-Queue: Trent Begin <tbegin@chromium.org> Reviewed-by:
Paul Moy <pmoy@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/heads/master@{#791995}
-
My Nguyen authored
Bug: 1000989 Change-Id: I7ae5d8279cb46866e28a4393d8cdc0d3ae21bcd0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315901Reviewed-by:
-
Maksim Sisov authored
Removes unnecessary defines, chooses correct path based on OzonePlatform feature usage. ----- PS: Please note that this is a temp solution that will help to choose between ozone and non-ozone X11 build. The switch that will be used to choose the path is --enable-features=UseOzonePlatform. Once non-Ozone X11 path is removed (hopefully by Q1 2021 depending on how th finch trial goes), the wrapper will be removed. Please also note that it's impossible to build use_x11 && use_ozone without some hacks in PlatformCursor code. The changes to that are on their way to upstream. ---- Bug: 1085700 Change-Id: I5fced0993b55d0dedd9661d9845ff3b347b7bf4e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315885Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Maksim Sisov (GMT+3) <msisov@igalia.com> Cr-Commit-Position: refs/heads/master@{#791993}
-
James Cook authored
Select file dialogs are implemented in ash-chrome via SelectFileDialogExtension, which requires an aura::Window owning window for the dialog. Top-level windows in lacros-chrome are represented in ash-chrome via ShellSurface objects. Pass an ID for the shell surface over mojo from lacros-chrome to ash-chrome and use it for window parenting. The ID is a string: "org.chromium.lacros.<unguessable-token>", e.g. "org.chromium.lacros.8B93BD96131616984961C7790B5E9A62". Lacros creates an ID for each WaylandToplevelWindow and uses xdg_shell's set_app_id method to set it. This is similar to how ARC++ encodes an Android task ID in the app ID, e.g. "org.chromium.arc.12345". The ID is sent as a string to provide future flexibility (in case we need to encode different window types, like "lacros_popup") and because it felt like an appropriate return type for the cross-platform method ui::PlatformWindow::GetInternalWindowId(). Feature design doc at go/lacros-select-file Bug: 1090587 Test: multiple simultaneous file open dialogs spawn/stack/close correctly Change-Id: I7b2cdb934480f72f5dbb3523922d30cf5df0376a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2301119 Commit-Queue: James Cook <jamescook@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by:
Robert Kroeger <rjkroege@chromium.org> Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Reviewed-by:
Erik Chen <erikchen@chromium.org> Reviewed-by:
Jorge Lucangeli Obes <jorgelo@chromium.org> Cr-Commit-Position: refs/heads/master@{#791992}
-
James Hollyer authored
For privacy concerns there is a push to add feature policy and Secure Context requirements to gamepads. We are adding these behind a flag now so that we can more easily coordinate the rollout with other browsers. Bug: 1099544 Change-Id: Ic64ae35d74692eaf29f618f8fdbb49cf7a143751 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2269718 Commit-Queue: James Hollyer <jameshollyer@chromium.org> Reviewed-by:
Oliver Chang <ochang@chromium.org> Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Reviewed-by:
Matt Reynolds <mattreynolds@chromium.org> Cr-Commit-Position: refs/heads/master@{#791991}
-
Adithya Srinivasan authored
Bug: 1109750 Change-Id: I2c2f95f427d41dfd98ec230dd4a89f0997635d3c Tbr: apaseltiner@chromium.org, johnidel@chromium.org No-Try: True Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2321399Reviewed-by:
-
Ahmed Mehfooz authored
The implementation to use layer transforms to resize the bubble is no longer used due to recent optimizations. Removing this code and the extra view containers that were required for it. Bug: 1024530 Change-Id: I71e5cecbc51011b16c0b7d0da09464ea4562eacd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318693 Commit-Queue: Ahmed Mehfooz <amehfooz@chromium.org> Reviewed-by:
Tim Song <tengs@chromium.org> Cr-Commit-Position: refs/heads/master@{#791989}
-
Anand K Mistry authored
Bug: b:159021439 Change-Id: Ie1cd845dc910af48d241e5193a2d39ff7e1bd106 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2294940 Auto-Submit: Anand K Mistry <amistry@chromium.org> Reviewed-by:
Brian White <bcwhite@chromium.org> Reviewed-by:
-
