- 21 Aug, 2020 40 commits
-
-
Hirokazu Honda authored
Bug: 1045825 Test: Build video_encode_accelerator_perf_tests Change-Id: I55c9af739236ee154a04ebc9f858be28c00e37ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368653Reviewed-by:
David Staessens <dstaessens@chromium.org> Commit-Queue: Hirokazu Honda <hiroh@chromium.org> Cr-Commit-Position: refs/heads/master@{#800449}
-
jongdeok.kim authored
In this CL, create a transform node instead of setting Layer::SetHasWillChangeTransformHint(). By doing so, each node can see if it's parents have will-change:transform compositing reason. Bug: 1114504 Change-Id: Ia5e9fe82126dc343e0cffbdbccff3b2d4cf4fcac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2355660 Commit-Queue: jongdeok.kim <jongdeok.kim@navercorp.com> Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#800448}
-
Maggie Cai authored
In the case of getting apps from app service, there is no need to defer the navigation. Update the code to move the icon loading code out of defer navigation and never defer navigation. BUG=853604 Change-Id: Idbc0dba4eb18eea16dfe907be7849877f0879395 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367232Reviewed-by:
Dominick Ng <dominickn@chromium.org> Commit-Queue: Maggie Cai <mxcai@chromium.org> Cr-Commit-Position: refs/heads/master@{#800447}
-
Juliet Levesque authored
Add style to make dictionaries passed as NS_LOGS more readable on the debug page. Bug: 1093634 Change-Id: Iae95b101a1ad00af5e0267d1aa444f33fe670a56 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368496Reviewed-by:
Josh Nohle <nohle@chromium.org> Commit-Queue: Juliet Levesque <julietlevesque@google.com> Cr-Commit-Position: refs/heads/master@{#800446}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/77419b0f04e8..9869f187b5ea 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: Iba63033667499609e903edeb5947a6e983664212 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368247Reviewed-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@{#800445}
-
Ilya Sherman authored
This provider is preventing the AsyncInit task from ever completing, which is causing a major drop-off in Chrome OS metrics. Bug: b:165076656 Change-Id: I4d8a700b3b11a6cb9db4fddeebc75e5484a0d137 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368142 Auto-Submit: Ilya Sherman <isherman@chromium.org> Reviewed-by:
Weilun Shi <sweilun@chromium.org> Commit-Queue: Weilun Shi <sweilun@chromium.org> Commit-Queue: Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#800444}
-
Lindsay Pasricha authored
now that we'rve rolled main this is redundant. Change-Id: I11c10b7cd646d1c1405846584b5182fcc3514886 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368012Reviewed-by:
Garrett Beaty <gbeaty@chromium.org> Commit-Queue: Lindsay Pasricha <lindsayw@chromium.org> Cr-Commit-Position: refs/heads/master@{#800443}
-
Harry Cutts authored
This is part of the work described in go/cros-wheel-tick-counts, fixing code which assumes linear scrolling from wheels. Later CLs in the series will populate and use the field. On Mac, see the (very helpful) comment "Of Mice and Men" in web_input_event_builders_mac.mm for details on the axes used. Bug: 1077644 Test: run unit tests Change-Id: I74f060fb3acbc141f2d04b16068030e0e0e62ee4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2336911 Commit-Queue: Harry Cutts <hcutts@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#800442}
-
tby authored
Right now we record type metrics like this: - user action received by ash - ash sends result id to chrome - chrome re-associates id with a ChromeSearchResult object - we log the type associated with the ChromeSearchResult object However the re-association step is subject to a race condition related to whether the search result objects have been cleared from the cache. This CL changes the process to be: - user action received by ash - ash sends an AppListNotifier::Result object to chrome, containing id and type - chrome logs type directly. Note: the result id string in AppListNotifier::Result is now unused on the chrome side, but we're planning to use it for other impressions-related work soon. Bug: 1076270 Change-Id: I699f293139ac7b89cbcfe92aa9c5af017b033a48 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2365572 Commit-Queue: Tony Yeoman <tby@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Reviewed-by:
Rachel Wong <wrong@chromium.org> Cr-Commit-Position: refs/heads/master@{#800441}
-
Juliet Levesque authored
Fix the dom-repeat element typo in the Contact Tab and fixed the spacing between list elements, as seen here: https://screenshot.googleplex.com/eb1d918c-0c7a-4890-8086-8ef893ef27f4. Bug: 1093634 Change-Id: Ifc586dd982e28d3ee2853359cb8cfa8e220ceb0d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368332Reviewed-by:
Josh Nohle <nohle@chromium.org> Commit-Queue: Juliet Levesque <julietlevesque@google.com> Cr-Commit-Position: refs/heads/master@{#800440}
-
Chromium WPT Sync authored
Using wpt-import in Chromium c41b4fb5. With Chromium commits locally applied on WPT: 3b705a74 "WPT: Service Worker: Add unexpected state check to wait_for_state()" 9f52c7e4 "COOP: add reporting to redirects" f3b221b0 "[COOP] access reporting: Extend report.body.type values." Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md NOAUTOREVERT=true TBR=foolip@google.com No-Export: true Change-Id: Id2aa467bea6308cec82a7da998e57d16826bcdca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367518Reviewed-by:
WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#800439}
-
Rachel Carpenter authored
At the moment it navigates to a support.google.com link in a tab. This doesn't work offline, so utilising the help app which caches this article instead. Bug: b/157935237 Change-Id: Ibb5098b032bc959a826d52b1d05ebd7d14ab7cb3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362166 Commit-Queue: Rachel Carpenter <carpenterr@chromium.org> Reviewed-by:
Trent Apted <tapted@chromium.org> Cr-Commit-Position: refs/heads/master@{#800438}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/c060d8d65786..e689d3164f34 2020-08-20 jmadill@chromium.org Vulkan: Don't end RenderPass on DS feedback loops. 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 cnorthrop@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: None Tbr: cnorthrop@google.com Change-Id: I47980b1185a1aa197903238d9de24d1e97586e82 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368275Reviewed-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@{#800437}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/bedb605c8272..ea7fbfb9665b 2020-08-20 deadbeef@webrtc.org Implement network monitor for iOS. 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: Ie315cf1d77b624d612a09d463d345f9cbf888d78 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368539Reviewed-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@{#800436}
-
Wei-Yin Chen (陳威尹) authored
This reverts commit a1325695. Reason for revert: Android ASAN bot compilation failure. crbug.com/1120202 Original change's description: > Reland "Add -noverify to build commands to improve runtime (local builds only)" > > This reverts commit 17e2a917. > > Reason for revert: Ensure buildtools.py is a no-op on bots. > > Original change's description: > > Revert "Add -noverify to build commands to improve runtime (local builds only)" > > > > This reverts commit 132e1deb. > > > > Reason for revert: Android ASAN bot compilation failures: https://ci.chromium.org/p/chromium/builders/ci/Android%20ASAN%20%28dbg%29/26489 > > > > Original change's description: > > > Add -noverify to build commands to improve runtime (local builds only) > > > > > > The flag is guarded by treat_warnings_as_errors=false so that it > > > will apply only to local developer builds. > > > > > > Results from //tools/android/build_speed/benchmark.py base_java_sig: > > > With change: > > > base_java_sig: 68.0s avg (68.8s, 67.2s) > > > base_java_sig: 68.4s avg (68.6s, 68.2s) > > > > > > Without change: > > > base_java_sig: 69.4s avg (69.3s, 69.5s) > > > base_java_sig: 69.7s avg (69.7s, 69.7s) > > > > > > time out/Debug/bin/run_base_junit_tests: > > > With Change: > > > real 0m22.741s > > > real 0m23.543s > > > > > > Without change: > > > real 0m23.176s > > > real 0m24.328s > > > > > > Bug: 1117222 > > > Change-Id: I4bfd742165468bf9538e6fa0dc8f35daa9e0f23f > > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313299 > > > Commit-Queue: Andrew Grieve <agrieve@chromium.org> > > > Auto-Submit: Andrew Grieve <agrieve@chromium.org> > > > Reviewed-by: Peter Wen <wnwen@chromium.org> > > > Cr-Commit-Position: refs/heads/master@{#799285} > > > > TBR=wnwen@chromium.org,agrieve@chromium.org > > > > Change-Id: I82f411e5dab89c361a30c33e9103bd8561f19765 > > No-Presubmit: true > > No-Tree-Checks: true > > No-Try: true > > Bug: 1117222 > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362493 > > Reviewed-by: Hajime Hoshi <hajimehoshi@chromium.org> > > Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#799471} > > Bug: 1117222 > Change-Id: Ib43bfe72869def7da43b237360df0e155149a963 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363975 > Reviewed-by: Peter Wen <wnwen@chromium.org> > Commit-Queue: Peter Wen <wnwen@chromium.org> > Auto-Submit: Andrew Grieve <agrieve@chromium.org> > Cr-Commit-Position: refs/heads/master@{#800233} TBR=wnwen@chromium.org,agrieve@chromium.org Change-Id: I0d617bcfc7a311bfae743445fccaaab26364511e No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1117222 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368541Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Commit-Queue: Wei-Yin Chen (陳威尹) <wychen@chromium.org> Cr-Commit-Position: refs/heads/master@{#800435}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=pbommana@chromium.org Change-Id: Ia9e729229f4f9943a068fcfcb014487f44d1ad6a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367524Reviewed-by:
Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#800434}
-
Christopher Lam authored
This CL changes RulesRegistry::DeserializeAndAddRules() to bail out if the extension has been unloaded. This may have been the cause of some crashes where a ContentAction was being created for an unloaded extension. Bug: 1010336, 1115969 Change-Id: Ibbd01c1b5b0a8f4cc3c2668fbb4b804189ba0b20 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2345939 Commit-Queue: calamity <calamity@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/master@{#800433}
-
Maggie Cai authored
This reverts commit cb9cdc66. Reason for revert: This CL is likely the cause of build failure for Builder Linux Tests (dbg)(1) since https://ci.chromium.org/p/chromium/builders/ci/Linux%20Tests%20%28dbg%29%281%29/91043. Revert to see if that fix the build Original change's description: > Give blink::CueTimeline a timer for precisely handling cue events > > Cue-related events (enter, exit, cuechange) are fired up to 250ms late, > and there is a similar latency in their display which is quite > noticeable. > > The underlying problem is that we only update cues alongside the > `timeupdate` event, which is fixed at 4 Hz. > > My solution is to add a separate timer to CueTimeline > (`CueTimeline::cue_event_timer_`) which is given a timeout for the > next cue event based on the current playback position and rate. This > allows for significantly more precise cue timing accuracy without a > significant performance penalty. > > Additionally, several web tests were written with the expectation that > the 'time marches on' algorithm is run before video playback begins > (ie, upon loading text track cues). This behavior is not in accordance > with the spec (as outlined in crbug/1050767), so this CL fixes those > expectations and adds a new test to prevent regressing. > > Bug: 576310, 1050767 > Change-Id: I675f5f030a68ba9cee10e12b3e79a9b174048193 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008079 > Commit-Queue: Will Cassella <cassew@google.com> > Reviewed-by: Fredrik Söderquist <fs@opera.com> > Cr-Commit-Position: refs/heads/master@{#800148} TBR=fs@opera.com,alancutter@chromium.org,mlamouri@chromium.org,cassew@google.com Change-Id: I0563b173344cef976c16b4f2851b45762a67843f No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 576310 Bug: 1050767 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368614Reviewed-by:
Maggie Cai <mxcai@chromium.org> Commit-Queue: Maggie Cai <mxcai@chromium.org> Cr-Commit-Position: refs/heads/master@{#800432}
-
Renato Silva authored
Add a few strings that will be used for the lock screen settings. TBR=rsorokin@google.com Bug: 663982 Change-Id: I746480842436213efb40197e3efbcdb110c38dfd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367979Reviewed-by:
Renato Silva <rrsilva@google.com> Commit-Queue: Renato Silva <rrsilva@google.com> Cr-Commit-Position: refs/heads/master@{#800431}
-
Donn Denman authored
Moves the logic for whether to send the base page URL to Google servers from the C++ delegate into the Java policy class. This allows better control for Related Searches, but has no logic change. BUG=1062737 Change-Id: I8c563557eb97f736fe5cdb820dcd77d9b924f10d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366302 Commit-Queue: Donn Denman <donnd@chromium.org> Auto-Submit: Donn Denman <donnd@chromium.org> Reviewed-by:
Jinsuk Kim <jinsukkim@chromium.org> Cr-Commit-Position: refs/heads/master@{#800430}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/ab4e4feb01ac..e8dc820fbc1e 2020-08-21 enga@chromium.org Skip TextureSubresourceTest.MipmapLevelsTest on Vulkan w/ validation 2020-08-20 bryan.bernhart@intel.com D3D12: check if resource manager exists before releasing If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/dawn-chromium-autoroll Please CC cwallez@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:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel Bug: chromium:1117595 Tbr: cwallez@google.com Change-Id: If855398d377cdb4361f4f5fcd62a7d10e7f20b64 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368477Reviewed-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@{#800429}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1597946202-cb1005c445d83fc8c9db9d03ba0a749f78675139.profdata to chrome-mac-master-1597967068-f4dc3a01dd1d9ac3893254a5c720534a30d259cc.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 sebmarchand+pgo_roller@google.com,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: sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@google.com Change-Id: I782f0c9637beb97d771e42c26331a226355e4300 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368280Reviewed-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@{#800428}
-
Regan Hsu authored
* Move code that was in CellularSetupDialogUI to CellularSetupImpl so that both OsSettingsUI and CellularSetupDialogUI can use it. * Bind OsSettingsUI to mojo interface. * Add cellular setup localized strings to internet section so they will be displayed in the shared UI. Bug: 1093185 Change-Id: I044e8af8f1cee07a1dda1d7ee0ada38e2c3fe6d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2349389Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Reviewed-by:
Azeem Arshad <azeemarshad@chromium.org> Commit-Queue: Regan Hsu <hsuregan@chromium.org> Cr-Commit-Position: refs/heads/master@{#800427}
-
Elly Fong-Jones authored
This method has no overrides and always returns true. This change removes it, removes the only call to it, and simplifies code around that call site as a result. Bug: None Change-Id: I2c5b13552923f11615e5b2e629fc2da70fb26eb8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367650 Commit-Queue: Robert Liao <robliao@chromium.org> Reviewed-by:
Robert Liao <robliao@chromium.org> Cr-Commit-Position: refs/heads/master@{#800426}
-
Mike Reed authored
See https://skia-review.googlesource.com/c/skia/+/312248 Change-Id: I49dec4ff0e6f19329e300eb6e94b209790229985 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367441Reviewed-by:
Florin Malita <fmalita@chromium.org> Reviewed-by:
Philip Rogers <pdr@chromium.org> Commit-Queue: Mike Reed <reed@google.com> Cr-Commit-Position: refs/heads/master@{#800425}
-
Pranav Batra authored
Add Linux support for PPD resolution options. Test: ./printing_unittests Change-Id: I15d2245567e37938633c72daa2edc66cfa6f4b22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360472 Commit-Queue: Pranav Batra <batrapranav@chromium.org> Reviewed-by:
Daniel Hosseinian <dhoss@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#800424}
-
chinsenj authored
Currently a user can only cycle the window cycle list using alt+tab or alt+shift+tab. Also, the user can only confirm their selection by releasing the alt key. This CL improves the interactivity of window cycler by introducing the following changes. Pressing the left and right arrows now move the selection while the window cycler is open. Pressing enter or space now confirms the selection. WindowCycleControllerTest.KeysConfirmSelection Test: WindowCycleControllerTest.LeftRightCycle, Bug: 1067327 Change-Id: I03682c5545bf82415b9e71a4814bf5c1b0c196bc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2358586 Commit-Queue: Jeremy Chinsen <chinsenj@chromium.org> Reviewed-by:
Sammie Quon <sammiequon@chromium.org> Reviewed-by:
Xiaoqian Dai <xdai@chromium.org> Cr-Commit-Position: refs/heads/master@{#800423}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/56d9df4fa53f..77419b0f04e8 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-mac-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: I216e344fa665ab514a8993a559b6ef10fd0f1efb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367972Reviewed-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@{#800422}
-
James Hawkins authored
Bug: 1045266 Test: NetworkComponentsNetworkPropertyListMojoTest* Change-Id: I14e9be994b77445a4106b156fcce3e48421c340b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368494 Auto-Submit: James Hawkins <jhawkins@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Commit-Queue: Kyle Horimoto <khorimoto@chromium.org> Commit-Queue: James Hawkins <jhawkins@chromium.org> Cr-Commit-Position: refs/heads/master@{#800421}
-
Sunny Sachanandani authored
This reverts commit 9d22b694. Reason for revert: Broke non-overlay video playback: crbug.com/1119666 Original change's description: > Use shared images with DX11 video decoder > > This change enables support for SkiaRenderer. In a future change, > GLRenderer will also be supported. > > Change-Id: I760013fdd163dcec3e3fe5d888541f07849749c7 > Bug: 1011555 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2250890 > Auto-Submit: Bryan Bernhart <bryan.bernhart@intel.com> > Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org> > Reviewed-by: Frank Liberato <liberato@chromium.org> > Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org> > Cr-Commit-Position: refs/heads/master@{#794763} TBR=sunnyps@chromium.org,liberato@chromium.org,bryan.bernhart@intel.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1011555, 1119666, 1120094 Change-Id: Ie5fb291ea7093d3d695433181583302a36ecd88d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368240Reviewed-by:
Sunny Sachanandani <sunnyps@chromium.org> Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org> Cr-Commit-Position: refs/heads/master@{#800420}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/bbb2038a3f14..bb85de36d277 2020-08-21 dpranke@google.com Fix visibility on //xfa:xfa_warnings. 2020-08-20 tsepez@chromium.org Fix initialziation of XFA fuzzers against CPPGC heap. 2020-08-20 tsepez@chromium.org Make CFWL_Message and its subclasses stack-only types. 2020-08-20 tsepez@chromium.org Rename class CFX_FontSourceEnum_File to CFGAS_FontSourceEnumFile. 2020-08-20 thestig@chromium.org Reduce nesting in RelocateTableRowCells(). 2020-08-20 tsepez@chromium.org Garbage collect the FWL layer objects. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pdfium-autoroll Please CC pdfium-deps-rolls@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: chromium:1119533 Tbr: pdfium-deps-rolls@chromium.org Change-Id: I63b2fa2c3e5d834eb308ad1f92b8e7cf96a90eb3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368278Reviewed-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@{#800419}
-
Ian Kilpatrick authored
Additionally simplify the logic with SetMinimumSizeIfAuto. There should be no behaviour change. Change-Id: I9baf6d3737fc2d0de5531b7f02a53f425d3ccb94 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2365313 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Reviewed-by:
Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#800418}
-
Yuki Yamada authored
This reverts commit 351529d8. Reason for revert: This CL was intended to be reverted before M86 branch cutoff Original change's description: > Reland "Reland "Change HeapObserverList to HeapObserverSet"" > > This is a reland of 944fde32. > It was reverted because WebSocketChannelImpl::ProcessSendQueue() > accessed an unbound HeapMojoRemote, which was guaranteed to be bound > without this CL. > The issue was fixed in another CL: https://crrev.com/c/2362042 > > Original change's description: > > Reland "Change HeapObserverList to HeapObserverSet" > > > > This is a reland of f29d2ae1 > > > > ExecutionContext::NotifyContextDestroyed() has relied on the > > deterministic iteration order of ObserverList, so landing the original > > CL caused a problem. It is fixed in another CL: > > https://crrev.com/c/2352588 > > > > Original change's description: > > > Change HeapObserverList to HeapObserverSet > > > > > > The previous CL for HeapObserverList https://crrev.com/c/2060348 > > > addressed two things: changing HeapObserverList to HeapObserverSet and > > > allowing removal while iteration, and was reverted for performance > > > reasons. This CL only does the former and avoids performance > > > implications of the latter. > > > > > > This CL is for migration of NewLinkedHashSet. > > > See: https://crrev.com/c/2134039 > > > > > > Bug: 1100257 > > > Change-Id: I2426d14d77a68f200bf1398b16638e1605dd4ff1 > > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2319087 > > > Commit-Queue: Yuki Yamada <yukiy@chromium.org> > > > Reviewed-by: Keishi Hattori <keishi@chromium.org> > > > Reviewed-by: Kentaro Hara <haraken@chromium.org> > > > Reviewed-by: Bartek Nowierski <bartekn@chromium.org> > > > Cr-Commit-Position: refs/heads/master@{#797115} > > > > Bug: 1100257, 1115411 > > Change-Id: Id8e1b9a4141777de89bbc471f6ac8c6508a0adff > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352292 > > Commit-Queue: Yuki Yamada <yukiy@chromium.org> > > Reviewed-by: Bartek Nowierski <bartekn@chromium.org> > > Reviewed-by: Keishi Hattori <keishi@chromium.org> > > Reviewed-by: Kentaro Hara <haraken@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#798576} > > Bug: 1100257 > Bug: 1115411 > Change-Id: I796232c723d4295599832672c9eeedc8e979e757 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2359657 > Commit-Queue: Yuki Yamada <yukiy@chromium.org> > Reviewed-by: Bartek Nowierski <bartekn@chromium.org> > Reviewed-by: Kentaro Hara <haraken@chromium.org> > Cr-Commit-Position: refs/heads/master@{#800048} TBR=haraken@chromium.org,keishi@chromium.org,yukiy@chromium.org,bartekn@chromium.org Change-Id: I7070e33c597991a997d5cf81be59b7bbe64d3b46 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1100257 Bug: 1115411 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367255Reviewed-by:
Yuki Yamada <yukiy@chromium.org> Reviewed-by:
Bartek Nowierski <bartekn@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Yuki Yamada <yukiy@chromium.org> Cr-Commit-Position: refs/heads/master@{#800417}
-
Kent Tamura authored
This is a reland of f1a2ccf7 This CL has no differences from the original CL. The original CL caused some memory regressions in system_health.memory_mobile, and had memory improvement in some stories. We decided not to fix the regressions. Original change's description: > Enable LayoutNG for BUTTON elements and INPUT buttons by default > > Bug: 1040826 > Change-Id: I0a2f9db962e74a44758293e0711009617e6a42d3 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354119 > Commit-Queue: Kent Tamura <tkent@chromium.org> > Commit-Queue: Koji Ishii <kojii@chromium.org> > Auto-Submit: Kent Tamura <tkent@chromium.org> > Reviewed-by: Koji Ishii <kojii@chromium.org> > Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> > Cr-Commit-Position: refs/heads/master@{#797991} Bug: 1040826, 1078327 Change-Id: I6cfa6183571fe6c6816be09d8ef0c7110c5c45cd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368612 Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#800416}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/6a9a910fd2c3..bedb605c8272 2020-08-20 hta@webrtc.org Transition ICE gathering state to "new" once all transports go away 2020-08-20 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 7a8fca54..4591d36d (800031:800155) 2020-08-20 jasonlon@google.com DTMF Event Sub-API on VoIP API 2020-08-20 minyue@webrtc.org Send estimated capture clock offset when sending Abs-capture-time RTP header extension. 2020-08-20 peah@webrtc.org Removing call to deprecated SetExtraOptions method 2020-08-20 jakobi@webrtc.org Reland "Call OnReceivedOverhead after audio network adaptor is created." 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: chromium:1086942,chromium:1115080 Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I83400f9b3e8330520c56322d3a2fa9cd32094ee1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368433Reviewed-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@{#800415}
-
Bo Majewski authored
DISALLOW_COPY_AND_ASSIGN macro is deprecated as indicated on the review of CL 2251524. Bug: 1111229 Change-Id: Ib25ce85a8ace16b8eb7b00a0974fec5a73e536fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362364Reviewed-by:
calamity <calamity@chromium.org> Commit-Queue: Bo Majewski <majewski@chromium.org> Cr-Commit-Position: refs/heads/master@{#800414}
-
Yuke Liao authored
This CL cleans up linux-lacros-compile-rel as it has been replaced by linux-lacros-rel. Bug: 1116180 Change-Id: I617527f1a36250edb506e47952b463e564f73379 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368473Reviewed-by:
Sven Zheng <svenzheng@chromium.org> Commit-Queue: Yuke Liao <liaoyuke@chromium.org> Cr-Commit-Position: refs/heads/master@{#800413}
-
Dana Fried authored
It feels weird to be able to drag the toolbar down in order to open the tabstrip tray in tablet mode but not drag up to close. This makes it possible to start a drag or fling with either the tray open or closed as long as the initial direction of the motion is correct (otherwise, the event is processed as normal). So for example, dragging or flinging down when the tray is closed, or dragging or flinging upwards when the tray is open will cause the tray to move, but not vice-versa. Bug: 1116651 Change-Id: I815d1ff189c28feb7fd6c81181e85ae37767a7ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2361122Reviewed-by:
Collin Baker <collinbaker@chromium.org> Commit-Queue: Dana Fried <dfried@chromium.org> Cr-Commit-Position: refs/heads/master@{#800412}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/cbfd396756c6..44e1791f100c 2020-08-20 srisser@google.com Add getPhysicalDeviceFeatures2 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: Id99ecc711a7e5904d1e57a8605d92c11aefba234 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367782 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@{#800411}
-
Yuke Liao authored
This CL disables retrying invalid shards in coverage build. Bug: 1119972 Change-Id: If0679948a745f5897835ebd823d3201fcfcb661e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368235Reviewed-by:
Stephen Martinis <martiniss@chromium.org> Commit-Queue: Yuke Liao <liaoyuke@chromium.org> Cr-Commit-Position: refs/heads/master@{#800410}
-