- 02 Jun, 2020 40 commits
-
-
Andy Paicu authored
Bug: 1016730 Change-Id: Ic376f168d5538366026224d7bc3514d84795261c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218778Reviewed-by:
Dominick Ng <dominickn@chromium.org> Commit-Queue: Andy Paicu <andypaicu@chromium.org> Cr-Commit-Position: refs/heads/master@{#774248}
-
Dominic Battre authored
This CL extends, resurrects and ends the life-time of some Autofill histograms. I have also made sure via ``` for p in mathp sebsg rogerm wuandy parastoog ftirelo gogerald \ seblalancette vincb tmartino estade mahmadi; do xmllint --xpath "//histogram[not(./obsolete) and contains(@name, 'Autofill')][./owner[contains(text(), '$p')]]" histograms.xml | grep "<histogram"; done ``` that no previous owners remain as histogram owners so that we get expiration events in the future. Bug: 1088598,1088603e,1088604,1088607,1088608,1088609,1088610,1088611,1088612,1088624,1088625,1088626,1088627,1088637,1088638,1089241,1089683,1089684,1089685,1089891,1089892,1089893 Change-Id: I25468642d019de448b8a5b027805db2882c20ac7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2224865Reviewed-by:Matthias Körber <koerber@google.com> Reviewed-by:
Brian White <bcwhite@chromium.org> Commit-Queue: Dominic Battré <battre@chromium.org> Cr-Commit-Position: refs/heads/master@{#774247}
-
Michael Ludwig authored
Bug: 1087413 Change-Id: If59a27697f3e2b3aa0049c56f9e7f28bad6e9437 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220877 Auto-Submit: Michael Ludwig <michaelludwig@google.com> Reviewed-by:
Jonathan Ross <jonross@chromium.org> Commit-Queue: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/master@{#774246}
-
danakj authored
It used to fail with site isolation but it no longer does. R=foolip@chromium.org Bug: 1007228 Change-Id: I69ba7539d8b08cad2185aecdb22df000df97bec4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2223080Reviewed-by:
Philip Jägenstedt <foolip@chromium.org> Commit-Queue: danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#774245}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/dad4850e5d7a..fc0efae149cb 2020-06-02 primiano@google.com Merge "ui/tp: fix race in trace-processor --httpd and improve performance" If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll 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 Cq-Include-Trybots: luci.chromium.try:linux-perfetto-rel Bug: None Tbr: perfetto-bugs@google.com Change-Id: I122a71b5a4374971fd99f7a0d7fb338d543d8927 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226886Reviewed-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@{#774244}
-
Domenic Denicola authored
Bug: 1042415 Change-Id: I2acd2fea79a12e1f60eb9a0114abcf61630e269a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2202512 Commit-Queue: Domenic Denicola <domenic@chromium.org> Reviewed-by:
James MacLean <wjmaclean@chromium.org> Cr-Commit-Position: refs/heads/master@{#774243}
-
Xida Chen authored
Right now we report throughput to UKM system at: 1. 5 seconds after a sequence starts. 2. Every 500 seconds after that as long as the sequence lasts. The problem is that in many cases users stay on a page less than 500 seconds, and thus we would only get the report for the first 5 seconds, which can be heavily dominated by the page loading period. This CL changes it such that we record the throughput every 5 seconds, and then report the median throughput to the UKM when the page shuts down. At this moment, this applies to the kUniversal tracker only, which tracks all kinds of frame productions. For other types of trackers, such as the trackers tracks animation/scroll, etc, this change will be applied later. Bug: 1040634 Change-Id: I452e16c45187393f29abf1bdf3650a4e5ffb45fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2112953Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Reviewed-by:
Bryan McQuade <bmcquade@chromium.org> Reviewed-by:
Stephen Chenney <schenney@chromium.org> Reviewed-by:
danakj <danakj@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#774242}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/113bf7f2..f0122481 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: Ib6d01b70017846e6ab09ce2ef3c080d1d3c8c33a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225048Reviewed-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@{#774241}
-
Sean Kau authored
The printer filters which were provided through component download have been moved into the rootfs. As such, remove the code responsible for downloading them from Chrome. Bug: 1056364 Change-Id: Ia9bd06b0321326880bace28da7e61554eb877c94 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2146052Reviewed-by:
Piotr Pawliczek <pawliczek@chromium.org> Commit-Queue: Piotr Pawliczek <pawliczek@chromium.org> Auto-Submit: Sean Kau <skau@chromium.org> Cr-Commit-Position: refs/heads/master@{#774240}
-
Sven Zheng authored
With this feature, test can post link to Milo UI. The work for getting gtest supports links is in this design doc: go/gtest-supports-artifacts Bug: 1028400 Change-Id: I5be1699932c5f5304c1ec3a44abbf70829ae394b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1940553 Commit-Queue: Sven Zheng <svenzheng@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#774239}
-
Jesse Schettler authored
These histograms are still being used to devise a solution for handling large print jobs. Bug: chromium:1089318 Change-Id: I1d03975e4d50dd796cbc48d5436c5ab0b922f74f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225471 Commit-Queue: Brian White <bcwhite@chromium.org> Reviewed-by:
-
Devon O'Brien authored
Remove Venafi Gen2 CT log from list of Qualified CT Logs and mark DigiCert Log Server 2 as Retired. Bug: 688510, 698094 Change-Id: I48ae6378753da92c12937490d308900065246958 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225514Reviewed-by:
Ryan Sleevi <rsleevi@chromium.org> Commit-Queue: Devon O'Brien <asymmetric@chromium.org> Cr-Commit-Position: refs/heads/master@{#774237}
-
Ankit Kumar authored
Bug: 1075436 Change-Id: If95e2eeecb1b3a8ed71dfa241086ccb4904ce758 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2217675Reviewed-by:
Lei Zhang <thestig@chromium.org> Commit-Queue: Ankit Kumar
🌪 ️ <ankk@microsoft.com> Cr-Commit-Position: refs/heads/master@{#774236} -
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/03a0d5b08cac..393b040fb4f0 2020-06-02 ehmaldonado@chromium.org Add sokcevic@google.com to owners If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Please CC agable@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: agable@chromium.org Change-Id: Icbf5e7ad9b94255cf9e89a6f7e9c5aa0214fef1d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226888Reviewed-by:
-
Ben Mason authored
TBR=govind@chromium.org Change-Id: I7db3d7137cb6366cc15954c87af45fd7dd678cde Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226309Reviewed-by:
Ben Mason <benmason@chromium.org> Reviewed-by:
Krishna Govind <govind@chromium.org> Commit-Queue: Ben Mason <benmason@chromium.org> Cr-Commit-Position: refs/heads/master@{#774234}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1591099170-ba6cbc301c88d5a4ac71a10c96042329de00e207.profdata to chrome-mac-master-1591113598-81d0db8118cc6885d9786065771de10da2a65ecd.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-mac-chromium Please CC jeffyoon@google.com,liaoyuke@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: chrome/try:mac-chrome Tbr: jeffyoon@google.com,liaoyuke@google.com Change-Id: Iec3bc128f1763d326baffa462d1a9a4c839da053 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226949Reviewed-by:
-
Xianzhu Wang authored
We no longer need to skip composited scrolling for css clip and clip-path since (perhaps) BlinkGenPropertyTrees. In compositor, when we hit test on a layer with special clip/mask, we'll still fallback to main thread hit testing/scrolling because only the main thread knows which area is hit testable. This is achieved by cc::LayerTreeHostImpl::IsInitialScrollHitTestReliable() returning false. Bug: 1074395 Change-Id: I91260b063879812ca82928fe783de25c4b6732a3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225229 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
Philip Rogers <pdr@chromium.org> Reviewed-by:
Robert Flack <flackr@chromium.org> Reviewed-by:
David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#774232}
-
Dale Curtis authored
The root cause is now resolved, so these tests should go back to trying to use real audio. Fixed: 986021,1047655 Change-Id: I4744c0613e47477107cc9a078deb3d8f51b29a62 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225750Reviewed-by:
John Rummell <jrummell@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Commit-Queue: Nasko Oskov <nasko@chromium.org> Auto-Submit: Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#774231}
-
Jochen Eisinger authored
Bug: 1089368 Change-Id: Ifabbbf7c3ccef71cf0f1e115e7b735c1bfd7da91 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225762 Auto-Submit: Jochen Eisinger <jochen@chromium.org> Commit-Queue: Brian White <bcwhite@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/a0cf1eabb73e..4b1ab5728344 2020-06-02 danilchap@webrtc.org Add av1 test with spatial scalability. 2020-06-02 hbos@webrtc.org [Adaptation] Move IsAdaptationUpAllowed/OnAdaptationApplied out of API. 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: I3fc6f19cc9a02837bfe1f33180243357ac0c55bc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226885Reviewed-by:
-
Chris Lu authored
Move common implementations of InfobarBannerInteractionHandler by its subclasses into InfobarBannerInteractionHandler. The DCHECK(inserter_) in OverlayTabHelper is removed, because it can easily lead to tests failing if the ordering of creating TabHelper will fail here. Bug: 1071914 Change-Id: I1f4c8a212aac29112810a2a8b4fef33da909fa84 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2219039 Commit-Queue: Chris Lu <thegreenfrog@chromium.org> Reviewed-by:
Kurt Horimoto <kkhorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#774228}
-
Xianzhu Wang authored
We snap scroll offsets etc. to whole pixels. When we update a cc::TransformNode which has snapping enabled, we do the following: to_parent.Translate(-old_snap_amount); (in TransformTree::UndoSnapping) ... to_parent.Translate(new_snap_amount); (in TransformTree::UpdateSnapping) In most cases (when there is no non-translation transform to screen), we want to_parent to be integral after the snapping, but the above operation can cause floating-point errors causing a non-integral scroll offset. Also repeated operations accumulate errors. To avoid the problems, add gfx::Transform::IsApproximatelyIdentityOrIntegerTranslation(), and use it in TransformTree::UpdateSnapping to check for error, and reset the error. Bug: 1070802 Change-Id: Ic05ab6fa8393aaa5446d6892a85090d36c78b800 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225463 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
-
Brandon Wylie authored
Bug: 1083917 Change-Id: Iea521ba0dc2d525fe266cb0246ef6f0c72a759de Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2222821 Commit-Queue: Brandon Wylie <wylieb@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#774226}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/a5ced794731b..aa9d99ff6b53 2020-06-02 egdaniel@google.com Add support for vk image sharing mode and handle queues xfers correctly. 2020-06-02 bsalomon@google.com Add threshold for partitioning blur draws 2020-06-02 scroggo@google.com Remove transform_scanline from SkWebpEncoder 2020-06-02 herb@google.com Make path data private 2020-06-02 cwallez@chromium.org Rolling 2 dependencies 2020-06-02 jvanverth@google.com Bind D3D constants. 2020-06-02 brianosman@google.com Rewrite SkVertices serialization to use SkReadBuffer/SkWriteBuffer 2020-06-02 skia-autoroll@skia-public.iam.gserviceaccount.com Roll ANGLE from 48102b2b3655 to 77e5316a515d (11 revisions) 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 tdenniston@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: chromium:1084458,chromium:1086532 Tbr: tdenniston@google.com Test: Test: Test: angle_perftest --gtest_filter=VulkanBarriersPerfBenchmark.Run/vulkan_buffer_copy Change-Id: I6b60f9c8e1fa0a6b6e137ac745644024baa110de Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226882Reviewed-by:
-
Ilia Samsonov authored
The purpose of this cl is to reduce the output snippet. This is most prevalent when tests fails on exit, and executed in large batches. Bug: 1086276 Change-Id: I73072f072e12597cdb5dfe53f6153ffaf9cf09d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226089Reviewed-by:
-
kylechar authored
This CL implements code needed for WrappedSkImage to handle shared memory GpuMemoryBuffers. This enables using WrappedSkImage in more places with both SkiaRenderer/Dawn and SkiaRenderer/Vulkan. There are issues with using WrappedSkImage for SkiaRenderer/GL so the logic there is still just for OOP-R. Bug: 1082819 Change-Id: I13a7526f8319f183bf215548aa70ce2cb9faa22d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2210789 Commit-Queue: kylechar <kylechar@chromium.org> Reviewed-by:
Khushal <khushalsagar@chromium.org> Reviewed-by:
Peng Huang <penghuang@chromium.org> Cr-Commit-Position: refs/heads/master@{#774223}
-
Chrome Metrics Logs authored
Updates the expires_after attribute for 181 histograms that show frequent access in the past 90 days. These are the 90% most frequently used histograms over that time that do not already have a date later than or within 60 days of 2020-11-29. TBR=chromium-metrics-reviews@google.com Change-Id: Ifc51ba2db775d597230fbc7208facb37b5c71cce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226111Reviewed-by:
Chrome Metrics Logs <chrome-metrics-team+robot@google.com> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Commit-Queue: Chrome Metrics Logs <chrome-metrics-team+robot@google.com> Commit-Queue: Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#774222}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/72f885bd4df9..4391bc111097 2020-06-02 mathias@chromium.org Recognize CSS variables as valid properties 2020-06-02 patrick.brosset@microsoft.com DevTools: E2E test covering going from perf to sources 2020-06-02 tvanderlippe@chromium.org Remove logic for downloading a content_shell from npm_test.js 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:1071296,chromium:1079076,chromium:1087379 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I718047984ad85e636ac14772e3becc551267558b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226875Reviewed-by:
-
Ricardo Quesada authored
The linux-explicit-sync Wayland interface allows to exchange two different kind of fences: release and acquire. The release fence comes from DrmDevice, but only when drm-atomic is available. Similar, when drm-atomic is present, the Acquire fence can be used in DrmAtomic. And technically, the Acquire-fence can be waited-on outside DrmDevice, but practice shows that when this happens and if drm-atomic is not present, some flickers migtht appear. So, this CL disables the Wayland linux-explicit-sync interface when drm-atomic is not present. This CL should only land *AFTER* these two CLs from ARC are uprevved: * ARC-P: http://ag/11624164 * ARC-R: http://ag/11661407 Tested on ARC Pi and ARC Rvc with the CLs mentioned above. Bug: chromium:1083569 Test: Manually disabled linux-explicit-sync on Chrome side. Change-Id: Iff78eebc5567f96cc9d775d9fce3f851104b04f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2223090Reviewed-by:
Robert Kroeger <rjkroege@chromium.org> Reviewed-by:
Daniele Castagna <dcastagna@chromium.org> Commit-Queue: Ricardo Quesada <ricardoq@chromium.org> Auto-Submit: Ricardo Quesada <ricardoq@chromium.org> Cr-Commit-Position: refs/heads/master@{#774220}
-
Timothy Gu authored
r453744 and r474224 added six use counters to the getters and setters of <embed> and <object>, but none of them keep track of how many such property accesses actually returns a non-null value. This CL adds such a use counter, mending that gap. Bug: 695895 Change-Id: Idef2b4e3c22f7c97611bb67a9399e3555233efed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226910Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Kentaro Hara <haraken@chromium.org> Commit-Queue: Timothy Gu <timothygu@chromium.org> Auto-Submit: Timothy Gu <timothygu@chromium.org> Cr-Commit-Position: refs/heads/master@{#774219}
-
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-win-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: I8d3c80a2bf5115957815a5268248175dd926d401 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226306Reviewed-by:
-
Xi Han authored
Bug: 1086608 Change-Id: Id46f9775c0de498d2b6b15754da281444e3ce06a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2216277Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Reviewed-by:
Matthew Jones <mdjones@chromium.org> Commit-Queue: Xi Han <hanxi@chromium.org> Cr-Commit-Position: refs/heads/master@{#774217}
-
Reilly Grant authored
Linux considers both actual terminals (like the system console) and serial ports to be TTYs. The previous implementation used a series of heuristics to guess whether a new device in the "tty" subsystem was a serial port or not. This information however is available precisely from the kernel. This change parses /proc/tty/drivers and checks if a TTY device matches the major and minor numbers for a known serial port driver. This allows a number of heuristics to be removed. Bug: 1046475 Change-Id: Icc6b8d8bb56270c9762b5ab91a59c63df1e30379 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225491 Auto-Submit: Reilly Grant <reillyg@chromium.org> Reviewed-by:
Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org> Commit-Queue: Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#774216}
-
Jongmok Kim authored
Change-Id: I5469cbb89167f1d1dfd5a83bb15f12e58ae1d454 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226316Reviewed-by:
Connie Wan <connily@chromium.org> Commit-Queue: Connie Wan <connily@chromium.org> Cr-Commit-Position: refs/heads/master@{#774215}
-
Matt Menard authored
This is a reland of 2aef8221 DCHECK use in EnterpriseActivityStorageTest caused linux-chromeos-rel to fail, but not in TryJobs. Original change's description: > Ensure activity is not overwritten when there are multiple users on the same day. > > Since activity is stored from midnight onward for all users (regardless of what time of day the usage interval actually occurred) and the IntervalMap removes overlapping intervals, it would nondeterministically remove usage intervals that occur on the same day with different users. This instead culls usage beyond 24 hours in a day. Since all time is stored UTC this is appropriate in all cases without losing usage due to time changes. > Add unit tests to EnterpriseActivityStorage and ActivityStorage. > Refactor to isolate functionality of each method of the storage classes for better reuse. > Change |user_email| to |activity_id| so the class can be used by classes that need to key preferences but not by an email. > > Bug: 1058453 > Change-Id: I8e5bd7b552d00bddd478c3a275313ccc7ed214a4 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2153748 > Commit-Queue: Matt Menard <mattme@google.com> > Reviewed-by: Aga Wronska <agawronska@chromium.org> > Reviewed-by: Sergey Poromov <poromov@chromium.org> > Cr-Commit-Position: refs/heads/master@{#773574} Bug: 1058453 Change-Id: I0df21c560e0693b998739b58b5d210125d188967 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225817Reviewed-by:
Sergey Poromov <poromov@chromium.org> Commit-Queue: Matt Menard <mattme@google.com> Cr-Commit-Position: refs/heads/master@{#774214}
-
Katie D authored
AX-Relnotes: Adds feature flag for cursor color to chrome://flags. Bug: 1085442 Change-Id: Ie06092e3edb92c93d6b0791349c705aa049f7f2c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220386 Commit-Queue: Katie Dektar <katie@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#774213}
-
Songtao Xia authored
This CL fixes an issue where hinge is shifted when a user changes screen setting. For example in Windows, when a user increases "the size of text, apps and other items" in display setting. The hinge is displaced. Cause: Tools::Draw function takes a windows to view port scale. Hinge copied the logic from HighlightQuad. It draws a quad, whose calculation applies the scale. It really shouldn't as the hinge's geometric parameters by px is measured not in the device world. Like the the width and height of the device, they are measured in the windows/chrome client world. Fix: create the quad using a scale of 1. Before image (annotated with the window-viewport scale and emulation scale factor): https://imgur.com/XCLBdRL Hinge is shifted by window-viewport scale:1.5. After image: 1) Same situation as above: https://imgur.com/XUBdYvb 2) manually chosen emulation scale with scrolling and zooming: https: //imgur.com/e2dTaIX Change-Id: Id1237748d2f41ef5aecd8374c4457e3205d6a91d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2202121Reviewed-by:
Yang Guo <yangguo@chromium.org> Reviewed-by:
Brandon Goddard <brgoddar@microsoft.com> Commit-Queue: Songtao Xia <soxia@microsoft.com> Cr-Commit-Position: refs/heads/master@{#774212}
-
Samuel Tang authored
Manifest parser can now parse protocol_handlers This feature allows the blink parser to parse protocol_handlers defined in its app manifest. It is checked in behind the flag ParseUrlProtocolHandler. The current CL does not include semantic validation of the scheme. We will include it in a subsequent CL to keep CLs small and scoped. This feature is part of a Chrome experiment, see the feature page: https://chromestatus.com/features/5151703944921088 The URLProtocolHandler explainer can be found here: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/URLProtocolHandler/explainer.md The main bug link is: https://bugs.chromium.org/p/chromium/issues/detail?id=1019239 The blinkdev proposal is here: https://groups.google.com/a/chromium.org/forum/?hl=en#!topic/blink-dev/x4Ev_l9Oj2U Bug: 1019239 Change-Id: I85a99064485f12e7c224bdaf491ad413e451229c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2211200Reviewed-by:
Alex Russell <slightlyoff@chromium.org> Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Commit-Queue: Samuel Tang <samtan@microsoft.com> Cr-Commit-Position: refs/heads/master@{#774211}
-
Domenic Denicola authored
Bug: 1067389, 1042415 Change-Id: I5edc60736200bf8335ff1ff9422d53d8fea52569 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2199909Reviewed-by:
-
Fabian Sommer authored
For component policies that fail to validate against their schema, an error message is now displayed in about:policy. Components will still not see the invalid policy values. Fixed: 974676 Change-Id: I2a8fa750df69721617a2043344364700acbccb9d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2054944 Commit-Queue: Fabian Sommer <fabiansommer@chromium.org> Reviewed-by:
Alexander Hendrich <hendrich@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Cr-Commit-Position: refs/heads/master@{#774209}
-
