- 05 Mar, 2018 40 commits
-
-
Marina Ciocea authored
Bug: 788657 Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Change-Id: Idb284c691eec3b6c468431c2a16ae2a7977211cf Reviewed-on: https://chromium-review.googlesource.com/921281Reviewed-by:
Olga Sharonova <olka@chromium.org> Reviewed-by:
Max Morin <maxmorin@chromium.org> Commit-Queue: Marina Ciocea <marinaciocea@chromium.org> Cr-Commit-Position: refs/heads/master@{#540812}
-
Alexander Timin authored
WorkQueue class has work_queue_ field, which is confusing. Rename it to tasks_. R=alexclarke@chromium.org,skyostil@chromium.org Change-Id: Ibdf4c69cf29a9ffbd48205fac1cd9b20c92f7a13 Reviewed-on: https://chromium-review.googlesource.com/897525 Commit-Queue: Alexander Timin <altimin@chromium.org> Reviewed-by:
Alex Clarke <alexclarke@chromium.org> Reviewed-by:
Sami Kyöstilä <skyostil@chromium.org> Cr-Commit-Position: refs/heads/master@{#540811}
-
Alexander Timin authored
Follow-up for comments in 939469. R=haraken@chromium.org Change-Id: I7ff56c9ef77a7174c8e6cc2e3a9a91faebff2ed2 Reviewed-on: https://chromium-review.googlesource.com/941327Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Alexander Timin <altimin@chromium.org> Cr-Commit-Position: refs/heads/master@{#540810}
-
Greg Thompson authored
6.7.1 and newer are failing CFI builds. BUG=818611 TBR=grt@chromium.org Change-Id: Ie0439da3fd330a8814daee9f3da3e2c412fbbf6f Reviewed-on: https://chromium-review.googlesource.com/948485Reviewed-by:
Greg Thompson <grt@chromium.org> Commit-Queue: Greg Thompson <grt@chromium.org> Cr-Commit-Position: refs/heads/master@{#540809}
-
Kent Tamura authored
This reverts commit 5c7dc5f2. Reason for revert: Broke Linux x64 clobber build. Original change's description: > Apply snake_case to generated files in gen/blink/core/css/properties/*/. > > Generated files in these directories are often identical to other > checked-in files. It's difficult to make move_blink_source.py workable > in such situation. So, this CL renames these generated files beforehand. > > This CL has no behavior changes. > > Bug: 770603 > Change-Id: I3bf2312b7a238fe605e33a9217959d84d43ffb4f > Reviewed-on: https://chromium-review.googlesource.com/947546 > Reviewed-by: nainar <nainar@chromium.org> > Commit-Queue: Kent Tamura <tkent@chromium.org> > Cr-Commit-Position: refs/heads/master@{#540796} TBR=tkent@chromium.org,nainar@chromium.org Change-Id: I5203839d03f67e7b28098c051803769ed3fa817a No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 770603 Reviewed-on: https://chromium-review.googlesource.com/948643Reviewed-by:
Kent Tamura <tkent@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#540808}
-
François Beaufort authored
This CL makes sure document.pictureInPictureEnabled always returns false and video.requestPictureInPicture() rejects if PictureInPicture and UseSurfaceLayerForVideo features are not enabled. Bug: 806249 Change-Id: Icc91903aa0f44dde577ce479a8d5d453952e6575 Reviewed-on: https://chromium-review.googlesource.com/937301 Commit-Queue: François Beaufort <beaufort.francois@gmail.com> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Cr-Commit-Position: refs/heads/master@{#540807}
-
Greg Thompson authored
This is a tentative care to silence all flaky tests. We have found all the tests using the test mount point info are flaky affecting the trybot runs every time. So we'll disable all the affected test before fixing the root cause. TBR=yamaguchi@chromium.org Bug: 804413 Change-Id: I7f711446accc61a8bedf00f52c328a1037a11791 Reviewed-on: https://chromium-review.googlesource.com/948483Reviewed-by:
-
François Beaufort authored
The "media.autoplay_allowed" preference can be set to allow autoplay as a Chrome Policy. It is meant to be used for internal websites that may be broken by the change described at chromium.org/audio-video/autoplay. Bug: 779087 Change-Id: I6a2b5a13e80adfc72056536bc9cf425e30f50e6a Reviewed-on: https://chromium-review.googlesource.com/941956 Commit-Queue: François Beaufort <beaufort.francois@gmail.com> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Reviewed-by:
-
Alex Clarke authored
This optionally sets initial_virtual_time and beginFrameControl. Change-Id: I6a0d6237137dbda57578a92b5abb4f160049ac20 Reviewed-on: https://chromium-review.googlesource.com/937402 Commit-Queue: Alex Clarke <alexclarke@chromium.org> Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Reviewed-by:
Eric Seckler <eseckler@chromium.org> Cr-Commit-Position: refs/heads/master@{#540804}
-
Eric Seckler authored
crbug.com/817364 is fixed, so we don't need to take double screenshots anymore. Bug: 817364 Change-Id: Ie5e467d21858dcec1f8fb52d4ff52df7c2edd472 Reviewed-on: https://chromium-review.googlesource.com/948484Reviewed-by:
-
Marc Treib authored
This CL removess the two features CaptureThumbnailDependingOnTransitionType and CaptureThumbnailOnNavigatingAway and updates all the places that checked them. Bug: 765588 Change-Id: Iaf4756410093d7ffb9caef7a9a221ebd9c62efe4 Reviewed-on: https://chromium-review.googlesource.com/943042Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Commit-Queue: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#540802}
-
Greg Thompson authored
BUG=818603 TBR=jamescook@chromium.org Change-Id: Icaa17e76bfa8067091870ddb818b89210866ce30 Reviewed-on: https://chromium-review.googlesource.com/947975Reviewed-by:
-
Gustav Sennton authored
We need to keep the names of all boundary interface classes and methods used by the support library and chromium to ensure their names are the same in the support library as in the WebView APK. However, utility classes in the boundary interface package can be obfuscated just fine since they are not part of the boundary interface API. Ideally then, we will put everything that is part of the boundary interface API in one specific package, and keep utility methods in a sub-package, to allow for simple proguard rules (and avoid bugs where we incorrectly keep/remove new boundary interfaces). Bug: 809471 Change-Id: I7a700fcc50998d83bf3bfa799196477289bedb3e Reviewed-on: https://chromium-review.googlesource.com/943504Reviewed-by:
agrieve <agrieve@chromium.org> Reviewed-by:
Richard Coles <torne@chromium.org> Commit-Queue: Gustav Sennton <gsennton@chromium.org> Cr-Commit-Position: refs/heads/master@{#540800}
-
Marina Ciocea authored
Following discussion from [1], I updated DebugRecordingFileProvider interface to take stream type and ID instead of FilePath suffix as input, and build file suffix in interface implementation. This CL introduces duplicate code in media/audio/audio_debug_recording_session_impl.cc, that will be removed after switching to mojo implementation [2]. [1] https://crrev.com/c/810809/40/services/audio/public/mojom/debug_recording.mojom#18 [2] https://crrev.com/c/921281 Bug: 788657 Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Change-Id: I2e656797be3ca4663eb9393e74df7a73785e02a2 Reviewed-on: https://chromium-review.googlesource.com/941949 Commit-Queue: Marina Ciocea <marinaciocea@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
-
Christopher Cameron authored
It used to be a valid assumption that ui::Compositors would be destroyed before BrowserCompositorMac::DisableRecyclingForShutdown was called, but changes to NSWindows' lifetimes have made that assumption no longer valid. Destroy all BrowserCompositorMac instances at that call. Make relevant methods on RenderWidgetHostViewCocoa and RenderWidgetHostViewMac early-out when the BrowserCompositorMac is gone. Bug: 805726 Change-Id: I429b6b546344a23cd93e64dae4a004065328d5a6 Reviewed-on: https://chromium-review.googlesource.com/947813 Commit-Queue: ccameron <ccameron@chromium.org> Reviewed-by:
Trent Apted <tapted@chromium.org> Cr-Commit-Position: refs/heads/master@{#540798}
-
Alex Clarke authored
Change-Id: I17932c9db2e9c42ca0cef4eccd063cb61b9ff123 Reviewed-on: https://chromium-review.googlesource.com/947943Reviewed-by:
-
Kent Tamura authored
Generated files in these directories are often identical to other checked-in files. It's difficult to make move_blink_source.py workable in such situation. So, this CL renames these generated files beforehand. This CL has no behavior changes. Bug: 770603 Change-Id: I3bf2312b7a238fe605e33a9217959d84d43ffb4f Reviewed-on: https://chromium-review.googlesource.com/947546Reviewed-by:
nainar <nainar@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#540796}
-
Yutaka Hirano authored
TBR=grt@chromium.org Bug: 818167 Change-Id: I2b32ad5308e51f4da39947d1f3b631587b2fe2d3 Reviewed-on: https://chromium-review.googlesource.com/948402Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#540795}
-
https://webrtc.googlesource.com/src.git/+log/12c8110e8c71..3ba7a57f8fff $ git log 12c8110e8..3ba7a57f8 --date=short --no-merges --format='%ad %ae %s' Created with: roll-dep src/third_party/webrtc BUG=None,None,None The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng;master.tryserver.chromium.win:win-msvc-dbg TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: Ib2e051f77dad5c01e99f97abf8d3212d09419f21 Reviewed-on: https://chromium-review.googlesource.com/948269 Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#540794}
-
Bence Béky authored
Change-Id: I2c14a7c94d55b38b303a6b827fd5d1d06a8feca4 Reviewed-on: https://chromium-review.googlesource.com/946151 Commit-Queue: Adam Rice <ricea@chromium.org> Reviewed-by:
Adam Rice <ricea@chromium.org> Cr-Commit-Position: refs/heads/master@{#540793}
-
Max Morin authored
fuchsia_audio_manager_free should be called, I think. Bug: None Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Change-Id: I58bc4b9fb00fcd1d9d074752ddc8d59777911d6a Reviewed-on: https://chromium-review.googlesource.com/945913Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Commit-Queue: Max Morin <maxmorin@chromium.org> Cr-Commit-Position: refs/heads/master@{#540792}
-
Tien-Ren Chen authored
The paint rect for background in scrolling content layer should be expanded to the full scrollable rect, i.e. layout overflow rect. This CL fixes a bug in BoxPainter and BoxPaintInvalidator that we forgot to convert LayoutBox::LayoutOverflowRect() from flipped coordinates to physical coordinates for painting and invalidation. BUG=787666 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: I4b4c45e910ea1d860e61eece6005263d0a8c708e Reviewed-on: https://chromium-review.googlesource.com/942485 Commit-Queue: Tien-Ren Chen <trchen@chromium.org> Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
Steve Kobes <skobes@chromium.org> Cr-Commit-Position: refs/heads/master@{#540791}
-
Mikel Astiz authored
Trivial change, no behavioral differences. Bug: 681921 Change-Id: Id512b11a574afcf902d35553bb10a1a85cbcdea7 Reviewed-on: https://chromium-review.googlesource.com/940134Reviewed-by:
Sean Kau <skau@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Pavel Yatsuk <pavely@chromium.org> Commit-Queue: Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#540790}
-
Yutaka Hirano authored
The test has succeeded unexpectedly, so this CL also adds an expectation file. Bug: 812667 Change-Id: I649a7663c54f83ccb951c5a4bf075b588908b088 Reviewed-on: https://chromium-review.googlesource.com/948184 Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#540789}
-
Ned Nguyen authored
Owners no longer use this benchmark Change-Id: Ic544da522fb68ffe85da5cd777da2dc314f82fc8 Reviewed-on: https://chromium-review.googlesource.com/948245Reviewed-by:
Kenichi Ishibashi <bashi@chromium.org> Reviewed-by:
Yuki Shiino <yukishiino@chromium.org> Commit-Queue: Ned Nguyen <nednguyen@google.com> Cr-Commit-Position: refs/heads/master@{#540788}
-
This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 The AutoRoll server is located here: https://afdo-chromium-roll.skia.org Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=gbiv@chromium.org Change-Id: I807f89abb3cc9a7896ae7c5252a124ce4e1afbb7 Reviewed-on: https://chromium-review.googlesource.com/948265 Commit-Queue: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#540787}
-
Zhuoyu Qian authored
IsAmbiguousBoundaryCharacter() only used in SpellChecker.cpp, move it from EditingUtilities to SpellChecker.cpp for better code structure. Bug: 802922 Signed-off-by:
Zhuoyu Qian <zhuoyu.qian@samsung.com> Change-Id: Ie86aed1551481312544c2471dac2068199e5cd65 Reviewed-on: https://chromium-review.googlesource.com/945350Reviewed-by:
Xiaocheng Hu <xiaochengh@chromium.org> Cr-Commit-Position: refs/heads/master@{#540786}
-
Chromium WPT Sync authored
Using wpt-import in Chromium 533c6272. Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/13319 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 Directory owners for changes in this CL: rouslan@chromium.org, mathp@chromium.org: external/wpt/payment-request TBR=qyearsley No-Export: true Change-Id: Ib7f68d4e9b7a3ad2e9141d02804f70df9c05ccd9 Reviewed-on: https://chromium-review.googlesource.com/947837 Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Reviewed-by:
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Cr-Commit-Position: refs/heads/master@{#540785}
-
Zhuoyu Qian authored
This patch makes EditorParagraphSeparator to be an enum class for better type safety. Bug: Signed-off-by:
Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#540784}
-
Makoto Shimazu authored
This reverts commit ace9aca7. The test actually crashes only when DCHECK is on. The difference from the original patch is adding -expected.txt file and changing [ Crash ] to [ Crash Pass ]. TBR=falken@chromium.org Bug: 771815 Change-Id: I9354c80c6e1478160214151065f6f0cbf25ad862 Reviewed-on: https://chromium-review.googlesource.com/948242Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Commit-Queue: Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#540783}
-
Peter Collingbourne authored
Bug: 749784 Change-Id: I8ae48e1b1080ddeef87faafc7fad8f40ddb01126 Reviewed-on: https://chromium-review.googlesource.com/947715Reviewed-by:
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=amineer@chromium.org Change-Id: I8fdb21a1682cbb9e2937556d521db77b6b410f55 Reviewed-on: https://chromium-review.googlesource.com/947838Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#540781}
-
Hitoshi Yoshida authored
REASON OF RELAND: The issue was out of Chromium repository, and run on only Chrome official build. Hence I revert the chagne in merger.py, not to check v8_context_snapshot.bin. Original CL is https://chromium-review.googlesource.com/c/chromium/src/+/923683 This CL makes it possible to create and use V8 context snapshot files on Android, if a developer puts "use_v8_context_snapshot=true" The V8 context snapshot feature is currently supported and enabled on Windows, MacOSX, and Linux (not ChromeOS), and its Finch experiment showed 20% reduction of time to create V8 contexts. On local Android machine, this feature shows 50% time recution. Beside it, in order to enable the feature on cross-build platforms like Android, we have to build Blink twice. So this CL does not flip the flag |use_v8_context_snapshot|. FYI, some numbers with the feature are written in the next CL; https://chromium-review.googlesource.com/c/chromium/src/+/923623 TBR=caitkp,kuniko,nyquist,rockot,haraken,mkwst Bug: 764576, 817288 Change-Id: Id819aa2d4762e04bd7a9b4f700603d89ee0fe5dd Reviewed-on: https://chromium-review.googlesource.com/945248Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Reviewed-by:
Xiaohan Wang <xhwang@chromium.org> Reviewed-by:
Tao Bai <michaelbai@chromium.org> Commit-Queue: Hitoshi Yoshida <peria@chromium.org> Cr-Commit-Position: refs/heads/master@{#540780}
-
Koji Ishii authored
Following bot results are included. 4034 4035 4036 4040 4041 4044 4045 4046 4047 4048 4049 4050 4051 4052 4053 4054 25 lines were removed and 18 lines were deflaked by consecutive results since 3993. TBR=eae@chromium.org NOTRY=true Bug: 591099 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: I32758809317e7fe8a2504de939f1620775f30076 Reviewed-on: https://chromium-review.googlesource.com/945038 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#540779}
-
Tatsuhisa Yamaguchi authored
This will protect mounted zip file caches from the disk cleanup logic. Bug: 816928 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I73d36a2317d643fdbbc74c342960b027b99dddb0 Reviewed-on: https://chromium-review.googlesource.com/940645 Commit-Queue: Tatsuhisa Yamaguchi <yamaguchi@chromium.org> Reviewed-by:
Michael Giuffrida <michaelpg@chromium.org> Reviewed-by:
Jesse Doherty <jwd@chromium.org> Reviewed-by:
Yuki Awano <yawano@chromium.org> Cr-Commit-Position: refs/heads/master@{#540778}
-
Matt Falkenhagen authored
CompositorImageAnimation changed some timings and the resource was not yet cached when the test was expecting it to be. I've rearranged the test and it seems to pass reliably now on Linux: it passes 100 iterations whereas it would fail within 10 iterations previously. R=nhiroki Bug: 813468 Change-Id: I5b76353f90e728981922c325486fa1700e85f73e Reviewed-on: https://chromium-review.googlesource.com/945708 Commit-Queue: Matt Falkenhagen <falken@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#540777}
-
Yutaka Hirano authored
It's flaky with --enable-features=NetworkService. Bug: 818445 Change-Id: I42bcd27471d03f497989ee8181208e2c043c6099 Tbr: jam@chromium.org Reviewed-on: https://chromium-review.googlesource.com/948162Reviewed-by:
-
Gyuyoung Kim authored
Most of the callers of ReleaseFreeMemory() have been usually invoking ClearMemory() together. So it would be good if we call ClearMemory() inside ReleaseFreeMemory(). It will help to return more free memory through ReleaseFreeMemory(). This CL makes ReleaseFreeMemory() purge more free memory through calling ClearMemory(). But this CL just calls SkGraphics::PurgeAllCaches() directly, since ClearMemory() doesn't do much stuff. And, this CL removes ClearMemory() that is no longer needed. The test case is implemented by referring to RenderThreadImplDiscardableMemoryBrowserTest.ReleaseFreeDiscardableMemory(). It calls RenderThreadImpl::ReleaseFreeMemory through a fake memory pressure notification. Besides RenderThreadImplClearMemoryBrowserTest.MAYBE_ClearMemory should be also removed because ClearMemory() is removed. Test: RenderThreadImplDiscardableMemoryBrowserTest.ReleaseFreeMemory() Bug: None Change-Id: If82e204b6d8785e8d97cd57fe7eac9f0f852a7a8 Reviewed-on: https://chromium-review.googlesource.com/945748 Commit-Queue: Gyuyoung Kim <gyuyoung.kim@lge.com> Reviewed-by:
-
Jinsuk Kim authored
The API was used to collect UMA stat on mobile-friendly pages for DOM distiller (reader mode) project. It can now be deleted. Bug: 598880 Change-Id: Ia922743fc6294bd57c7a92d71dc1678ce651c843 Reviewed-on: https://chromium-review.googlesource.com/945348Reviewed-by:
Maria Khomenko <mariakhomenko@chromium.org> Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Cr-Commit-Position: refs/heads/master@{#540774}
-
Will Harris authored
BUG=803621 Change-Id: I2a028ce864808a88f71c0b0a0e0d3f493e0f1f77 Reviewed-on: https://chromium-review.googlesource.com/940616Reviewed-by:
Steven Holte <holte@chromium.org> Commit-Queue: Will Harris <wfh@chromium.org> Cr-Commit-Position: refs/heads/master@{#540773}
-
