- 16 Jan, 2020 40 commits
-
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/5fc197dc7669..5c6a3c247590 git log 5fc197dc7669..5c6a3c247590 --date=short --first-parent --format='%ad %ae %s' 2020-01-16 capn@google.com Remove the GL_NV_read_depth_stencil extension Created with: gclient setdep -r src/third_party/swiftshader@5c6a3c247590 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Please CC swiftshader-team+autoroll@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: Iaced2f9f37d65f35413e60c7b7124dc2d401154f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2004893Reviewed-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@{#732555}
-
Tina Wang authored
- No user visible change in this cl. - Add new directory for profile card. - Add basic classes. Change-Id: Ic09d5f097f712a9c58c1ed666eba22fac1d9236c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993146Reviewed-by:
sebsg <sebsg@chromium.org> Reviewed-by:
David Trainor <dtrainor@chromium.org> Commit-Queue: Tina Wang <tinazwang@chromium.org> Cr-Commit-Position: refs/heads/master@{#732554}
-
Ryan Sturm authored
This is a reland of 4e23e8e8 Patchset 1 is what previously landed. This caused flakes in other loading predictor browser tests, so I added the holdback to all of the tests. In a follow-up, I will make sure the tests check for preconnects on the appropriate URLs. See https://chromium-review.googlesource.com/c/chromium/src/+/2004181 for revert rationale. Original change's description: > Adding a FTT config for PreconnectSameOriginDesktop > > This experiment is in canary/dev and should be moved to Beta. > > Bug: 1038774 > Change-Id: I4fc9c44e2b68aa58f9eee7210a625103f45edb01 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992684 > Commit-Queue: Ryan Sturm <ryansturm@chromium.org> > Reviewed-by: Alex Ilin <alexilin@chromium.org> > Reviewed-by: Ilya Sherman <isherman@chromium.org> > Reviewed-by: Tarun Bansal <tbansal@chromium.org> > Cr-Commit-Position: refs/heads/master@{#732219} Bug: 1038774 Change-Id: Id7bd4bddf5b5812d02a8953d0733f8af73007fb6 TBR=tbansal@chromium.org,alexilin@chromium.org Change-Id: Id7bd4bddf5b5812d02a8953d0733f8af73007fb6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2004691Reviewed-by:
Alex Ilin <alexilin@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Ryan Sturm <ryansturm@chromium.org> Commit-Queue: Ryan Sturm <ryansturm@chromium.org> Cr-Commit-Position: refs/heads/master@{#732553}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/01c0d6bd8d7f..bdb0f8a52414 git log 01c0d6bd8d7f..bdb0f8a52414 --date=short --first-parent --format='%ad %ae %s' 2020-01-16 angle-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/vulkan-tools/src 2c436960d2c0..4792a6854238 (3 commits) 2020-01-16 sugoi@google.com Support blendable capability 2020-01-16 angle-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/vulkan-headers/src f63dd5c9d874..881bbb347a08 (1 commits) 2020-01-16 jonahr@google.com Expose GL_ANGLE_framebuffer_blit in NULL backend Created with: gclient setdep -r src/third_party/angle@bdb0f8a52414 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 jonahr@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_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 Bug: chromium:1029829 Tbr: jonahr@google.com Change-Id: I4387a446682487ca735f0423c6bee716a858c125 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2005308Reviewed-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@{#732552}
-
Takumi Fujimoto authored
This CL adds a secondary_title field to media_router.mojom.MediaStatus, corresponding to the media.metadata.subtitle field in Cast SDK media status messages, which contains artist names for media. The artist name is shown in a Cast notification item in Global Media Controls. Other labels are also rearranged to match the mocks. Screenshot: https://drive.google.com/file/d/1Ecr-7WsGFE7Be3MuPvsau3SEUwKPQPJr/view?usp=sharing Bug: 1042016 Change-Id: Iff3cc50af41ef24e6a4e8ec10090acbffe049f8f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003388 Commit-Queue: Takumi Fujimoto <takumif@chromium.org> Reviewed-by:
Tommy Steimel <steimel@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
mark a. foltz <mfoltz@chromium.org> Cr-Commit-Position: refs/heads/master@{#732551}
-
Fei Ling authored
Fix issue 1038319: Unable to change chrome language via chrome://settings/languages on Windows-Hebrew machine. The problem is that the chrome installer uses the old language code for Hebrew, "iw", instead of the new code "he". This value is saved in the user's local state. The language model in langauges.js does not recognize this language code, thus the bug. Fixed: 1038319 Change-Id: Ib227b2972989c2fa87fdc2d4be408040ad137c55 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1990476Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Fei Ling <feiling@chromium.org> Cr-Commit-Position: refs/heads/master@{#732550}
-
Oriol Brufau authored
Unlike ::before and ::after, in ::marker 'content: normal' and 'none' should behave differently: the former should display it normally, the latter should prevent it from generating a box. Before this patch, 'normal' and 'none' were both stored as nullptr, so they were indistinguishable. This patch makes 'none' be stored as a NoneContentData instead. However, 'none' keeps behaving as 'normal' for anything different than ::marker. In getComputedStyle, 'none' keeps resolving to 'normal' for anything different than ::marker, ::before and ::after, and 'normal' keeps resolving to 'none' for ::before and ::after. Inheritance is not affected either since the 'content' property can't be inherited in Chromium. BUG=457718 TEST=external/wpt/css/css-pseudo/marker-computed-content.html TEST=external/wpt/css/css-pseudo/marker-computed-size.html TEST=external/wpt/css/css-pseudo/marker-content-019.html marker-content-019.html fails in legacy. Change-Id: Ib71ef18dfb7f7c98e76888bffb408a17fa458235 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002517Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Commit-Queue: Oriol Brufau <obrufau@igalia.com> Cr-Commit-Position: refs/heads/master@{#732549}
-
Wenyu Fu authored
Add focus & setEnabled related enhancement to RadioButtonWithEditText and add some test. Change-Id: Iad713ddaa108f084e9f98e882bcd6e6135384756 Bug: 1036470 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1991717 Commit-Queue: Wenyu Fu <wenyufu@chromium.org> Auto-Submit: Wenyu Fu <wenyufu@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Cr-Commit-Position: refs/heads/master@{#732548}
-
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-sdk-chromium-autoroll Please CC cr-fuchsia+bot@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast Tbr: cr-fuchsia+bot@chromium.org Change-Id: I182a534bbca26fd66c8c907c2ef0bd9c72168fcc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2005332Reviewed-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@{#732547}
-
Robert Ma authored
Bug: 1036130 Change-Id: Ie6bf04fcdae3af73aa7f412acbfd9cf692ad156d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002747 Commit-Queue: Robert Ma <robertma@chromium.org> Commit-Queue: Rakib Hasan <rmhasan@google.com> Auto-Submit: Robert Ma <robertma@chromium.org> Reviewed-by:
Rakib Hasan <rmhasan@google.com> Cr-Commit-Position: refs/heads/master@{#732546}
-
Zhuoyu Qian authored
Update the function GetUsageCachePathForOriginAndType to use dedicated Origin type instead of GURL. Bug: 598424 Change-Id: I05ddacce6d15c9d6125b92e425cc79b251e26b7f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2004356 Commit-Queue: Victor Costan <pwnall@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#732545}
-
Kurt Horimoto authored
Added in this CL: - Response info types for password modal delegate callbacks. - Coordinator and mediator classes to handle UI setup. - Update mock passwords delegate to set the URL. Bug: 1030357 Change-Id: Ia5b375869234b26b36df6220a1b2908847723e18 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995635 Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org> Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Reviewed-by:
Sergio Collazos <sczs@chromium.org> Auto-Submit: Kurt Horimoto <kkhorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#732544}
-
danakj authored
Drop the RenderWidget::StartStopCompositor() method and just have the two sites call LayerTreeView::SetVisible() directly. Turn TODOs into comments explaining things or delete them where they don't make sense anymore (we're done them!). RenderViewImpl::CloseWindowSoon() should check if there is a main frame instead of checking if it owns a RenderWidget, so we can move ownership over to RenderFrameImpl. These two are equivalent currently. R=avi@chromium.org Bug: 419087 Change-Id: I8449ed02d694eb28046b8ae2d7439640bdbf49ce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003630 Commit-Queue: danakj <danakj@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#732543}
-
Demetrios Papadopoulos authored
flattenhtml does not work with Polymer3 generated files. Instead register images with the WebUIDataSource so that they can be served by a chrome://extensions URL. Bug: None Change-Id: I33346fac61b1f4d0937615fa8dde38c22809de89 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003196Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#732542}
-
Henrique Nakashima authored
This is CL 3/5 for moving ChromeFeatureList to the .flags package. Bug: 1041468 Change-Id: Ib46b9ecab62300d54e7f236ee75ddd150af2d019 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003441 Commit-Queue: Henrique Nakashima <hnakashima@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Cr-Commit-Position: refs/heads/master@{#732541}
-
Stephen Chenney authored
The Blink.MainFrame.UpdateTime metric was missing from the affected metrics list for the PreLCP, PostLCP and AggregatedPreLCD suffixes. Bug: 1040545 Change-Id: Ie8db9ac44d14b41617bf381cd5a743832c0cc881 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001247 Auto-Submit: Stephen Chenney <schenney@chromium.org> Reviewed-by:
Bryan McQuade <bmcquade@chromium.org> Commit-Queue: Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#732540}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/c4b8eefe5653..2cd5d43f022c git log c4b8eefe5653..2cd5d43f022c --date=short --first-parent --format='%ad %ae %s' 2020-01-16 halcanary@google.com [minor] docs/examples: cleanup 2020-01-16 mtklein@google.com Revert "Simplify VertexRegenerator GrStrikeCache handling" 2020-01-16 herb@google.com Simplify VertexRegenerator GrStrikeCache handling 2020-01-16 herb@google.com Handle color and translation outside of VertexRegenerator Created with: gclient setdep -r src/third_party/skia@2cd5d43f022c 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 mtklein@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-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: mtklein@google.com Change-Id: Ica2985cdbba32c491d817c87e8e09cba6d466354 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003625Reviewed-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@{#732539}
-
Victor Vasiliev authored
https://quiche.googlesource.com/quiche.git/+log/1f4fe2d7c33b..e5e25bc2ec5c $ git log 1f4fe2d7c..252403d10 --date=short --no-merges --format='%ad %ae %s' 2020-01-15 vasilvv Remove the DCHECK from ParsedQuicVersion constructor. 2020-01-15 wub gfe-relnote: For QUIC BBRv2, always count the number of loss marking events in a round and only exit PROBE_UP if that number is above a threshold. Protected by --gfe2_reloadable_flag_quic_bbr2_always_count_loss_events. 2020-01-15 bnc Remove Http2StrCat, use QuicheStrCat instead. 2020-01-15 bnc Move Http2Optional to QuicheOptional. 2020-01-14 bnc Move SpdyWrapUnique to QuicheWrapUnique. 2020-01-14 nharper gfe-relnote: Add kSupportedVersions to quic_versions.h, no behavior change 2020-01-14 renjietang Code cleanup in QuicStreamSequencer. 2020-01-14 fayang gfe-relnote: In QUIC, rename IsCryptoHandshakeConfirmed to OneRttKeysAvailable in QuicSession. Renaming only, not protected. 2020-01-14 wub gfe-relnote: Mimic QUIC BBRv2 style loss based exit in BBRv1 code. Protected by --gfe2_reloadable_flag_quic_bbr_loss_based_startup_exit _and_ connection option 'LRTT'. 2020-01-14 wub gfe-relnote: (n/a) Deprecate --gfe2_restart_flag_quic_use_circular_deque. 2020-01-14 fayang gfe-relnote: In QUIC, rename handshake_confirmed in handshaker to one_rtt_keys_available to make it clearer and more informative. Renaming only, not protected. 2020-01-14 quiche-dev Internal QUICHE change 2020-01-14 wub gfe-relnote: (n/a) Make QUIC BBRv2's initial ack height filter window tunable by flag --quic_bbr2_default_initial_ack_height_filter_window. No behavior change when the flag is at its default value. 2020-01-13 fayang gfe-relnote: Deprecate gfe2_reloadable_flag_quic_skip_packet_number_for_pto. 2020-01-13 fayang gfe-relnote: In QUIC, add a multiplier (default to 2) to consider overshooting happens if bytes_lost_with_network_parameters_adjusted_ * bytes_lost_multiplier_with_network_parameters_adjusted_ > IW. Protected by existing gfe2_reloadable_flag_quic_bbr_mitigate_overly_large_bandwidth_sample. 2020-01-13 dschinazi Refactor some QUIC version code 2020-01-13 dschinazi Refactor handling of supported versions 2020-01-13 dschinazi Internal QUICHE change 2020-01-13 wub gfe-relnote: Add QuicUdpSocketApi, a de-platformized version of QuicSocketUtils, and use it in some non-production code. No behavior change, not protected. 2020-01-13 fayang gfe-relnote: Deprecate gfe2_reloadable_flag_quic_enable_ietf_loss_detection. 2020-01-10 rch gfe-relnote: When a QUIC client receives an unexpected crypto tag, include the tag in the connection close details. Not flag protected. 2020-01-10 fayang gfe-relnote: Change cwnd bootstrapping UpAndDown experiment group IW to 10. Protected by existing gfe2_reloadable_flag_quic_bbr_mitigate_overly_large_bandwidth_sample. 2020-01-10 fayang gfe-relnote: Deprecate gfe2_reloadable_flag_quic_enable_pto. Created with: roll-dep src/net/third_party/quiche/src Change-Id: Ibf95032d6b672e9e888a9aa560827ed03e907bae Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003868 Commit-Queue: Victor Vasiliev <vasilvv@chromium.org> Reviewed-by:
Steve Anton <steveanton@chromium.org> Reviewed-by:
Ryan Hamilton <rch@chromium.org> Cr-Commit-Position: refs/heads/master@{#732538}
-
Natalie Chouinard authored
Move constants related to Autofill settings alongside the code that uses them. This will help future Settings modularization efforts. Change-Id: Ie50712842bafa681adfae29e46325b9b3cab9452 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2004050 Commit-Queue: sebsg <sebsg@chromium.org> Reviewed-by:
sebsg <sebsg@chromium.org> Cr-Commit-Position: refs/heads/master@{#732537}
-
Jae Hoon Kim authored
Measure the rate in which PluginVM DLC is fallingback to rootfs resident PluginVM. A good metric to have in order to determine a stable state of DLC(s) to deem removal from rootfs in the future. Bug: chromium:145814572 Test: unit_tests --gtest_filter=PluginVm* Change-Id: Ib13aa2f6922954bc18f973abf746a3485d0980fd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2004056 Commit-Queue: Jae Hoon Kim <kimjae@chromium.org> Reviewed-by:
Timothy Loh <timloh@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/heads/master@{#732536}
-
Tibor Goldschwendt authored
This prepares for reusing the grid for the backgrounds settings. Also, this CL adds support for non-full (i.e. the last row has empty spaces) grids. Bug: 1032328 Change-Id: Iab76c9bce52b832833d09301c560963b9ab2618c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003294 Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Reviewed-by:
Esmael Elmoslimany <aee@chromium.org> Cr-Commit-Position: refs/heads/master@{#732535}
-
Eric Stevenson authored
This is a reland of 24f7b916. Fixed in the reland: Disabled failing test when !DCHECK_IS_ON. Original change's description: > Android: Better error messaging for some UnsatisfiedLinkErrors. > > A common cause of UnsatisfiedLinkErrors is that the native library > hasn't been loaded yet. It's difficult to tell the difference between > this and other UnsatisfiedLinkErrors. > > This CL adds generated code that queries LibraryLoader to determine > library loading status and throws an explicit error when a native > method is called before the library has been loaded. > > Bug: 1022938 > Change-Id: I63980990abaef16da3847a05eda01cb116779560 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1976905 > Reviewed-by: Andrew Grieve <agrieve@chromium.org> > Commit-Queue: Eric Stevenson <estevenson@chromium.org> > Cr-Commit-Position: refs/heads/master@{#729461} Tbr: agrieve@chromium.org Bug: 1022938 Change-Id: I47651e6a222d55383689495ea2fc532d1d38d10c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001438 Commit-Queue: Eric Stevenson <estevenson@chromium.org> Auto-Submit: Eric Stevenson <estevenson@chromium.org> Reviewed-by:
Michael Thiessen <mthiesse@chromium.org> Cr-Commit-Position: refs/heads/master@{#732534}
-
Nico Weber authored
`gn format` recently changed its formatting behavior for deps, source, and a few other elements when they are assigned (with =) single-element lists to be consistent with the formatting of updates (with +=) with single-element. Now that we've rolled in a GN binary with the change, reformat all files so that people don't get presubmit warnings due to this. This CL was uploaded by git cl split. R=thomasanderson@chromium.org Bug: 1041419 Change-Id: I508a1fc4a66d5650bd7f635b45af94827577d2ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1998623 Auto-Submit: Nico Weber <thakis@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/master@{#732533}
-
Josh Nohle authored
Bug: 951969, 936273 Change-Id: I8c58888157ecc7d715d10ab1053cb0439e69d275 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986260Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Auto-Submit: Josh Nohle <nohle@chromium.org> Commit-Queue: Josh Nohle <nohle@chromium.org> Cr-Commit-Position: refs/heads/master@{#732532}
-
Eric Seckler authored
The deprecated TRACE_EVENT_ASYNC* macros have been superseded by TRACE_EVENT_NESTABLE_ASYNC*. Updating to the new macros is mostly straight-forward, except in cases where STEP_INTO/PAST macros were used extensively: In those cases, the steps have been converted into nested sub-events. Note this also fixes an issue in CompositorFrameReporter where the parent "PipelineReporter" event may have begin/end timestamps that didn't match its child stage event's explicit timestamps. Bug: 1038710 Change-Id: I127a266af023876a8653873108389c477da55c5f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986839 Commit-Queue: Eric Seckler <eseckler@chromium.org> Reviewed-by:
Eric Karl <ericrk@chromium.org> Reviewed-by:
Sami Kyöstilä <skyostil@chromium.org> Cr-Commit-Position: refs/heads/master@{#732531}
-
Taylor Bergquist authored
The deficiency from spec is the bounciness in the border returning to its start position - it should be more springlike, overshooting and then returning, maybe more than once. Bug: 1024009 Change-Id: Ibd374ed742fba7aa18705c744ec7420af58274c7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992207 Commit-Queue: Taylor Bergquist <tbergquist@chromium.org> Reviewed-by:
Peter Boström <pbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#732530}
-
Francois Doray authored
There isn't much more we can learn from this histogram. See current data in https://docs.google.com/document/d/18uYnVwLly7C_ckGsDbqdNs-AgAAt3AmUmn7wYLkyBN0/edit#heading=h.ithbu3taphzc Fixed: 1037320 Bug: 1037320 Change-Id: I11f68499b623e4c5c89eff3822de0f93cb80d0ac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003394Reviewed-by:
Mark Pearson <mpearson@chromium.org> Commit-Queue: François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#732529}
-
Christian Biesinger authored
I would like to use this value for the newer version of intrinsic-size, which will allow "none" and fixed values, so renaming this to None will make more sense for that. Bug: 991096 Change-Id: I61b827800c502c635cc6549ad83bcc705da12732 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2004395 Commit-Queue: Christian Biesinger <cbiesinger@chromium.org> Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Auto-Submit: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#732528}
-
Joshua Peraza authored
This reverts commit 3109a771. Reason for revert: crbug/1040374 Original change's description: > linux: enable crashpad > > This change disables Breakpad and enables Crashpad for Chrome_Linux. It > should not affect other embedders or Chrome_ChromeOS. > > Change-Id: I7017f1c6530fe58235e7ce955051b5b469e75244 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1958693 > Commit-Queue: Joshua Peraza <jperaza@chromium.org> > Reviewed-by: Ken Rockot <rockot@google.com> > Cr-Commit-Position: refs/heads/master@{#724394} TBR=rockot@google.com,jperaza@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Change-Id: I61e3e205b730527133e668b5aeaab6d99ad8fb86 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2005059Reviewed-by:
Joshua Peraza <jperaza@chromium.org> Reviewed-by:
Ken Rockot <rockot@google.com> Commit-Queue: Ken Rockot <rockot@google.com> Cr-Commit-Position: refs/heads/master@{#732527}
-
Nazerke authored
QRScannerLegacyCoordinator had explicit CommandDispatcher property. This CL updates it to use the preferred init for coordinators, which provides a Browser instance which includes those parameters. Bug: 1029346 Change-Id: Ib91ad76843f6af2960e4965639c2d1739cbd4315 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003173 Commit-Queue: Nazerke Kalidolda <nazerke@google.com> Reviewed-by:
Mark Cogan <marq@chromium.org> Cr-Commit-Position: refs/heads/master@{#732526}
-
Bailey Berro authored
This change introduces the ash::kDisplayChangeModal feature and flag to toggle the use of the display configuration change modal rather than the notification. In addition, this change parametrizes the tests in ResolutionNotificationControllerTest so that they are run with the flag in both positions. Change-Id: I9c52b618be412b8f3f41afe5bc3e256ac313932d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1979015 Auto-Submit: Bailey Berro <baileyberro@chromium.org> Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Reviewed-by:
Zentaro Kavanagh <zentaro@chromium.org> Commit-Queue: Bailey Berro <baileyberro@chromium.org> Cr-Commit-Position: refs/heads/master@{#732525}
-
Roger Tawa authored
Bug: 1009158 Change-Id: I975c196c1f92201c1cb98c646bdffb7e12986ad0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994053Reviewed-by:
Jesse Doherty <jwd@chromium.org> Reviewed-by:
Daniel Rubery <drubery@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Roger Tawa <rogerta@chromium.org> Cr-Commit-Position: refs/heads/master@{#732524}
-
Antonio Gomes authored
blink.mojom.RemoteFrame is the target interface. BUG=1041066 R=avi@chromium.org, dcheng@chromium.org, dtapuska@chromium.org, haraken@chromium.org Change-Id: I8fafb5afb425b15bac4d97598130cb9c2c5dc911 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2004690Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Cr-Commit-Position: refs/heads/master@{#732523}
-
Kevin Babbitt authored
Testing with Windows Narrator scan mode on Wikipedia showed we were spending an inordinate amount of time comparing text positions due to the cost of creating ancestor positions. This CL avoids that cost by comparing the order of the first uncommon ancestors for each node, when it's possible to do so. Testing on https://en.wikipedia.org/wiki/List_of_highest-grossing_films with Narrator scan mode heading movement showed a reduction of about 87% CPU usage on the browser main thread with this CL. Bug: 1029867 Change-Id: I7efae50517a561319dad81668c49ec5f6ae900b5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1999083 Commit-Queue: Kevin Babbitt <kbabbitt@microsoft.com> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Jacques Newman <janewman@microsoft.com> Reviewed-by:
Adam Ettenberger <adettenb@microsoft.com> Reviewed-by:
Ethan Jimenez <ethavar@microsoft.com> Cr-Commit-Position: refs/heads/master@{#732522}
-
Stefan Zager authored
When the iframes are loaded in parallel, the ordering of the alert() calls is not deterministic. This converts the test to testharness, and loads the iframes serially to ensure determinism. If any of the iframes fails to generate a load event, the test will time out. BUG=1004650 R=clamy@chromium.org Change-Id: I4c4c2f2bca388f2a157907029b155366cf27b4da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986958 Commit-Queue: Stefan Zager <szager@chromium.org> Reviewed-by:
Daniel Vogelheim <vogelheim@chromium.org> Cr-Commit-Position: refs/heads/master@{#732521}
-
Francois Doray authored
Currently, Breakpad will silently truncate a crash key name with a length above the limit of 40 characters. Unfortunately, trying to retrieve the value of the key with crash_reporter::GetCrashKeyValue() will fail, as the truncated name is not used for retrieval. This CL adds a DCHECK for the crash key length, to avoid having other people chasing the same problem as me when writing a test for crash keys. Change-Id: I6f08ddcb5df9589b7604f34fbeb2dbb6573b1b20 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1999220 Commit-Queue: François Doray <fdoray@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#732520}
-
Alex Clarke authored
Update chromium protos to match internal ones. Bug: 1025781 Change-Id: I6c7c39d21d574e2e5f42cf51026a11e876946309 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2005188Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Commit-Queue: Alex Clarke <alexclarke@chromium.org> Cr-Commit-Position: refs/heads/master@{#732519}
-
Toni Barzic authored
BUG=1026343 Change-Id: Ibb517db781ceffd26e7f4fa9e00d087d9b814af3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2004053Reviewed-by:
Alex Newcomer <newcomer@chromium.org> Commit-Queue: Toni Baržić <tbarzic@chromium.org> Cr-Commit-Position: refs/heads/master@{#732518}
-
Hui Yingst authored
1. Add a two-up view flag inside DocumentLayout::Options. Modify layout_test.js accordingly and add matching unit tests. 2. Add backend support for handling message type "setTwoUpView", which will update viewport's layout options and apply the changes. 3. Add unit tests for PDFiumEngine::SetTwoUpView(). Bug: 51472 Change-Id: I212418b439e860feb9e6ed8761a5f722f2a14a9d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1976156Reviewed-by:
Lei Zhang <thestig@chromium.org> Commit-Queue: Hui Yingst <nigi@chromium.org> Cr-Commit-Position: refs/heads/master@{#732517}
-
Tom Anderson authored
On older versions of dpkg-shlibdeps, the line was omitted rather than being "shlibs:Depends=\n". BUG=1041360 TBR=thestig CC=wuwang NOTRY=true Change-Id: I66263774564ac3df9c083d3a79a3de54bd1bfea6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2004955 Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/master@{#732516}
-