- 14 May, 2018 19 commits
-
-
Joel Hockey authored
Change-Id: I107242a7118b5eaa0300c5a04c3ac48edf60dc5f Reviewed-on: https://chromium-review.googlesource.com/1056650Reviewed-by:
Nicholas Verne <nverne@chromium.org> Commit-Queue: Joel Hockey <joelhockey@chromium.org> Cr-Commit-Position: refs/heads/master@{#558185}
-
Kent Tamura authored
Change-Id: I7d22ee25a4b4b55e4de846db6ec79919e703ac3e Reviewed-on: https://chromium-review.googlesource.com/1051185Reviewed-by:
Quinten Yearsley <qyearsley@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#558184}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=mmoss@chromium.org Change-Id: I0950d5fe5966d56308402c65300e6466bb32f0eb Reviewed-on: https://chromium-review.googlesource.com/1056022Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#558183}
-
Kunihiko Sakamoto authored
This adds a parser for the CBOR certificate chain format defined in [1]. SignedExchangeCertificateChain::Parse() takes a version enum and selects a parser to use. For now, the new parser is used only by tests. [1] https://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-responses.html#cert-chain-format Bug: 815024,815025 Change-Id: Ia554ad3d086dbecd20294bdb6db03f37b60d67d9 Reviewed-on: https://chromium-review.googlesource.com/1002412 Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Tsuyoshi Horo <horo@chromium.org> Cr-Commit-Position: refs/heads/master@{#558182}
-
Sam McNally authored
The file manager app queries the team-drives flag asynchronously, but may use its value before the response arrives, causing team drives to be enabled non-deterministically. Wait for the flag value to arrive before using its value to avoid this race. Bug: 723977 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: Ic21f0833082be2ae8d297245fc6849a33e0b4058 Reviewed-on: https://chromium-review.googlesource.com/1053929Reviewed-by:
Sasha Morrissey <sashab@chromium.org> Commit-Queue: Sam McNally <sammc@chromium.org> Cr-Commit-Position: refs/heads/master@{#558181}
-
Eric Robinson authored
The pop-up string has been replaced with pop-ups and redirects. I've removed the old string, which will no longer be referenced after crrev.com/c/1047687. Bug: 840356 Change-Id: Iaf65ce22e3296215f27d25dfa7b7a81b0c605758 Reviewed-on: https://chromium-review.googlesource.com/1053953Reviewed-by:
Patti <patricialor@chromium.org> Commit-Queue: Eric Robinson <ericrobinson@chromium.org> Cr-Commit-Position: refs/heads/master@{#558180}
-
Xiaocheng Hu authored
This patch refactors bidi adjustment code in SelectonController by introducing ShouldAdjustBase/ExtentAtBidiBoundary(), so that adjustment criteria and adjustment result computation are separated. Bug: 811502 Change-Id: I197322426f1f108c9aeae971c599b5bff5a7fc46 Reviewed-on: https://chromium-review.googlesource.com/1053122Reviewed-by:
Yoichi Osato <yoichio@chromium.org> Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> Cr-Commit-Position: refs/heads/master@{#558179}
-
Eric Robinson authored
This CL is the first step in having NotifyResult select the check with the highest priority. In order to do that (and not store intermediate data), all of the checks must have finished prior to NotifyResult being called. This *may* regress performance, and we should track the potential regression in SubresourceFilter.PageLoad.SafeBrowsingDelay. Bug: 823414 Change-Id: I1339e3795e9178dd7dd789ac98fcd21a2b76d726 Reviewed-on: https://chromium-review.googlesource.com/984672 Commit-Queue: Eric Robinson <ericrobinson@chromium.org> Reviewed-by:
Varun Khaneja <vakh@chromium.org> Reviewed-by:
Asanka Herath <asanka@chromium.org> Reviewed-by:
Charlie Harrison <csharrison@chromium.org> Cr-Commit-Position: refs/heads/master@{#558178}
-
Charlie Harrison authored
This information is no longer being used anywhere. TBR=avi@chromium.org Bug: 842337 Change-Id: Iacdffd68df415a90ffe1b2c63971bd2c327d5cb0 Reviewed-on: https://chromium-review.googlesource.com/1056167 Commit-Queue: Charlie Harrison <csharrison@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Helen Li <xunjieli@chromium.org> Cr-Commit-Position: refs/heads/master@{#558177}
-
Noel Gordon authored
Allows use to group "tabindex*" tests together (and eventually get rid of the FileManagerBrowserTestWithLegacyEventDisapatch class). Bug: 836254 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: Ifd4c81458e853799e8a59e1185f8745fb27f8da8 Reviewed-on: https://chromium-review.googlesource.com/1056768Reviewed-by:
Stuart Langley <slangley@chromium.org> Commit-Queue: Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#558176}
-
Timothy Loh authored
This CL adds a LauncherCrostiniAppUpdater that ensures the Shelf knows about app uninstallation so it can remove pinned Crostini apps. TEST=Manually uninstalled an app and saw the pin disappear. Manually uninstalled Crostini and saw pins disappear. Bug: 839699 Change-Id: I81e6b60414ad8766ef159a9ea3969809beb5112c Reviewed-on: https://chromium-review.googlesource.com/1046605Reviewed-by:
Stefan Kuhne <skuhne@chromium.org> Commit-Queue: Timothy Loh <timloh@chromium.org> Cr-Commit-Position: refs/heads/master@{#558175}
-
Sergei Datsenko authored
Default parameters are determined by the CrosDisks, it's not up to the client to decide which ones are the "default" so it ignores those anyway. BUG=chromium:831491 Change-Id: Ibb8cc66b318282b15bfcb361a6428e37028dcf37 Reviewed-on: https://chromium-review.googlesource.com/1053343 Commit-Queue: Sergei Datsenko <dats@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Reviewed-by:
Sam McNally <sammc@chromium.org> Cr-Commit-Position: refs/heads/master@{#558174}
-
Bence Béky authored
Remove SpdyNetworkTransactionTest.ServerPushBeforeHeaders, because this case is covered by SpdyNetworkTransactionPushTest.*/0. Remove SpdyNetworkTransactionTest.ServerPushInvalidCrossOrigin, because this case is covered by SpdyNetworkTransactionTest.ServerPushCrossOriginCorrectness. Change ServerPushCrossOriginCorrectness into a parametrized subclass, just like SpdyNetworkTransactionPushTest. For clarity, rename SpdyNetworkTransactionPushTest to SpdyNetworkTransactionPushHeaderTest, ServerPushCrossOriginCorrectness to SpdyNetworkTransactionPushUrlTest, and use PushHeaderTestParams and PushHeaderUrlParams as test data struct name, respectively. This will make it much easier to add tests for an upcoming histogram. Bug: 831536 Change-Id: I298fbd9a2dd4b6567b8cb597fcb704b956819218 Reviewed-on: https://chromium-review.googlesource.com/1055751 Commit-Queue: Bence Béky <bnc@chromium.org> Reviewed-by:
Ryan Hamilton <rch@chromium.org> Cr-Commit-Position: refs/heads/master@{#558173}
-
chaopeng authored
This issue is caused by: 1. Press on any mouse button will update the last_scrollbar_under_mouse_ in EventHandler. last_scrollbar_under_mouse_ will set to null and call Scrollbar::MouseExited() when mouse middle click out of scrollbar. 2. Release any mouse button will check last_scrollbar_under_mouse_ for cleanup the mouse press state on Scrollbar. Because mouse middle button press happens before any mouse button release, last_scrollbar_under_mouse_ is null then release mouse button will not clear the scrollbar press state. There is another related issue here. We can drag the scrollbar by pressing the middle button. The root cause of the bug is not checking for the left mouse button before updating last_scrollbar_under_mouse_ and calling Scrollbar::MouseDown. In this patch, we only handle mouse left button for Scrollbar. Bug: 721303 Change-Id: I714eca2bbdd9dd1628e596dc6b9119bb5de85cc3 Reviewed-on: https://chromium-review.googlesource.com/1048389 Commit-Queue: Jianpeng Chao <chaopeng@chromium.org> Reviewed-by:
David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#558172}
-
Wez authored
Allowances were added in thread checks, but these are no longer required since the fake for this class now grabs the calling-thread's TaskRunner. Bug: 838386 Change-Id: I27bc5bc192067ac5fc6c1636108dad30e92190f0 Reviewed-on: https://chromium-review.googlesource.com/1056252 Commit-Queue: Daniel Murphy <dmurph@chromium.org> Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Cr-Commit-Position: refs/heads/master@{#558171}
-
Owen Rodley authored
The include flow is: test_struct_sizes.c arch_dependent_sizes_(32|64).h test_struct_sizes.c again arch_dependent_sizes_(32|64).h again then we hit the include guard as we've included the header twice test_struct_sizes.c is the only file that includes either of these headers, so the #include of test_struct_sizes.c is redundant. Change-Id: I95a4efe45a46dfe26b9b0e60b15af702d5546717 Reviewed-on: https://chromium-review.googlesource.com/1055009Reviewed-by:
Raymes Khoury <raymes@chromium.org> Commit-Queue: Owen Rodley <orodley@chromium.org> Cr-Commit-Position: refs/heads/master@{#558170}
-
Sam McNally authored
The cros-disks equivalent for MountType (MountSourceType) has a third option (MOUNT_SOURCE_NETWORK_STORAGE) without a matching enumerator in MountType; this value is now used for generic fuse mounts. VolumeManager falls-through switches due to the unexpected value. Add MOUNT_TYPE_NETWORK_SOURCE on the chrome side to avoid this problem. Since this is currently a catch-all value for all generic fuse mount types, VolumeManager isn't capable of handling their mounts reasonably. Instead, ignore mount events with type MOUNT_TYPE_NETWORK_SOURCE in VolumeManager; the mounters will handle their mount events individually. Bug: 829274,832507 Change-Id: I18dc0b5b68120c94da2ebbe05ee863a6f471b81c Reviewed-on: https://chromium-review.googlesource.com/1053621Reviewed-by:
Joel Hockey <joelhockey@chromium.org> Commit-Queue: Sam McNally <sammc@chromium.org> Cr-Commit-Position: refs/heads/master@{#558169}
-
Noel Gordon authored
Enabled in RELEASE, now re-enable this test in DEBUG/MSAN/ASAN. Bug: 836254 Change-Id: Ie6ca28f923dcf70be407c8782985195874f47758 Reviewed-on: https://chromium-review.googlesource.com/1056748Reviewed-by:
-
Noel Gordon authored
Remove TODOs (found a better way to address this in future changes). Comment only change. No-Try: true Bug: 836254 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: Ibfb73d564964afbaca95ac4b1125a084a7939691 Reviewed-on: https://chromium-review.googlesource.com/1056767Reviewed-by:
-
- 13 May, 2018 20 commits
-
-
Noel Gordon authored
Remove unused #include. Also update to copyright notice per style. Bug: 836254 Change-Id: Icb7bcec55d20535cdd2f0f5eb49bd1c3e22ca2ca Reviewed-on: https://chromium-review.googlesource.com/1056747Reviewed-by:
-
Jinsuk Kim authored
https://crrev.com/c/517683 introduced a bug in accessibility mode when page scale factor is not 1. Before the patch, the hover event coordinate is converted to CSS (https://goo.gl/ER8wu5) but after the patch the unit was DIP by mistake. (https://goo.gl/ER8wu5). This CL fixes it by applying the page scale factor to set the unit right to CSS. Bug: 840609 Change-Id: Iaa17882e2ffb2d5637e59df1ebe7cf677f4a76a3 Reviewed-on: https://chromium-review.googlesource.com/1055067 Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#558165}
-
Bence Béky authored
This platform directory is meant to make sharing code easier. //net/spdy is not shared, no need to use platform there. This change is git cl formatted. Change-Id: Ic83a923a75815c01e0eb819eeb77c669c1a54d27 Reviewed-on: https://chromium-review.googlesource.com/1054524Reviewed-by:
-
fuchsia-sdk-chromium-autoroll authored
The AutoRoll server is located here: https://fuchsia-sdk-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=luci.chromium.try:fuchsia_arm64_cast_audio;luci.chromium.try:fuchsia_x64_cast_audio TBR=cr-fuchsia+bot@chromium.org Change-Id: Ie524ebb911d34d88897b64101c6670ef486c18d6 Reviewed-on: https://chromium-review.googlesource.com/1056261 Commit-Queue: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#558163}
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/ec48812c5a54..b06a1eb4e579 $ git log ec48812c5..b06a1eb4e --date=short --no-merges --format='%ad %ae %s' 2018-05-13 reed detect overflow for morphology Created with: roll-dep src/third_party/skia The AutoRoll server is located here: https://autoroll.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.blink:linux_trusty_blink_rel;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_optional_gpu_tests_rel TBR=herb@chromium.org Change-Id: I59a42f2941b8bf69196cc27d6ae9337e1b88a6ab Reviewed-on: https://chromium-review.googlesource.com/1056254Reviewed-by:
skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#558162}
-
Stefan Zager authored
BUG=841791 R=skobes@chromium.org Change-Id: I41ebc90803c4398aaaab3a8713e34fd3824595c5 Reviewed-on: https://chromium-review.googlesource.com/1055675Reviewed-by:
Stefan Zager <szager@chromium.org> Reviewed-by:
Steve Kobes <skobes@chromium.org> Commit-Queue: Stefan Zager <szager@chromium.org> Cr-Commit-Position: refs/heads/master@{#558161}
-
Wez authored
This reverts commit de03f4c9. Reason for revert: CL introduced a ReportingPermissionsChecker class which appears to be intended to safely "cancel" UI-thread work posted from the IO thread, when the class instance is destroyed. The class, however, is always destroyed on the IO thread, so this use of WeakPtrs does not have the intended effect. Original change's description: > Reporting: Use BACKGROUND_SYNC permission to control uploads > > We now use the BACKGROUND_SYNC permission to decide whether or not to > upload reports for a particular origin. Note that as currently written, > we don't use this permission to decide whether to *collect* the reports, > only whether to *send* them. Whether or not to collect is controlled > by the site's cookie settings. > > Bug: 704259 > Change-Id: I059019ab85106c26f4d156e9f5d61e2f8b8fa757 > Reviewed-on: https://chromium-review.googlesource.com/937572 > Reviewed-by: Ryan Hamilton <rch@chromium.org> > Commit-Queue: Douglas Creager <dcreager@google.com> > Cr-Commit-Position: refs/heads/master@{#540257} TBR=rch@chromium.org,juliatuttle@chromium.org,dcreager@google.com Bug: 704259 Change-Id: I9cb1990f4273f74e39de83b99a12e6bfc00e7348 Reviewed-on: https://chromium-review.googlesource.com/1056727 Commit-Queue: Wez <wez@chromium.org> Reviewed-by:
Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#558160}
-
David Reveman authored
SetCursor should determine if cursor hotspot changed by looking at the last set hotspot and not the last captured hotspot. Bug: 842507 Test: exo_unittests --gtest_filter=PointerTest.SetCursor Change-Id: I98de185a618adeb440165f372d8127bbc0c4a6f0 Reviewed-on: https://chromium-review.googlesource.com/1056667Reviewed-by:
Daniele Castagna <dcastagna@chromium.org> Commit-Queue: David Reveman <reveman@chromium.org> Cr-Commit-Position: refs/heads/master@{#558159}
-
Charlie Harrison authored
These methods aren't being used anymore. This CL also removes some tests which exercise these methods. This CL was split from https://chromium-review.googlesource.com/c/chromium/src/+/1055738 Bug: 842337 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo TBR=slan@chromium.org,jochen@chromium.org,sergeyu@chromium.org Change-Id: Ie695e2e1ab33cc13ebf8abc6e148251e0c4ec70c Reviewed-on: https://chromium-review.googlesource.com/1056108 Commit-Queue: Charlie Harrison <csharrison@chromium.org> Reviewed-by:
-
Han Leon authored
This CL propagates change of registration's `updateViaCache` to corresponding registration objects in the renderer process to set their ServiceWorkerRegistration#updateViaCache attribute. BUG=675540 Change-Id: I6bb80dacbdd6a276f7ba8eb95f9f1e5379fbf03b Reviewed-on: https://chromium-review.googlesource.com/1002732Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Reviewed-by:
-
chromeos-commit-bot@chromium.org authored
BUG=762641 TBR=xiyuan@chromium.org Change-Id: Ifef0be617da29fa1d39f06acbe6d578ac2c1a80f Reviewed-on: https://chromium-review.googlesource.com/1056121 Commit-Queue: ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> Reviewed-by:
ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#558156}
-
afdo-chromium-autoroll authored
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: I4b7f7269d63430aa4e51cfd68593715f962bc825 Reviewed-on: https://chromium-review.googlesource.com/1056628 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@{#558155}
-
https://pdfium.googlesource.com/pdfium.git/+log/82cb80962bc6..e20f0c4938f8 $ git log 82cb80962..e20f0c493 --date=short --no-merges --format='%ad %ae %s' 2018-05-13 hnakashima Add option to run safetynet_compare.py without a profiler. Created with: roll-dep src/third_party/pdfium The AutoRoll server is located here: https://pdfium-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=dsinclair@chromium.org Change-Id: Idf631118eb7adb6160058fd46ca01dd43598567d Reviewed-on: https://chromium-review.googlesource.com/1056608 Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#558154}
-
Abhishek Arya authored
TBR=mmoroz@chromium.org,liaoyuke@chromium.org Change-Id: I7c192d6ef87ff08291574ba3c42aeeb8640d9306 Reviewed-on: https://chromium-review.googlesource.com/1056627Reviewed-by:
Abhishek Arya <inferno@chromium.org> Commit-Queue: Abhishek Arya <inferno@chromium.org> Cr-Commit-Position: refs/heads/master@{#558153}
-
Alexey Baskakov authored
In low disk space scenarios, Cryptohome erases caches while target amount of free disk space is not reached. It starts from low priority categories. Cryptohome.DiskCleanupProgress histogram reports, which topmost priority was reached to fulfill a cleanup request. platform2 part: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/1049986 We need to land this before Friday to get it working in M68. Bug: 835114 Change-Id: Ia89335ac64d2e94ae7298b24a96de8547d8e392e Reviewed-on: https://chromium-review.googlesource.com/1051209 Commit-Queue: Alexey Baskakov <loyso@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Cr-Commit-Position: refs/heads/master@{#558152}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=mmoss@chromium.org Change-Id: I73e84b64b6842ff34c0f13530c9a21d7988ed8fe Reviewed-on: https://chromium-review.googlesource.com/1056021Reviewed-by:
-
Dominic Farolino authored
Initial infrastructure changes to support Priority Hints. This includes adding a FetchImportanceMode enum to fetch_api_request.mojom, some supporting getters/setters to FetchParameters as well as ResourceRequest, and priority-modifying logic to ResourceFetcher. R=kinuko@chromium.org, yhirano@chromium.org, yoav@yoav.ws Bug: 821464 Change-Id: I5ab7f70f44e80d01b7d47ad4c00ae3f4817815ee Reviewed-on: https://chromium-review.googlesource.com/1053221 Commit-Queue: Dominic Farolino <domfarolino@gmail.com> Reviewed-by:
Yoav Weiss <yoav@yoav.ws> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#558150}
-
Jinsuk Kim authored
ByteArrayGenerator, CipherFactory are used by Chrome only, and don't have to be in content layer. This CL moves it to chrome directory, and deletes the corresponding DEPS exception rules. Bug: 617324 Change-Id: Iee5d8effe2148ef3e50375e8848048a58a0cc046 Reviewed-on: https://chromium-review.googlesource.com/1049769 Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Reviewed-by:
Chris Palmer <palmer@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Reviewed-by:
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/96b0b46f2334..ec48812c5a54 $ git log 96b0b46f2..ec48812c5 --date=short --no-merges --format='%ad %ae %s' 2018-05-12 angle-skia-autoroll Roll third_party/externals/angle2/ 18e323ab2..66aafcb46 (1 commit) Created with: roll-dep src/third_party/skia The AutoRoll server is located here: https://autoroll.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.blink:linux_trusty_blink_rel;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_optional_gpu_tests_rel TBR=egdaniel@chromium.org Change-Id: Icc36391577d1663b3802986e38d96850f9a14e87 Reviewed-on: https://chromium-review.googlesource.com/1056063 Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
-
Dmitry Gozman authored
This is a reland of 500de904 Original change's description: > Merge WebClipboardImpl and Pasteboard into Clipboard > > Bug: 775830 > Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 > Change-Id: I3da04418bac37e0e03b63df4a8d2407296948e77 > Reviewed-on: https://chromium-review.googlesource.com/1045492 > Commit-Queue: Dmitry Gozman <dgozman@chromium.org> > Reviewed-by: Kentaro Hara <haraken@chromium.org> > Reviewed-by: Daniel Cheng <dcheng@chromium.org> > Cr-Commit-Position: refs/heads/master@{#557739} Bug: 775830 Change-Id: I921c9c3becf2acf3b169049656e898be6e4b8e1e Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Reviewed-on: https://chromium-review.googlesource.com/1056427 Commit-Queue: Dmitry Gozman <dgozman@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#558147}
-
- 12 May, 2018 1 commit
-
-
Max Moroz authored
The test has been removed in https://chromium-review.googlesource.com/c/chromium/src/+/1053765 Bug: 789981 TBR=inferno@chromium.org,liaoyuke@chromium.org Change-Id: Ic27246e0e839557f5dab5a7238c166b16ab1dba2 Reviewed-on: https://chromium-review.googlesource.com/1056065 Commit-Queue: Max Moroz <mmoroz@chromium.org> Reviewed-by:
Max Moroz <mmoroz@chromium.org> Cr-Commit-Position: refs/heads/master@{#558146}
-
