- 27 Jul, 2020 40 commits
-
-
Leonard Grey authored
Currently, if no max width is specified, we use 1.5 * min_width as the max which can be insufficient especially in longer languages (but this also affects English: for example, on my machine "GPU memory" nor "Keepalive count" can fit the name in the header). This change leaves the max width unset if it's not specified. It also changes the autoresizing style to "Sequential" which prioritizes in leading to trailing order, to ensure "Task" is prioritized for resizes. Bug: 1109129 Change-Id: I238942541af72b4baea4d61b98e5cfcaa795ff98 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317837Reviewed-by:
Robert Sesek <rsesek@chromium.org> Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Leonard Grey <lgrey@chromium.org> Cr-Commit-Position: refs/heads/master@{#792039}
-
Ilia Samsonov authored
Baselines were generated in the following build: https://ci.chromium.org/p/chromium/builders/try/linux-blink-optional-highdpi-rel/5 Bug: 1068400 Change-Id: Ib968dee91dff397c094f56849fc4ffeb29642b76 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2293112Reviewed-by:
Dominik Röttsches <drott@chromium.org> Commit-Queue: Ilia Samsonov <isamsonov@google.com> Cr-Commit-Position: refs/heads/master@{#792038}
-
Katie D authored
Bug: 1109932, 1109931 Change-Id: I1779f4b7c4a78aef7d6addaaa5161d84dc169843 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2320083 Auto-Submit: Katie Dektar <katie@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Commit-Queue: Mark Pearson <mpearson@chromium.org> Cr-Commit-Position: refs/heads/master@{#792037}
-
Rakib M. Hasan authored
If the 'test' key is in the definition for a basic test suite, then that value overrides the mixed compound test suites name. The name for the suite should be the test suites name plus the identifier field set in a variants list entry. Bug: 1041619 Bug: 1109967 Change-Id: I8a44b23d2511d2a5e85c0d06e3047c1d50abf011 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318305 Commit-Queue: Rakib Hasan <rmhasan@google.com> Reviewed-by:
Garrett Beaty <gbeaty@chromium.org> Cr-Commit-Position: refs/heads/master@{#792036}
-
Hongchan Choi authored
Fixes a potential data race of |source_number_of_channels_|. In the worst scenario, the rendering may fail with a crash when the output channel count does not match. - SetFormat() is peeking/writing the value. (mostly from main thread) - Process() is reading the value. (rendering thread) Bug: 1108477 Change-Id: I4b64eab94b66e1998a456915d4eaa391791dc44f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316404 Commit-Queue: Hongchan Choi <hongchan@chromium.org> Reviewed-by:
Raymond Toy <rtoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#792035}
-
wutao authored
Bug: b/162140949 Test: manual Change-Id: Ib162aa253ac6f47c519a8e0100f1d369bc9c1d01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2319146Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Commit-Queue: Tao Wu <wutao@chromium.org> Cr-Commit-Position: refs/heads/master@{#792034}
-
James Long authored
A convex hull is now created around nodes within the same buildtarget, expanded outwards slightly, and rendered on the visualization. Each buildtarget is a different color, and nodes are colored according to their buildtarget. This feature can be turned off with a radio button UI element. To support this feature, the original node colorings have been changed to outline colors. Bug: 1106121 Change-Id: Idbb89a5010fa56bc6ac083c65e98d77930796127 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316790Reviewed-by:
Mohamed Heikal <mheikal@chromium.org> Reviewed-by:
Samuel Huang <huangs@chromium.org> Commit-Queue: James Long <yjlong@google.com> Cr-Commit-Position: refs/heads/master@{#792033}
-
Andrew Comminos authored
When a pointer lock is active for an element, all pointer events are dispatched to the element holding the lock in PointerEventManager::HandlePointerEvent. Incorporate this logic in LocalFrame::CanAccessEvent to ensure isInputPending works with pointer locks. Bug: 1092617, 910421 Change-Id: Ie1089322e81731c832d78bf016be91cefedd63ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318650Reviewed-by:
Stefan Zager <szager@chromium.org> Commit-Queue: Andrew Comminos <acomminos@fb.com> Cr-Commit-Position: refs/heads/master@{#792032}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/c3ccd3a79714..308078b0ca18 2020-07-27 jmadill@chromium.org Tests: Add getProcAddress method to GLWindowBase. 2020-07-27 tobine@google.com Vulkan:Enable Validation best practices layer 2020-07-27 cclao@google.com Vulkan: Make mDefaultUniformStorage per ContextVk 2020-07-27 flibitijibibo@gmail.com Add GGP to Platform Support table 2020-07-27 msisov@igalia.com X11: cast native display type to XDisplay. 2020-07-27 nguyenmh@google.com Update CaptureAndReplay.md and Python script with links 2020-07-27 angle-autoroll@skia-public.iam.gserviceaccount.com Roll SwiftShader from 6a8a74986c35 to 3b2cd31c7400 (9 revisions) 2020-07-27 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Vulkan-ValidationLayers from adf938680697 to 361fb5311b9b (13 revisions) 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 tobine@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:1085700 Tbr: tobine@google.com Change-Id: Ib7f3eb5a62663714756fb4ba5b3fac0029cb91a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2321089Reviewed-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@{#792031}
-
Daniel McArdle authored
Although it seems unlikely that the clock would ever return a positive or negative infinity value in real life, we need to help the fuzzer get over this bump. Under the hood, TimeBase::operator- was being invoked when we computed |backoff_duration = absolute_release_time - time_now|, and this operation was overflowing the int64_t. This CL converts the values to TimeDelta before subtracting. As a result, the subtraction now uses TimeDelta::operator-, ensuring the integer overflow does not occur via saturating math. Bug: 1083616 Change-Id: I24481920a4dfc4b2f8bd57b106190879656ddc28 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2320416Reviewed-by:
Maksim Orlovich <morlovich@chromium.org> Commit-Queue: Dan McArdle <dmcardle@chromium.org> Cr-Commit-Position: refs/heads/master@{#792030}
-
Sebastien Lalancette authored
This first iteration: - Adds a new Context Menu with a "Copy" action, - Wraps the old implementation with a feature flag check, - Adds metrics for the new context menu and its action. Bug: 1093302 Change-Id: I4dbf4b1384b0db59d1ff811ee969059d3f0e2c43 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2303023 Commit-Queue: Sebastien Lalancette <seblalancette@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Mark Cogan <marq@chromium.org> Cr-Commit-Position: refs/heads/master@{#792029}
-
Ken Rockot authored
Navigations which fail with network errors may attempt to auto-reload in some cases, in order to more seamlessly recover from transient failures. This behavior was previously implemented renderer-side and copied verbatim from Chrome. The Chrome implementation has been moved browser-side (see bug for why) and also made into a reusable component. This changes WebLayer to use the same component implementation and deletes all the corresponding renderer logic. Fixed: 1098578 Change-Id: I10c337abcae36f64be47f31b89e36c7393989077 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2311371 Commit-Queue: John Abd-El-Malek <jam@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#792028}
-
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:
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@{#792019}
-
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:
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@{#792015}
-
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 <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#792012}
-
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:
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@{#792011}
-
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:
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@{#792006}
-
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}
-