- 03 Jan, 2019 17 commits
-
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/bbd8fc1f9fa4..a70cce175222 Created with: gclient setdep -r src-internal@a70cce175222 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll 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=mmoss@chromium.org Change-Id: Id71543b5f469a205da6aca3dca7010188fc08c60 Reviewed-on: https://chromium-review.googlesource.com/c/1393357Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#619555}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Headers.git/+log/4618b86e9e4b..392ae31831b7 git log 4618b86e9e4b..392ae31831b7 --date=short --no-merges --format='%ad %ae %s' 2019-01-03 johnkslang@users.noreply.github.com Merge pull request #87 from rtbo/dlang Created with: gclient setdep -r src/third_party/spirv-headers/src@392ae31831b7 The AutoRoll server is located here: https://autoroll.skia.org/r/spirv-headers-chromium-autoroll 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: Ia712ff4d3bccbe1bfec57a7c68dce03e7b7ced7e Reviewed-on: https://chromium-review.googlesource.com/c/1393926Reviewed-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@{#619554}
-
Dan Beam authored
This CL was generated with: $ eslint --fix ui/webui $ git cl format --js Note: there are some annoying edge cases that mess up formatting. Specifically: if (blah) // trailing comment <do something> is transformed by eslint --fix into: if (blah) // trailing comment { <do something> } and all other types of things start to get funky. R=aee@chromium.org BUG=916782 NOPRESUBMIT=true # for __lookupGetter__ in cr.js Change-Id: I2698d8c17ee06dac0688aa55d783f7978f587663 Reviewed-on: https://chromium-review.googlesource.com/c/1393626 Commit-Queue: Dan Beam <dbeam@chromium.org> Reviewed-by:Esmael El-Moslimany <aee@chromium.org> Cr-Commit-Position: refs/heads/master@{#619553}
-
khmel@chromium.org authored
We are 2+ years using shelf pins supported by sync. Now we can drop import from prefs code. As a side effect this fixes several DCHECKs. This also makes pin positions for default apps and apps, pinned by policy deterministic and not-dependent from installation order. TEST=Locally + unit_tests. Logic of unit tests is not changed. BUG=918203 BUG=907221 Change-Id: I11d1cd7f1f0192719b48adfd3fa9e56c9dc1429b Reviewed-on: https://chromium-review.googlesource.com/c/1392280 Commit-Queue: Yury Khmel <khmel@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/heads/master@{#619552}
-
Peter Kotwicz authored
This CL changes the names of methods which search for a WebAPK which matches a given URL to make it clearer what the return value is if there are several matching WebAPKs. Changed method names in WebApkValidator: queryWebApkPackage() -> queryFirstWebApkPackage() queryWebApkResolveInfo() -> queryFirstWebApkResolveInfo() findWebApkPackage() -> findFirstWebApkPackage() findWebApkResolveInfo() -> findFirstWebApkResolveInfo() BUG=None Change-Id: I2a1bb3042f93fb6f465cd069f672bfca57acb7f9 Reviewed-on: https://chromium-review.googlesource.com/c/1390320 Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Cr-Commit-Position: refs/heads/master@{#619551}
-
Daniel Rubery authored
The crash in http://crbug/915037 appears to have been fixed, so this CHECK is ready to be removed. Bug: 915037 Change-Id: I1b09c308287e3ef6d411b60378f08f334c8396e3 Reviewed-on: https://chromium-review.googlesource.com/c/1393884 Commit-Queue: Varun Khaneja <vakh@chromium.org> Reviewed-by:
Varun Khaneja <vakh@chromium.org> Cr-Commit-Position: refs/heads/master@{#619550}
-
Aidan Wolter authored
Bug: None Test: None Change-Id: Ib9daa3f4e144c3c7b62d7d472cb631f2e6db41a5 Reviewed-on: https://chromium-review.googlesource.com/c/1393892Reviewed-by:
Wez <wez@chromium.org> Commit-Queue: Aidan Wolter <awolter@chromium.org> Cr-Commit-Position: refs/heads/master@{#619549}
-
Xiaocheng Hu authored
When NextLinePosition() reaches block boundaries, it uses NextLeafWithSameEditability() to search forward in DOM tree to look for an appropriate starting node in the next block. The function performs editability adjustment by itself that, and uses the editability of the starting node, which is the last node in the last block, which is incorrect as shown in the new test case. This patch fixes the problem by specifying the correct editability. Bug: 906148 Change-Id: I0d62212209a900ec26ba5b3bfbc6d1873dba02d7 Reviewed-on: https://chromium-review.googlesource.com/c/1392257 Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> Reviewed-by:
Shimi Zhang <ctzsm@chromium.org> Cr-Commit-Position: refs/heads/master@{#619548}
-
Wez authored
User input is now received via the Scenic session, so remove the legacy InputConnection path for those events. Bug: 900428 Change-Id: Ifcbb04c52cf517fe8f472854d5736625ff1a87d5 Reviewed-on: https://chromium-review.googlesource.com/c/1393705Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Commit-Queue: Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#619547}
-
chuanl authored
This is guarded by the CCTModuleCustomHeader Finch feature. Bug: 882404 Change-Id: I2a7675b95d2135b602f89b26a5d9220677d9079a Reviewed-on: https://chromium-review.googlesource.com/c/1386428Reviewed-by:
Michael van Ouwerkerk <mvanouwerkerk@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Reviewed-by:
Matthew Jones <mdjones@chromium.org> Commit-Queue: John Lin <chuanl@google.com> Cr-Commit-Position: refs/heads/master@{#619546}
-
Toni Barzic authored
SigninExtensionsDeviceCloudPolicyBrowserTests were opening a browser window in Sign-in profile and running the test code in that context. In general, browser windows should not be used in sign-in profile, so we should not rely on this behavior in tests. The test code is moved to the test extensions background page, and run on runtime.onInstalled event (which should be dispatched on each extension install event - note that running the tests in event listener is not strictly necessary, but it gives better indication of the reason the background page is loaded). Given that in sign-in profile, background hosts are not allowed for non-policy installed extensions, the test is updated to set up policy to force install the test extension (which is packed into a CRX, which is added to test data dir). Furthermore, the test extension is transformed to an app, and whitelisted using whitelisted-extension-id switch. This makes ScopedSigninScreenPolicyProviderDisabler unnecessary. PreinstalledSigninExtensionsDeviceCloudPolicyBrowserTest is dropped, and the component policy caching is tested by running sign-in extension device policy tests in two parts: * first, PRE_ManagedStorage test downloads the component policy from the tests server and runs the test extension (matches the logic in replaced InstallAndRunInWindow test) * the second, ManagedStorage test verifies that the downloaded policy is cached and usable after restart by throttling the component policy download request. BUG=916859 Change-Id: Ia0748c2914649ea439664d748aca0bd5461a397f Reviewed-on: https://chromium-review.googlesource.com/c/1379702Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Commit-Queue: Toni Baržić <tbarzic@chromium.org> Cr-Commit-Position: refs/heads/master@{#619545}
-
Chris Harrelson authored
This is because change of stacking may result in a change of the size or position of a composited layer. Bug: 916896 Change-Id: I44d42efc84df892c9e6cbf04f9dcb9ee34a803d9 Reviewed-on: https://chromium-review.googlesource.com/c/1392363Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#619544}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/bba675db3eb4..c63ddb2a3f9a git log bba675db3eb4..c63ddb2a3f9a --date=short --no-merges --format='%ad %ae %s' 2019-01-02 amithi@webrtc.org Negotiating Simulcast in the initial offer/answer - Part1. Created with: gclient setdep -r src/third_party/webrtc@c63ddb2a3f9a The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-chromium-autoroll 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:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I78fd30bb16b9eefb7d01b08f6fea768211d8459a Reviewed-on: https://chromium-review.googlesource.com/c/1393415Reviewed-by:
-
Danan S authored
This reverts commit e775e110. Reason for revert: This is inconsistently crashing demo mode when Android apps are launched on certain devices. Original change's description: > Added UMA metric to count unique apps launched during Demo Mode. > > Bug: 904564 > Change-Id: I653438bf5244bc98bcb742d9d986b4ea2bd4b40a > Reviewed-on: https://chromium-review.googlesource.com/c/1334563 > Commit-Queue: Michael Giuffrida <michaelpg@chromium.org> > Reviewed-by: Michael Giuffrida <michaelpg@chromium.org> > Reviewed-by: Brian White <bcwhite@chromium.org> > Reviewed-by: Mitsuru Oshima <oshima@chromium.org> > Cr-Commit-Position: refs/heads/master@{#609961} TBR=oshima@chromium.org,michaelpg@chromium.org,bcwhite@chromium.org,danan@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 917156 Change-Id: I7e8d88541ad5f74fda720425c05816f48e4ba4a8 Reviewed-on: https://chromium-review.googlesource.com/c/1387953Reviewed-by:
Michael Giuffrida <michaelpg@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Commit-Queue: Danan S <danan@chromium.org> Cr-Commit-Position: refs/heads/master@{#619542}
-
James Hollyer authored
This change adds a list of notifications that are currently displayed and checks that list for duplicates before displaying a new notification. Bug: 789362 Change-Id: I1f8025dbb237da35b088de5bd6f21e80a1bbec52 Reviewed-on: https://chromium-review.googlesource.com/c/1373436 Commit-Queue: James Hollyer <jameshollyer@chromium.org> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#619541}
-
liberato@chromium.org authored
Since it turns out to be much easier to record results for a regressor than a classifier, add support for it to ExtraTrees. Change-Id: I0734c81bafd87e06c23df8f74b7a0c4c80d616e6 Reviewed-on: https://chromium-review.googlesource.com/c/1391327 Commit-Queue: Frank Liberato <liberato@chromium.org> Reviewed-by:
Dan Sanders <sandersd@chromium.org> Cr-Commit-Position: refs/heads/master@{#619540}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/bdda5e4967f2..534e18423b9c git log bdda5e4967f2..534e18423b9c --date=short --no-merges --format='%ad %ae %s' 2019-01-02 dburger@chromium.org Removal of out of date active_waterfall comments in chromeos_config.py Created with: gclient setdep -r src/third_party/chromite@534e18423b9c The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-chromium-autoroll 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=chrome-os-gardeners@chromium.org Change-Id: Ib70c0bba183eb56232f4e9d4cf66af5185280593 Reviewed-on: https://chromium-review.googlesource.com/c/1393355Reviewed-by:
-
- 02 Jan, 2019 23 commits
-
-
John Lee authored
Change-Id: I6ceea7e847bd9b141426e7f491f447e739c64437 Reviewed-on: https://chromium-review.googlesource.com/c/1389395 Commit-Queue: John Lee <johntlee@chromium.org> Reviewed-by:
Hector Carmona <hcarmona@chromium.org> Cr-Commit-Position: refs/heads/master@{#619538}
-
Jinsuk Kim authored
This CL partially reverts the change made in https://crrev.com/c/1381352 which was a mistake. The main menu should appear if ephemeral tab is in peeked mode, while should be disabled in the other available mode(maxmized). This CL fixes it. Bug: 916931 Change-Id: Ie80bdd606be065685689e7f45ae0792b6253cdb7 Reviewed-on: https://chromium-review.googlesource.com/c/1392688Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Cr-Commit-Position: refs/heads/master@{#619537}
-
Ted Choc authored
Update the suggestion visibility call to handle multiple focus/lost focus cycles by always calling the finish animations method after any url focus event. BUG=902243 Change-Id: I413b772436faaa30c19106799ba27c638b6986e9 Reviewed-on: https://chromium-review.googlesource.com/c/1393375Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/bbdeee914aeb..48bbc53ea4d0 git log bbdeee914aeb..48bbc53ea4d0 --date=short --no-merges --format='%ad %ae %s' 2019-01-02 bryan.bernhart@intel.com ES31: Fix for reading back initialized SSBO buffers in D3D11 2019-01-02 syoussefi@chromium.org Suppress flaky Linux/Intel/OpenGL test. Created with: gclient setdep -r src/third_party/angle@48bbc53ea4d0 The AutoRoll server is located here: https://autoroll.skia.org/r/angle-chromium-autoroll 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: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=ynovikov@chromium.org Change-Id: Ib4f6846d4ee3b65da1681f8d06641b1eb756533f Reviewed-on: https://chromium-review.googlesource.com/c/1393356Reviewed-by:
-
Aidan Wolter authored
Bug: None Test: ./tools/fuchsia/local-sdk.py <fuchsia> x64 Change-Id: I9b73e6cf179b739345ea0d48c5e597de44eef8f1 Reviewed-on: https://chromium-review.googlesource.com/c/1393743Reviewed-by:
Fabrice de Gans-Riberi <fdegans@chromium.org> Reviewed-by:
-
Peter Boström authored
This change makes flood fill the default ink-drop style. Square InkDrops are currently bugs in the browser that are kind-of hidden by InkDrop masks. It makes use of the same path that FocusRing uses for masks to make sure that the InkDrop and FocusRing are in sync by default. These mismatch bugs keep popping up, especially on Mac, as testers verify new parts of the UI. Follow-up changes will be to reduce the number of classes that override CreateInkDrop methods and make sure that they explicitly request a SquareInkDrop when they want it. Bug: chromium:888204, chromium:907833, chromium:915284 Change-Id: I681b93d6f5bdfe7f78421ebc8f2fbd522fb6eee4 Reviewed-on: https://chromium-review.googlesource.com/c/1367186 Commit-Queue: Peter Boström <pbos@chromium.org> Reviewed-by:
Michael Wasserman <msw@chromium.org> Reviewed-by:
Mohsen Izadi <mohsen@chromium.org> Cr-Commit-Position: refs/heads/master@{#619533}
-
Dan Beam authored
Previously, there were things like: --some-color: #010203; --some-color-opacity-X: rgba(1, 2, 3, X); Which is a bit inflexible and leads to a bit of redundancy. Instead, let's use this syntax, which allows minting an arbitrary number of colors with var() + rgba() syntax: --some-color-rgb: 1, 2, 3; --some-color: rgb(var(--some-color)); /* later ... */ color: rgba(var(--some-color-rgb), X /* any opacity */); Bug: 883049 Change-Id: If730a1123294e43f2ea04b433c6c5a46933cc08e Reviewed-on: https://chromium-review.googlesource.com/c/1393442Reviewed-by:
-
Adrienne Walker authored
This reverts this patch: https://chromium-review.googlesource.com/1229693 UMA data has been gathered and this isn't something we want to track over time, so just remove all of this code. Bug: 590373 Change-Id: I67947714a6099dc33230ad28e7a3b61374e5adb6 Reviewed-on: https://chromium-review.googlesource.com/c/1357640Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Commit-Queue: enne <enne@chromium.org> Cr-Commit-Position: refs/heads/master@{#619531}
-
Evan Stade authored
TBR=jamescook@chromium.org Bug: 831826 Change-Id: Ic089f47b5069c54f79d9daaa66d1c6d6bde25657 Reviewed-on: https://chromium-review.googlesource.com/c/1393555Reviewed-by:
Evan Stade <estade@chromium.org> Commit-Queue: Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#619530}
-
Lukasz Anforowicz authored
This CL adds a feature that, when enabled, will stop giving content scripts a URLLoaderFactory with |is_corb_enabled| set to false (unless a given extension is on an allowlist). To minimize churn and risk, the feature is disabled by default for now. Tests added in the CL ensure proper behavior when: 1. The feature is disabled (the default, content scripts are able to make cross-origin requests) 2. The feature is enabled and the test extension is allowlisted (same behavior expectations as above) 3. The feature is enabled and the test extension is *not* allowlisted (new, desirable behavior: CORB enforcement for cross-origin requests) The allowlist is computed as a sum of 1) Extensions.CrossOriginFetchFromContentScript2 Rappor data (see kHardcodedPartOfCorbAllowlist introduced by the CL in //extensions/browser/url_loader_factory_manager.cc) 2) An optional field trial param (see kBypassCorbAllowlistParamName). Bug: 846346 Change-Id: I1ab69261cb092b709042a9a963781acc95e8cde6 Reviewed-on: https://chromium-review.googlesource.com/c/1354260Reviewed-by:
Charlie Reis <creis@chromium.org> Reviewed-by:
danakj <danakj@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Cr-Commit-Position: refs/heads/master@{#619529}
-
Wez authored
This test was disabled on Windows in https://chromium-review.googlesource.com/c/1293670 because of failures on the Windows Debug bots. The failure cannot be reproduced locally, and we don't have links to logs from the failed runs, so re-enabling the test to allow us to repro and diagnose the issue. Bug: 897735, 802393 Change-Id: I9086366e7b1f9240674f3b5678810d221b5d01ff Reviewed-on: https://chromium-review.googlesource.com/c/1393545Reviewed-by:
Albert J. Wong <ajwong@chromium.org> Reviewed-by:
-
Robert Ma authored
to unblock the importer. Each test has their corresponding bug filed manually. TBR=hbos Bug: 832501, 918663, 918664 Change-Id: I69e94ed84c412ebf744a9a6074d9f158bcf7f4ae Reviewed-on: https://chromium-review.googlesource.com/c/1393557Reviewed-by:
Robert Ma <robertma@chromium.org> Commit-Queue: Robert Ma <robertma@chromium.org> Cr-Commit-Position: refs/heads/master@{#619527}
-
rbpotter authored
testIronIcons assumes that iron-icons are set using the |icon| property, so it checks that any iron-icon without |icon| set has zero width and height. However, iron-icons can also be set using the |src| property, which causes the iron-icon to have nonzero size with an undefined |icon| property. Return early in this case instead of failing. Bug: None Change-Id: Ie522ca001241bb5b56a3c6775cdc90251acb9409 Reviewed-on: https://chromium-review.googlesource.com/c/1393458Reviewed-by:
Dan Beam <dbeam@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#619526}
-
Albert J. Wong authored
With Network Service many of these are deprecated. Since they were quasi-incorrectly using child_id, routing_id as a proxy for "tab" deleting them now makes the code cleaner. Bug: 472869, 392171, 304341 Change-Id: Iacd99a39c496f3d56d4dd6bda70813c4bf9e7c24 Reviewed-on: https://chromium-review.googlesource.com/c/1387947 Commit-Queue: Albert J. Wong <ajwong@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Cr-Commit-Position: refs/heads/master@{#619525}
-
Peter K. Lee authored
They are failing across all bots. Bug: 918711 Change-Id: Ib1f293a2181b0a6fe0371f5383138198a9490aef Reviewed-on: https://chromium-review.googlesource.com/c/1393706Reviewed-by:
Eugene But <eugenebut@chromium.org> Commit-Queue: Peter Lee <pkl@chromium.org> Cr-Commit-Position: refs/heads/master@{#619524}
-
chrome://settings/contentJohn Lee authored
Change-Id: I2c38ed6ebbf7cb7cedd6b4228c8753c75eed730d Reviewed-on: https://chromium-review.googlesource.com/c/1391775 Commit-Queue: John Lee <johntlee@chromium.org> Reviewed-by:
-
Evan Stade authored
Broaden the filters to disable all tab dragging tests, since a lot (all?) are flakily failing on mash_fyi_interactive_ui_tests TBR=mukai@chromium.org Bug: 890071 Change-Id: Ifd4415d4326c49f374e0f023875a003365905cbe Reviewed-on: https://chromium-review.googlesource.com/c/1393534Reviewed-by:
-
Vikas Soni authored
Remove NOTREACHED() from the internal format calculations for GLImageAHardwareBuffer. All the default buffer format should use GL_RGBA as internal format. Bug: 918661 Change-Id: Id15561161def1891674f8eb62bc8e189665991c5 Reviewed-on: https://chromium-review.googlesource.com/c/1393544Reviewed-by:
Antoine Labour <piman@chromium.org> Commit-Queue: vikas soni <vikassoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#619521}
-
Leonard Grey authored
Made in service of dark mode, but also setting one for light mode after consulting with UX. Bug: 918194 Change-Id: Ie4a5c76cd8ba833d5e518a65fea1ff21d0f8b28d Reviewed-on: https://chromium-review.googlesource.com/c/1393022Reviewed-by:
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/b87374f9130f..191e64b6c6c2 git log b87374f9130f..191e64b6c6c2 --date=short --no-merges --format='%ad %ae %s' 2019-01-02 reed@google.com pass a font to GlyphRunBuilder 2019-01-02 kjlubick@google.com [canvaskit] Move to using SkFont instead of SkPaint.measure* 2019-01-02 benjaminwagner@google.com [infra] Uninstall ASAN when cleaning up Android device. 2019-01-02 egdaniel@google.com Add initial support for creating a vulkan secondary command buffer drawing context. 2019-01-02 reed@google.com Revert "undefine SK_SUPPORT_LEGACY_PAINT_TEXTMEASURE" 2019-01-02 brianosman@google.com Remove special case for DCI P3 when making ICC profiles 2019-01-02 ianloic@google.com Update SkFontMgr_fuchsia.cpp for new FIDL API 2019-01-02 herb@google.com Return SkGlyphCache and GrTextStrike together. 2019-01-02 fmalita@chromium.org [skottie] Initial 3D layer transform support Created with: gclient setdep -r src/third_party/skia@191e64b6c6c2 The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll 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: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 TBR=bungeman@chromium.org Change-Id: Icac1bcfd5a51c1805220f37b09a0471235fb7d17 Reviewed-on: https://chromium-review.googlesource.com/c/1393354Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/7a3b1ce7ab6d..bbd8fc1f9fa4 Created with: gclient setdep -r src-internal@bbd8fc1f9fa4 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll 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=mmoss@chromium.org Change-Id: I1ae7da720290d16f081ea108c25ec6ea619190c5 Reviewed-on: https://chromium-review.googlesource.com/c/1393414Reviewed-by:
-
Michael Ludwig authored
Bug: 915735 Change-Id: Ie574420c2c6bda5da5cc3ba531e2ca3cdcae6b56 Reviewed-on: https://chromium-review.googlesource.com/c/1391305 Commit-Queue: Michael Ludwig <michaelludwig@google.com> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#619517}
-
Leonard Grey authored
Bug: 918194 Change-Id: I4ffe380241ebaf46adac236535e8138729bfd227 Reviewed-on: https://chromium-review.googlesource.com/c/1393523Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Leonard Grey <lgrey@chromium.org> Cr-Commit-Position: refs/heads/master@{#619516}
-
