- 02 Feb, 2018 40 commits
-
-
Darren Shen authored
Currently CSSStyleImageValue implements the CSSImageValue class in Typed OM. CSSImageValue can be anything that's an <image> i.e. a <url>, <gradient>, or <cross-fade>. However, the current implementation of CSSStyleImageValue only really works for <url>s. This patch moves <url> specific logic into CSSURLImageValue. This prepares for the implementation of <gradient> and <cross-fade>, which will be subclasses of CSSStyleImageValue. We also do some cleanup work (e.g. making things const, moving code in header to cpp). Bug: 803680 Change-Id: I848b3eab5dbbcb9bbe7f0aea0d377497f63bfda3 Reviewed-on: https://chromium-review.googlesource.com/882786 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by:
nainar <nainar@chromium.org> Cr-Commit-Position: refs/heads/master@{#533949}
-
Yuta Kitamura authored
TBR=wez@chromium.org Bug: 808138 Change-Id: I773d3238fb4140211cba071148d1c864930983c9 No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/897393 Commit-Queue: Yuta Kitamura <yutak@chromium.org> Reviewed-by:
Yuta Kitamura <yutak@chromium.org> Cr-Commit-Position: refs/heads/master@{#533948}
-
John Budorick authored
This reverts commit ca7f0798. Reason for revert: Seems to be breaking chromium.chromiumos bots w/ GS ACL issues: crbug.com/808312 Original change's description: > Automated Commit: Committing new LKGM version 10365.0.0 for chromeos. > > TBR=chrome-os-gardeners@google.com > > Change-Id: I3f6a6302f140de133d5e4419a7b2b93065537820 > Reviewed-on: https://chromium-review.googlesource.com/897844 > Reviewed-by: ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> > Cr-Commit-Position: refs/heads/master@{#533936} TBR=chrome-os-gardeners@google.com,chromeos-commit-bot@chromium.org Change-Id: Ie67db1d4d475a25adee37edaade0c3234322905e No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/898642Reviewed-by:
John Budorick <jbudorick@chromium.org> Cr-Commit-Position: refs/heads/master@{#533947}
-
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: I0077afe015482b328614da282966a4886f74eebc Reviewed-on: https://chromium-review.googlesource.com/898662Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#533946}
-
Sean Kau authored
We need notification of reference invalidation for ExternalPrinters objects. So, change to distributing WeakPtrs instead of raw pointers. Bug: 805825 Change-Id: I06aee8e91df490ceae8fd8fe671e31472ae316fd Reviewed-on: https://chromium-review.googlesource.com/891574 Commit-Queue: Sean Kau <skau@chromium.org> Reviewed-by:
Xiaoqian Dai <xdai@chromium.org> Reviewed-by:
Achuith Bhandarkar <achuith@chromium.org> Cr-Commit-Position: refs/heads/master@{#533945}
-
Siddhartha authored
GetOrCreateAllocatorDump() was exposed for a particular case where multiple dump providers need to create same dump. Using this method in common providers lead to errors in reporting. R=dskiba@chromium.org Change-Id: I164574f635ab316390778eefd5b4b0c0c8ef5da5 Reviewed-on: https://chromium-review.googlesource.com/892491Reviewed-by:
Dmitry Skiba <dskiba@chromium.org> Commit-Queue: Siddhartha S <ssid@chromium.org> Cr-Commit-Position: refs/heads/master@{#533944}
-
Matt Giuca authored
These labels are treated specially by the parser, and need tests. We test both valid xn-- domain labels (ASCII only), as well as xn-- labels that contain Unicode characters (which are invalid). Bug: 804462 Change-Id: I943034745bdf65ae3b6df77c5ed8cb95a590a105 Reviewed-on: https://chromium-review.googlesource.com/897286Reviewed-by:
Mike West <mkwst@chromium.org> Commit-Queue: Matt Giuca <mgiuca@chromium.org> Cr-Commit-Position: refs/heads/master@{#533943}
-
Matt Falkenhagen authored
Previously, if the <video> src was same-origin as the page, and the service worker intercepted the request and responded with an opaque response (by making a cross-origin request without CORS sharing), the <video> would be considered same-origin data. The solution is to teach the data backing <video> about FetchResponseType, which tells us if a response is opaque or non-opaque. There is some complexity with multiple responses due to range requests/ partial content responses. It's possible that some responses are opaque and some are non-opaque. Once the opaque bit is set, it shouldn't be cleared. This fixes tests added in: https://chromium-review.googlesource.com/c/chromium/src/+/892683 and https://chromium-review.googlesource.com/c/chromium/src/+/897165 Bug: 780435 Change-Id: I95f7f088d907f84edd4c2db8b57532e761237465 Reviewed-on: https://chromium-review.googlesource.com/828564Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Tsuyoshi Horo <horo@chromium.org> Reviewed-by:
Fredrik Hubinette <hubbe@chromium.org> Commit-Queue: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#533942}
-
https://pdfium.googlesource.com/pdfium.git/+log/59790cef1a09..f7c84e910899 $ git log 59790cef1..f7c84e910 --date=short --no-merges --format='%ad %ae %s' 2018-02-02 thestig Fix IWYU errors in fpdfppo.cpp. 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: Ibc52bf576b7449bbeaa035f348c33bc91876a95a Reviewed-on: https://chromium-review.googlesource.com/898586Reviewed-by:
pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#533941}
-
Wez authored
Unlike the existing Linux warnings, this is enabled for Fuchsia including Chromecast and Ozone builds. Bug: 177475, 808138 Change-Id: Idaf85eabbf3029f37c9c37c7b1bd8f03e411a9d1 Reviewed-on: https://chromium-review.googlesource.com/898007 Commit-Queue: Wez <wez@chromium.org> Reviewed-by:
Scott Graham <scottmg@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Reviewed-by:
Maks Orlovich <morlovich@chromium.org> Cr-Commit-Position: refs/heads/master@{#533940}
-
Xianzhu Wang authored
- Move PropertyTreeStatePrinter from PropertyTreeState.h into PaintPropertyNode.h and rename it to PropertyTreePrinter. - Remove duplicated code originally in platform/.../PropertyTreeState.h and core/.../PaintPropertyTreePrinter.cpp and let PaintPropertyTreePrinter use the new PropertyTreePrinter in platform/.../PaintPropertyNode.h - Add PaintPropertyNode::DebugName (DCHECK only) to store annotations for the node, so that we can also see them in the result of ToString() and ToTreeString(). This will help debugging property tree states in platform/ code. - Remove paintPropertyTreeGraph which is out-dated and unlikely to be maintained. - Other code cleanup and simplification Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: I02cdf3f054110a63190997db9f7543b6c254eb22 Reviewed-on: https://chromium-review.googlesource.com/897825 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
vmpstr <vmpstr@chromium.org> Cr-Commit-Position: refs/heads/master@{#533939}
-
https://skia.googlesource.com/skia.git/+log/e45d32abe132..85ae7159c9c8 $ git log e45d32abe..85ae7159c --date=short --no-merges --format='%ad %ae %s' 2018-02-01 bsalomon Add new GrContext queries for imagability, surfacability, and max sample count of color types 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;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 TBR=bungeman@chromium.org Change-Id: Ibf3a252c640f3be1e0a3715082a43e11453cb94b Reviewed-on: https://chromium-review.googlesource.com/898585Reviewed-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@{#533938}
-
Timothy Loh authored
This patch implements UKM for permission actions, alongside the current reporter which uses the SafeBrowsing service. For now we handle exactly the set of actions which the current reporting handles for prompts, but revocations are not yet reported. The logged URL is the top frame's url even for prompts from an iframes, as UKM does not permit logging iframe urls. This is fine as the upcoming permission delegation work will make those prompts request under the top frame's origin. Bug: 793202 Change-Id: I7b1d7a022c436eb8cbb458c1655f6ee81bdb88eb Reviewed-on: https://chromium-review.googlesource.com/872371 Commit-Queue: Timothy Loh <timloh@chromium.org> Reviewed-by:
Raymes Khoury <raymes@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Cr-Commit-Position: refs/heads/master@{#533937}
-
chromeos-commit-bot@chromium.org authored
TBR=chrome-os-gardeners@google.com Change-Id: I3f6a6302f140de133d5e4419a7b2b93065537820 Reviewed-on: https://chromium-review.googlesource.com/897844Reviewed-by:
ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#533936}
-
Dmitry Gozman authored
Bug: none Change-Id: I875bf9ad5eea00d1c1965ac280d0dce46215624b Reviewed-on: https://chromium-review.googlesource.com/896871Reviewed-by:
Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Commit-Queue: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#533935}
-
Yoshifumi Inoue authored
This patch changes "remove-underline-across-paragraph{,-bold}.html" to utilize |selection_test()| for ease of maintenance. Note: Both tests use similar test case, this patch puts them into one file. Bug: 679977 Change-Id: Ic80aa10d94210016fec484ff93262e9346e4639d Reviewed-on: https://chromium-review.googlesource.com/897309Reviewed-by:
Yoichi Osato <yoichio@chromium.org> Commit-Queue: Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#533934}
-
Yoshifumi Inoue authored
This patch changes "overtype.html" to utilize |selection_test()| for ease of maintenance. This patch is a preparation for the patch[1]. [1] http://crrev.com/c/737981 Introduce TextOffsetMapping to simplify word/paragraph selection Bug: 679977 Change-Id: I9a043b5537dc188a46984d62708ad98dcd9b933b Reviewed-on: https://chromium-review.googlesource.com/897306Reviewed-by:
Yoichi Osato <yoichio@chromium.org> Commit-Queue: Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#533933}
-
Yoshifumi Inoue authored
This patch changes "remove-format-multiple-elements-{mac,-win}.html" into "remove-format-multiple-elements.html" with utilizing |selection_test()| for ease of maintenance. Because of test cases specify selected range directly instead of using |Selection#modify()|, test cases are independent from platform, e.g. selecting whitespaces after word. Bug: 679977 Change-Id: I2dd807062a1c1547072a2407057f8b400b98b7c1 Reviewed-on: https://chromium-review.googlesource.com/896764Reviewed-by:
Yoichi Osato <yoichio@chromium.org> Commit-Queue: Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#533932}
-
Yoshifumi Inoue authored
This patch renames "pasteboard/5032095.html" to "inserting/insert_html_at_end_of_paragraph.html" to provide what this test verifies from file name for improving code health. Because of this test verifies "insertHTML" command instead of clipboard, this patch moves this file to "editing/inserting" directory. This is a follow-up the patch[1]. [1] http://crrev.com/c/892552 Rewrite editing/pasteboard/5032095.html to use selection_test() Bug: 679977 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: If90700169e84c2e6c9381a55a5397cc7bff05368 Reviewed-on: https://chromium-review.googlesource.com/897226Reviewed-by:
Yoichi Osato <yoichio@chromium.org> Commit-Queue: Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#533931}
-
v8-autoroll authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/ad9e8781..6c1a69bb Please follow these instructions for assigning/CC'ing issues: https://github.com/v8/v8/wiki/Triaging%20issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_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;master.tryserver.chromium.android:android_optional_gpu_tests_rel TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org Change-Id: I7928bf761af3d32bb85d3cccd295e7acd72f784b Reviewed-on: https://chromium-review.googlesource.com/897843Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#533930}
-
Yoshifumi Inoue authored
Rewrite editing/selection/doubleclick-inline-first-last-contenteditable.html to use selection_test() This patch changes "doubleclick-inline-first-last-contenteditable.html" to utilize |selection_test()| for ease of maintenance. Bug: 679977 Change-Id: Id65f597b65a031ff4a6ce2137373b03905e6b839 Reviewed-on: https://chromium-review.googlesource.com/896903Reviewed-by:
Yoichi Osato <yoichio@chromium.org> Commit-Queue: Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#533929}
-
Dirk Pranke authored
The mac10.13_blink_rel was not running any tests, because the builder it was set up to mirror ("Dummy WebKit Mac10.13") was on the wrong waterfall. R=robertma@chromium.org BUG=807817 Change-Id: I067f5f12dde2cdca89959ec59afeaed45d2296cc Reviewed-on: https://chromium-review.googlesource.com/898210 Commit-Queue: Dirk Pranke <dpranke@chromium.org> Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Reviewed-by:
Robert Ma <robertma@chromium.org> Cr-Commit-Position: refs/heads/master@{#533928}
-
Menglu Huang authored
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs Change-Id: Ie4729da59a1e03797ada6b29c74b95d437837a70 Reviewed-on: https://chromium-review.googlesource.com/898441Reviewed-by:
smut <smut@google.com> Commit-Queue: Menglu Huang <huangml@chromium.org> Cr-Commit-Position: refs/heads/master@{#533927}
-
https://chromium.googlesource.com/angle/angle.git/+log/5c5d7deef28d..95ed19473fb6 $ git log 5c5d7deef..95ed19473 --date=short --no-merges --format='%ad %ae %s' 2018-02-01 oetuaho Add a class for function lookups Created with: roll-dep src/third_party/angle The AutoRoll server is located here: https://angle-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.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 TBR=jmadill@chromium.org Change-Id: I7dcb3c4d770c871511b90025916d132b46194012 Reviewed-on: https://chromium-review.googlesource.com/898487Reviewed-by:
angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#533926}
-
Andrii Shyshkalov authored
https://crrev.com/c/881949 Making tarring isolate deterministic. R=maruel Bug: 804869 Change-Id: I3d4582eb9aa55aa764778b48027081e1d106d310 Reviewed-on: https://chromium-review.googlesource.com/898524Reviewed-by:
Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org> Cr-Commit-Position: refs/heads/master@{#533925}
-
Chris Cunningham authored
This is mostly a reland of https://chromium-review.googlesource.com/c/chromium/src/+/807604 with some improvements and now unblocked by changes to bots. Media layout tests need repair 1) Many tests check for proprietary codec support by only asking about "video/mp4" without specifying a codec. This check is busted because MP4 is no longer considered proprietary while codecs like H264 and AAC still are. We currently claim "video/mp4" is entirely unsupported via test hacks to avoid breaking those checks. 2) Some MSE tests focus on MP4 with H264. While many bots now have the needed codecs, we artificially remove their support via test-only hacks in order to keep expectations the same for all runners. This CL does the following 1) Remove incomplete checks for "video/mp4" - instead hardcode use of the .ogv files (preserving the existing behavior). 2) Update MSE mp4/h264 test expectations to PASS|FAIL. This gives us some coverage on bots with proprietary codecs while allowing failure on bots that lack codecs. 3) Remove test hacks that artificially reduce codec support. It is also not a goal to make LayoutTests try all the supported codecs. That is covered by unit/integration tests. Due to 3) above, some external/wpt/media-source tests now fail because they select mp4. Fixing these failures is tracked in Issue 794338. Bug: 327115,746579,787575,568704,794338,807110 Change-Id: I05565d7ca9d8d5b12391785888701723810671d5 Reviewed-on: https://chromium-review.googlesource.com/849641 Commit-Queue: Chrome Cunningham <chcunningham@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Peter Beverloo <peter@chromium.org> Reviewed-by:
Matthew Wolenetz <wolenetz@chromium.org> Cr-Commit-Position: refs/heads/master@{#533924}
-
Junliang Yan authored
Exclude gpu support since these platforms only need to build gn, which doesn't need graphic support. Change-Id: I74702eb03e6b73d38540560f03cf4d95543f0c1c Reviewed-on: https://chromium-review.googlesource.com/897684Reviewed-by:
Antoine Labour <piman@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#533923}
-
Marc-Antoine Courteau authored
R=stevenjb Bug: 808083 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I56dd69d92dd24393d63180449ab124ce93986652 Reviewed-on: https://chromium-review.googlesource.com/898078 Commit-Queue: Marc-Antoine Courteau <macourteau@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/heads/master@{#533922}
-
Bill Budge authored
- Goes through SecurityOrigin's ArrayBuffer Partition for ArrayBuffers allocated from the V8 side. - Reworks ArrayBufferContents to support multiple partitions for ArrayBuffers. Adds overload of AllocateMemoryOrNull to handle these allocations. Associates a PartitionRootGeneric with each allocation, storing a pointer just before the ArrayBuffer data. Bug:chromium:799573 Change-Id: I712176c715d1fb2511d87892052ba9d2d8084336 Reviewed-on: https://chromium-review.googlesource.com/853120Reviewed-by:
Chris Palmer <palmer@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Bill Budge <bbudge@chromium.org> Cr-Commit-Position: refs/heads/master@{#533921}
-
Wang Qing authored
This change enable tcmalloc on mips64el. BUG= nobug R= dpranke@chromium.org Change-Id: I6927ddf0b267caba539fc8b461d6ed0e822d6e30 Reviewed-on: https://chromium-review.googlesource.com/896967Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Commit-Queue: 汪 清 <wangqing-hf@loongson.cn> Cr-Commit-Position: refs/heads/master@{#533920}
-
Peter Boström authored
Highlights the location-bar passwords icon even when the dialog is triggered without user interaction (for instance when prompting the user to save credentials). This is done similarly to highlighting the StarView when the bookmark bubble shows. Bug: chromium:654115 Change-Id: Ia8f3a7020336186c83a1aa8ec997c9abd73b8f6a Reviewed-on: https://chromium-review.googlesource.com/898588 Commit-Queue: Peter Boström <pbos@chromium.org> Reviewed-by:
Bret Sepulveda <bsep@chromium.org> Cr-Commit-Position: refs/heads/master@{#533919}
-
Yutaka Hirano authored
As discussed at [1], it is reasonable to set per-process and global limits on the number of requests with keepalive set in order to prevent DOS. 1: https://groups.google.com/a/chromium.org/forum/m/#!topic/blink-dev/8vqcABTnDF4 Bug: 764589 Change-Id: I595cfc00b7d5c6008f39b1ea2f8b0927ae63908d Reviewed-on: https://chromium-review.googlesource.com/895422 Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
Takeshi Yoshino <tyoshino@chromium.org> Cr-Commit-Position: refs/heads/master@{#533918}
-
dpapad authored
Bug: 808182 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I02f96d49f3dffcde80f0bca06d1d588d080c743f Reviewed-on: https://chromium-review.googlesource.com/898403Reviewed-by:
Hector Carmona <hcarmona@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#533917}
-
https://chromium.googlesource.com/catapult.git/+log/d2080c565153..744dac913652 $ git log d2080c565..744dac913 --date=short --no-merges --format='%ad %ae %s' 2018-02-01 dtu [pinpoint] Add Kolmogorov-Smirnov test. 2017-11-10 benjhayden Replace RelatedHistogramBreakdown in longTasksMetric with RelatedNameMap. 2018-02-01 eakuefner [Telemetry] Add ShouldAddValue hook to replace ValueCanBeAddedPredicate 2018-02-01 magda.zawora Remove system_stub from archive_info_unittest.py Issue #3115 Created with: roll-dep src/third_party/catapult The AutoRoll server is located here: https://catapult-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.android:android_optional_gpu_tests_rel TBR=sullivan@chromium.org Change-Id: I85d9b25939570f6274c73cd4c7cf251fa5adc372 Reviewed-on: https://chromium-review.googlesource.com/898390Reviewed-by:
catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#533916}
-
CJ Dimeglio authored
This CL makes it so that if |stretch_to_fit_bounds| is set on a surface, damage calculation takes this into account and scales the damage quad accordingly. Bug: 799512 Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel Change-Id: I405ae815046d7ab51179bfceb0e54db9e5749725 Reviewed-on: https://chromium-review.googlesource.com/887789 Commit-Queue: CJ DiMeglio <lethalantidote@chromium.org> Reviewed-by:
enne <enne@chromium.org> Cr-Commit-Position: refs/heads/master@{#533915}
-
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/f2b5774fef6a..e150d63db9f7 $ git log f2b5774fe..e150d63db --date=short --no-merges --format='%ad %ae %s' 2018-02-01 sergeyberezin Roll mac_toolchain to d4dc0c2 Created with: roll-dep src/third_party/depot_tools BUG=797051 The AutoRoll server is located here: https://depot-tools-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=agable@chromium.org Change-Id: Idf59e37b339c8fe1f693b456bf8310b22a3a647e Reviewed-on: https://chromium-review.googlesource.com/898220 Commit-Queue: depot-tools-chromium-autoroll <depot-tools-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
depot-tools-chromium-autoroll <depot-tools-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#533914}
-
David Bokan authored
This relands r532919 which was reverted in r533667 The original patch worked only in the initial case but the corrected layer bounds were clobbered in ScrollingCoordinator::ScrollableAreaScrollLayerDidChange. Even though CompositedLayerMapping::UpdateScrollingLayerGeometry is always called after this method, in ScrollingCoordinator the bounds are set directly on the WebLayer. In CLM we set the bounds on a GraphicsLayer which caches the size itself. It'll only update the WebLayer bounds if the new size differs from the cached size. Thus, even though the bounds were changed in ScrollingCoordinator, CLM would early out since it the GraphicsLayer size hasn't changed. This CL applies the same fix in ScrollingCoordinator and also adds a new test that covers the linked bug more end-to-end. The original patch is uploaded in patchset 1 for easy diff'ing. Bug: 801381 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: I28f7088ef6b429875c6c984c45fd1c53cf813c02 Reviewed-on: https://chromium-review.googlesource.com/897962Reviewed-by:
Tien-Ren Chen <trchen@chromium.org> Commit-Queue: David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#533913}
-
Sebastien Marchand authored
Make Startup.BrowserMessageLoopStartHardFaultCount be gathered from a TaskPriority::BACKGROUND task Bug: 784853 Change-Id: Ia8772f9e66a20dabbd6e8fd7c73588bed421f9bc Reviewed-on: https://chromium-review.googlesource.com/884377 Commit-Queue: Sébastien Marchand <sebmarchand@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#533912}
-
Peter Boström authored
Bug: chromium:807886 Change-Id: I1eb8ed1c1ddd6e07ba38f63f66a140a0a524c356 Reviewed-on: https://chromium-review.googlesource.com/898523Reviewed-by:
Bret Sepulveda <bsep@chromium.org> Commit-Queue: Peter Boström <pbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#533911}
-
Kent Tamura authored
This reverts commit 9b477bca. Reason for revert: We should deprecate the feature first. Original change's description: > Remove extra form data, if "value" attribute present with non-empty value > > This patch removes the extra form data added, if "value" attribute > present with non-empty value for <input type='image'> > > Intent to Deprecate and Remove: > https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/hp1_-1tgvDs > > Bug: 753746 > Change-Id: I1de9a0c9babd9d16b45e5eefa780370fff8c75e9 > Reviewed-on: https://chromium-review.googlesource.com/896905 > Reviewed-by: Kent Tamura <tkent@chromium.org> > Commit-Queue: Shanmuga Pandi <shanmuga.m@samsung.com> > Cr-Commit-Position: refs/heads/master@{#533655} TBR=tkent@chromium.org,foolip@chromium.org,shanmuga.m@samsung.com Change-Id: I97c5987adba9eaa097808f7a35c54859217edd2e No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 753746 Reviewed-on: https://chromium-review.googlesource.com/897264Reviewed-by:
Kent Tamura <tkent@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#533910}
-