- 05 Mar, 2019 40 commits
-
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Headers.git/+log/d3752ea20886..dc3db3a5ae5e git log d3752ea20886..dc3db3a5ae5e --date=short --no-merges --format='%ad %ae %s' 2019-03-05 cepheus@frii.com Fix #96: Don't include a comment after #endif for the C header. Created with: gclient setdep -r src/third_party/spirv-headers/src@dc3db3a5ae5e 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: Ia59182204c21c30306a7208e991f8327835092b1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1502412Reviewed-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@{#637611}
-
Dan Beam authored
Screenshots: https://imgur.com/a/CoU73B4 R=hcarmona@chromium.org BUG=926658 Change-Id: If741189597175b1068d7fcd4a8521b997a40a862 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1501792 Commit-Queue: Dan Beam <dbeam@chromium.org> Auto-Submit: Dan Beam <dbeam@chromium.org> Reviewed-by:
Hector Carmona <hcarmona@chromium.org> Cr-Commit-Position: refs/heads/master@{#637610}
-
Kunihiko Sakamoto authored
Setting a mock ContentBrowserClient via SetBrowserClientForTesting doesn't work on Android KitKat. (crbug.com/864403) After this patch, VariantMatch and VariantMismatch test cases will be skipped in Android version < 5. Bug: 937930,864403 Change-Id: Ia246305fbaa906c9a3f44d45b85e6b6e69b35d1f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1501954Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Tsuyoshi Horo <horo@chromium.org> Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#637609}
-
Maggie Cai authored
Currently on permission changes, the all sites list will be re-populated. This is a issue when we reset the permission for an etld+1. Because this resets every single permission settings for all the origins under the etld+1, which triggers 16*n (n=number of origins) on permission changes, therefore makes the all sites list repopulate that many time. This affect the performance, also make the list jump back to the top and lost the last selected entry. This CL removes the event listener for permission change in all sites page. In the future, we should implement the similar banner with reload when permission changes from other places (not all sites page) occurs. BUG=835712 Change-Id: I54596b1ba7d9901bdcd3ddd2192c1a0973aa5acf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1496118Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Commit-Queue: Maggie Cai <mxcai@chromium.org> Cr-Commit-Position: refs/heads/master@{#637608}
-
Darren Shen authored
TBR=dstockwell@chromium.org Bug: 938192 Change-Id: If1b92cbb423874c9638e7676d1e8fafa0f2ca2f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1502492 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by:
Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#637607}
-
Eliot Courtney authored
Bug: b/127224879 Test: drag-move an Android PIP window - no crash upon finishing drag. Change-Id: I3d455f3545ea1a7bfba4c9ec6f6b51d3b218078d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1498744 Commit-Queue: Eliot Courtney <edcourtney@chromium.org> Reviewed-by:
Yuichiro Hanada <yhanada@chromium.org> Cr-Commit-Position: refs/heads/master@{#637606}
-
Samuel Huang authored
Thin-LTO builds produce many (~3000 for Chrome) .L.ref.tmp symbols. SuperSize could not find |object_path| for them because: * The linker .map file points to thinlto-cache filenames (|thin_obj|). * ".L.ref.tmp" has high population, so name matching done in later nm step won't help. This CL associates .L.ref.tmp symbols with other symbols that share the same |thin_obj|, and attempts to deduce |object_path| if there is no ambiguity. Details: * In linker_map_parser.py, extract |address| -> |thin_obj|, and return the map. * In demangle.py, pass the map until after nm gets called to assign |object_paths| to regular symbols. * Add DeduceObjectPathsFromThinMap() that takes |address| -> |thin_obj| map, computes |thin_obj| -> |object_paths|, and assigns |object_path| to .L.ref.tmp symbols if no ambiguity arise, i.e., when |thin_obj| is associated with a unique |object_path|. For Chrome, this change causes about 30% of .L.ref.tmp symbols to gain |object_path|. Bug: 923936 Change-Id: I1864e764924d8e45ca5cb44d0ed7d0f73bec13ad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1500781 Commit-Queue: Samuel Huang <huangs@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#637605}
-
Maksim Sisov authored
GetWindowBoundsInScreen adds display origin to bounds in pixels, which is incorrect, because they contain a location in screen, and adding additional offset results in wrong positions for menus (when the browser is located on a secondary display). Bug: 927280 Change-Id: Ib16f46b095751cb3f29bfa6579d44eabdf104647 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1497052Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Maksim Sisov <msisov@igalia.com> Cr-Commit-Position: refs/heads/master@{#637604}
-
Matt Falkenhagen authored
Follow-up of r637231 which removed the test parameters that were based on kServiceWorkerServicification. Bug: 926114 Change-Id: I4c1bd72a451dd882f8553254ff4f42a27edf920b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1498808Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Commit-Queue: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#637603}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/6dacdbca1d6e..edefc3380260 Created with: gclient setdep -r src-internal@edefc3380260 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=yigu@chromium.org,peria@chromium.org,dgrogan@chromium.org,treib@chromium.org Change-Id: Ibd833194f6ffdcc64c3d8e2a05373d60193d2da6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1502372Reviewed-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@{#637602}
-
Karandeep Bhatia authored
Remove custom handling code for the embedded test server in ExtensionsAPITest. Instead use net::test_server::RegisterDefaultHandlers. Also modify a couple of tests to make them pass. BUG=None Change-Id: I500f7abcf79d4a89f6abe6588bacd3894c077f21 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1497428 Commit-Queue: Istiaque Ahmed <lazyboy@chromium.org> Auto-Submit: Karan Bhatia <karandeepb@chromium.org> Reviewed-by:
Istiaque Ahmed <lazyboy@chromium.org> Cr-Commit-Position: refs/heads/master@{#637601}
-
Takashi Toyoshima authored
PermissionsUpdater::SetDefaultPolicyHostRestrictions needs to update cors access lists as well as other permission updating methods do. This patch extends NetworkPermissionsUpdateHelper to support the default policy host restrictions case in addition to permissions update. This makes following tests pass with OOR-CORS. - BackgroundXhrWebstoreTest.PolicyContentScriptXHR - BackgroundXhrWebstoreTest.PolicyUpdateXHR - BackgroundXhrWebstoreTest.PolicyUpdateIndividualXHR - BackgroundXhrWebstoreTest.PolicyUpdateDefaultXHR Bug: 907428 Change-Id: I0ae7777bd87baa1c98dfbefba44b9911eb9c08f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1478661Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> Cr-Commit-Position: refs/heads/master@{#637600}
-
François Beaufort authored
This CL record buttons pressed and tap gestures for all controls in the Picture-in-Picture window. Bug: 932410 Change-Id: Ie751322f7e4fe3026a47e95c1a839cb90e2ae85b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1475433Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Commit-Queue: François Beaufort 🦔 <beaufort.francois@gmail.com> Cr-Commit-Position: refs/heads/master@{#637599}
-
Giovanni Ortuño Urquidi authored
AppRegistrar should be used by clients to query information about apps. For example, if an app is installed. AppRegistrar has two implementations BookmarkAppRegistrar and WebAppRegistrar. BookmarkAppRegistrar is built on top of extensions. PendingBookmarkApp uses BookmarkAppRegistrar to avoid querying the ExtensionRegistry and ExtensionPrefs directly. Bug: 916381 Change-Id: I0706bef37f2ecbf4b86d63eafe8de1dd168f440a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1498736 Commit-Queue: Giovanni Ortuño Urquidi <ortuno@chromium.org> Reviewed-by:
Alexey Baskakov <loyso@chromium.org> Cr-Commit-Position: refs/heads/master@{#637598}
-
Dan Beam authored
R=dpapad@chromium.org BUG=930042 Change-Id: Ic20ceb781e363b033a56fbd541dabecd52f2158f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1497541Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Auto-Submit: Dan Beam <dbeam@chromium.org> Cr-Commit-Position: refs/heads/master@{#637597}
-
Dan Beam authored
Screenshot: https://imgur.com/a/inurhXK R=dpapad@chromium.org BUG=926658 Change-Id: I26bca3932d0e92dad7d6c3cbfab35fe543e022f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1501992 Commit-Queue: Dan Beam <dbeam@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Auto-Submit: Dan Beam <dbeam@chromium.org> Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#637596}
-
Lei Zhang authored
As is, by the time PrintViewManager::PrintPreviewDone() gets called to unblock a Print Preview initiator, FocusController already tried to give the initiator focus and failed, because the initiator was in a blocked state. Add PrintViewManager::PrintPreviewAlmostDone() and call it right before the Print Preview dialog closes. This is necessary to get the timing right so the underlying Print Preview initiator can be unblocked before the FocusController tries to give it back focus. BUG=936542 TEST=Manual, see bug. Change-Id: Ifa7fcb451b94a6da82c554b685bca350be032120 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1497860 Commit-Queue: Lei Zhang <thestig@chromium.org> Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#637595}
-
Darren Shen authored
There was a flaky failure in compiling components/subresource_filter/content/browser/subresource_filter_client.h See: https://ci.chromium.org/p/chromium/builders/ci/win32-rel/12234 Error message was that it couldn't find: components/subresource_filter/core/mojom/subresource_filter.mojom.h Speculatively fixing this issue by adding the mojom file to DEPS. TBR=sky@chromium.org Change-Id: I72668d5e8d12af8d6cb32fae4b8258c4b1b62bd2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1502332Reviewed-by:
Darren Shen <shend@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#637594}
-
Kyle Milka authored
If a customize background dialog is opened and the space key is pressed the main page shouldn't scroll. If the mouse is used to scroll the page the dialog should stay centered while the page scrolls in the background (this is consistent with the custom links dialogs). Screencast: http://go/scrcast/NTY3MzY0NjkyODQyOTA1Nnw1MzY0N2JhNS1hZA Bug: 908381, 899730 Change-Id: I71e99f6d4481c9e61d3f98d0ff23f4d059a21464 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1501934Reviewed-by:
Kristi Park <kristipark@chromium.org> Commit-Queue: Kyle Milka <kmilka@chromium.org> Cr-Commit-Position: refs/heads/master@{#637593}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/232c456db8e9..d69cdaba1445 git log 232c456db8e9..d69cdaba1445 --date=short --no-merges --format='%ad %ae %s' 2019-03-05 loganchien@google.com Add -Wno-implicit-fallthrough Created with: gclient setdep -r src/third_party/swiftshader@d69cdaba1445 The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-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 BUG=chromium:b/115344057 TBR=swiftshader-team+autoroll@chromium.org Change-Id: I1c5fdee380ff778b376bb09d4ba8e052b0ff00e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1502095Reviewed-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@{#637592}
-
Shao-Chuan Lee authored
In case of a crash, metrics from previous session is not available when generating initial stability logs, which is probably why aggregated crash counts on UMA don't have ARC state associated. This patch introduces StabilityMetricsManager, which persists stability metrics into local state and record value from local state to UMA when needed. Bug: 929583 Change-Id: I747493f2462454baa7fc187421932ea71d52c9a1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1469810 Commit-Queue: Shao-Chuan Lee <shaochuan@chromium.org> Reviewed-by:
Hidehiko Abe <hidehiko@chromium.org> Reviewed-by:
Yury Khmel <khmel@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#637591}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/5610d5a7e96a..6dacdbca1d6e Created with: gclient setdep -r src-internal@6dacdbca1d6e 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=yigu@chromium.org,peria@chromium.org,dgrogan@chromium.org,treib@chromium.org Change-Id: I8bf02633bad98c62a7cd3fdb2342517d505b330a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1502092Reviewed-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@{#637590}
-
Shu Chen authored
This cl doesn't change any behaviors. Bug: 937167 Change-Id: I35be2c76784d38c651f0e3d21a12e07a96b5e1af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1498253 Commit-Queue: Shu Chen <shuchen@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#637589}
-
Dan Beam authored
<extension-code-section> is used from 2 places in extensions (AFAICT), when showing where runtime errors come from and when showing errors trying to load an extension (i.e. manifest errors). This CL should confine "light mode" to just the actual code parts, and show the load errors in dark mode. Screenshots: https://imgur.com/a/gF1gd5D R=dpapad@chromium.org BUG=936524 Change-Id: I99b9cc56df1712c04023206a493a883d42d6fb8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1497804 Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Auto-Submit: Dan Beam <dbeam@chromium.org> Cr-Commit-Position: refs/heads/master@{#637588}
-
Simon Que authored
R=dpranke@chromium.org, hinoka@chromium.org, jbudorick@chromium.org Bug: 915568 Change-Id: I34e1cd438423e614db0652ff3c17f0832e8a6a82 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1500714Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: Simon Que <sque@chromium.org> Cr-Commit-Position: refs/heads/master@{#637587}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/b36f7a25a8a4..b8cff9e9347c git log b36f7a25a8a4..b8cff9e9347c --date=short --no-merges --format='%ad %ae %s' 2019-03-05 jiajia.qin@intel.com ES31: Add MAX_COMPUTE_SHARED_MEMORY_SIZE Created with: gclient setdep -r src/third_party/angle@b8cff9e9347c 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=cwallez@chromium.org Change-Id: I8e8805b73514e6ca255591b1cd09390bdd987d25 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1502094Reviewed-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@{#637586}
-
Jérôme Lebel authored
For some reasons, those metrics were not implemented for sign-in before unity. + Signin_Signin_WithDefaultSyncSettings + Signin_Signin_WithAdvancedSyncSettings This patch adds implementations for those 2 metrics for pre-unity and unity code. Also "Signin_Undo_Signin" is added for unity code (already implemented) with pre-unity. Bug: 937820 Change-Id: I27ec9769e9954b1daeccd273f4d663c35f9fa605 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1496981Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Commit-Queue: Jérôme Lebel <jlebel@chromium.org> Cr-Commit-Position: refs/heads/master@{#637585}
-
rbpotter authored
Only use color and duplex setByPolicy on Chrome OS, since these policies aren't implemented on other platforms. To make this simpler, move logic for computing whether any setting on the page is managed out of header.js and into model.js. This is also more reasonable since model.js is responsible for tracking the settings and is the only element where settings' |setByPolicy| field is updated. Change-Id: Ie682c38ffd775cccc4f47c15b66fa85a46761e20 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1500785Reviewed-by:
Hector Carmona <hcarmona@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#637584}
-
Donna Wu authored
Bug: 716628 Change-Id: If48a9b1aaa71a9264475dd0ad62707a45bd927e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1493716Reviewed-by:
Reilly Grant <reillyg@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Commit-Queue: Donna Wu <donna.wu@intel.com> Cr-Commit-Position: refs/heads/master@{#637583}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/4f63c40831f1..525c349dbfeb git log 4f63c40831f1..525c349dbfeb --date=short --no-merges --format='%ad %ae %s' 2019-03-05 dhanyaganesh@chromium.org BuildStore: Unittest for GetSlaveStatuses 2019-03-05 dhanyaganesh@chromium.org BuildStore: Redirect InsertBuildMessage & GetBuildMessages Created with: gclient setdep -r src/third_party/chromite@525c349dbfeb 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. CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel TBR=chrome-os-gardeners@chromium.org Change-Id: I01f56858d30011112969e431a5dfaf6376dd651d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1501854Reviewed-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@{#637582}
-
Dan Beam authored
No screenshots cuz I can't easily reproduce. And yes, this will mildly change the "light mode" (GB 500->700) but I think it's pretty clear that this UI is emulating a link and therefore should use the standard link colors. R=hcarmona@chromium.org BUG=926658 Change-Id: I6b9cc4697239edea6a165108935acb7ad2e07bff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1501795 Commit-Queue: Dan Beam <dbeam@chromium.org> Commit-Queue: Hector Carmona <hcarmona@chromium.org> Auto-Submit: Dan Beam <dbeam@chromium.org> Reviewed-by:
Hector Carmona <hcarmona@chromium.org> Cr-Commit-Position: refs/heads/master@{#637581}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/5800f2e8a920..fbc887df72ec git log 5800f2e8a920..fbc887df72ec --date=short --no-merges --format='%ad %ae %s' 2019-03-05 reed@google.com Revert "Remove (unnecessary?) flush in RenderYUVAToRGBA" 2019-03-04 recipe-roller@chromium.org Roll recipe dependencies (trivial). 2019-03-04 halcanary@google.com SkQP: fix five tests 2019-03-04 robertphillips@google.com Reduce usage of SkCanvas::flush 2019-03-04 fmalita@chromium.org Fix handling of SkSL nullable FPs 2019-03-04 mtklein@google.com mark lowp TODOs 2019-03-04 brianosman@google.com Add SkParticleValue to allow further customization of curve behavior 2019-03-04 herb@google.com Introduce SkStrikeCacheInterface 2019-03-04 egdaniel@google.com Add API for creating SkImage from AHB while uploading data to it. 2019-03-04 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/angle2 4d153383bd3a..0e1ce2e55387 (1 commits) 2019-03-04 robertphillips@google.com Clean up GrSurfaceContext's relationship with GrRecordingContext 2019-03-04 mtklein@google.com add kRGBA_F16Norm_SkColorType 2019-03-04 robertphillips@google.com Remove (unnecessary?) flush in RenderYUVAToRGBA 2019-03-04 skia-autoroll@skia-public.iam.gserviceaccount.com Roll ../src aae499d4..8e3cddfd (217 commits) 2019-03-04 halcanary@google.com SkQP: fix androidx (follows 2ccdd2bc1d0) 2019-03-04 robertphillips@google.com Remove peekProxy's side-effect behavior 2019-03-04 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader 823ca85404fb..bb305299f4de (1 commits) 2019-03-04 skia-recreate-skps@skia-swarming-bots.iam.gserviceaccount.com Update go_deps asset 2019-03-04 recipe-roller@chromium.org Roll recipe dependencies (trivial). Created with: gclient setdep -r src/third_party/skia@fbc887df72ec 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=reed@chromium.org Change-Id: Iefa4920baa09e09884108378028aaeefd39a7174 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1502093Reviewed-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@{#637580}
-
Kent Tamura authored
SECURITY_OWNERS should not be necessary to approve web_feature.mojom, but //PRESUBMIT.py asks to specify SECURITY_OWNERS for *.mojom. This CL adds per-file lines for web_features.mojom. Bug: 919393 Change-Id: Id2c99de603f13ee0cfd5c91ad40de93d4dba4b17 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1501195Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#637579}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=cmasso@chromium.org Change-Id: Ifc01a9d734470021084260cefcbf545dbf763d54 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1502213Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#637578}
-
Antonio Gomes authored
R=haraken@chromium.org CC=blink-reviews-vendor@chromium.org BUG=891908 Change-Id: I044f26b4cb2d2e0ae7ee0e1d55518765cdb34864 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1500972Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Cr-Commit-Position: refs/heads/master@{#637577}
-
Miyoung Shin authored
- short/int16_t -> uint16_t considering importing the value from web_bluetooth.mojom and exporting the value through bluetooth_advertising_event.idl. - Reference: https://google.github.io/styleguide/cppguide.html#Integer_Types Bug: 929985 Change-Id: Ib910dce00f0382fa7688547583d9c09d65272e5f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1501772Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Miyoung Shin <myid.shin@chromium.org> Cr-Commit-Position: refs/heads/master@{#637576}
-
Miyoung Shin authored
- short -> int16_t - No logic changes. - Reference: https://google.github.io/styleguide/cppguide.html#Integer_Types Bug: 929985 Change-Id: I6b22716e77ad858152a3255eb52204bb35a985ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1501237Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Miyoung Shin <myid.shin@chromium.org> Cr-Commit-Position: refs/heads/master@{#637575}
-
Nektarios Paisios authored
Line break elements are not defined as text nodes in Blink. However, traditionally we have been able to set a selection before or after a line break and our accessibility code on the browser side treats objects with the line break role as text objects. These tests ensure that line break elements are not treated as text objects for selection purposes. Also, adds more selection tests for text fields. R=dmazzoni@chromium.org, dtseng@chromium.org, aleventhal@chromium.org Change-Id: I4cf968225322a9bbc4eb2ace4b80c07dffc5a801 Bug: 639340 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1498611Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Nektarios Paisios <nektar@chromium.org> Commit-Queue: Nektarios Paisios <nektar@chromium.org> Cr-Commit-Position: refs/heads/master@{#637574}
-
Hector Carmona authored
Bug: 936624 Change-Id: Ifa7b57212f6de0346b5523ed6795f65d21b6e12d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1493374 Commit-Queue: Hector Carmona <hcarmona@chromium.org> Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Cr-Commit-Position: refs/heads/master@{#637573}
-
Malay Keshav authored
This patch adds an API to ui::Layers that lets clients set a rounded corner radius on the layer. The change is propagated to the cc layer and its effect node as well. Adds unit test for the change. Bug: 903486 Change-Id: Ib0d36af9e76b9f6701e0cb674e855e29f5844c7f Component: ui layer, cc layer, effect node Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1497851 Commit-Queue: Malay Keshav <malaykeshav@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
enne <enne@chromium.org> Cr-Commit-Position: refs/heads/master@{#637572}
-