- 14 Sep, 2018 40 commits
 - 
- 
Chromium WPT Sync authored
Using wpt-import in Chromium e8664ecd. With Chromium commits locally applied on WPT: d8d86dd3 "Implement Feature-Policy: lazyload" Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/24693 Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md NOAUTOREVERT=true TBR=markdittmer No-Export: true Change-Id: I21ee910b57973a08b07aaa9dd9db9037ce841d1e Reviewed-on: https://chromium-review.googlesource.com/1226815 Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Reviewed-by:
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Cr-Commit-Position: refs/heads/master@{#591333}
 - 
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://autoroll.skia.org/r/afdo-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=gbiv@chromium.org Change-Id: I80efaaf408717d3fb21fc379cb4f0128d06fe0e4 Reviewed-on: https://chromium-review.googlesource.com/1226817Reviewed-by:
afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#591332}
 - 
Balazs Engedy authored
Bug: 881321 Change-Id: Ie6b3476a9c8dc14734f545b6dbe7cc8f6b85ca03 Reviewed-on: https://chromium-review.googlesource.com/1221324 Commit-Queue: Balazs Engedy <engedy@chromium.org> Reviewed-by:
Jun Choi <hongjunchoi@chromium.org> Cr-Commit-Position: refs/heads/master@{#591331}
 - 
Sergey Poromov authored
This change removes enterprise_default for PacHttpsUrlStrippingEnabled, that was set to "False" and now all users should have it set to "True". Long-term security-wise the behavior should be that URLs are always stripped for Pac proxies, i.e.as the policy set to "True". We are keeping ability to change the policy in server-side configuration to "False" in case customers will be broken by the change. Otherwise, the policy is going to be deprecated in M74. Bug: 619087 Change-Id: I29db0211ced988b0fde5efaf3ce7863466bffb6e Reviewed-on: https://chromium-review.googlesource.com/1224449 Commit-Queue: Sergey Poromov <poromov@chromium.org> Reviewed-by:
Eric Roman <eroman@chromium.org> Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Cr-Commit-Position: refs/heads/master@{#591330}
 - 
Xida Chen authored
TBR=alexmos@chromium.org Bug: None Change-Id: I4654e5ff379aafd783a0cf578c0ccbf488baa134 Reviewed-on: https://chromium-review.googlesource.com/1226521Reviewed-by:
Xida Chen <xidachen@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#591329}
 - 
Yi Su authored
This feature is ready for shipping, enable the flag by default. Bug: 163201 Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs Change-Id: Iffcc4f61b162d507975507898c55ea2450b87e25 Reviewed-on: https://chromium-review.googlesource.com/1221262 Commit-Queue: Eric Noyau <noyau@chromium.org> Reviewed-by:
Eric Noyau <noyau@chromium.org> Cr-Commit-Position: refs/heads/master@{#591328}
 - 
Maja Kabus authored
Types. New implementations of DOMWindowTimers::setTimeout() and setInterval() added to accept TrustedScript as an argument. Previously existing implementations renamed to setTimeoutFromString() and setIntervalFromString(), respectively. Bug: 739170 Change-Id: I3513ebb651534f0b1ef1b8de9c694136b02e2412 Reviewed-on: https://chromium-review.googlesource.com/1179899Reviewed-by:
Mike West <mkwst@chromium.org> Reviewed-by:
Yuki Shiino <yukishiino@chromium.org> Commit-Queue: Maja Kabus <kabusm@google.com> Cr-Commit-Position: refs/heads/master@{#591327}
 - 
Mike West authored
`http://127.0.0.1` does not need to be upgraded, as it's "potentially trustworthy" in and of itself. Bug: 824462 Change-Id: I6e67abf258557e6be97ba1540f363c8586a5a24e Reviewed-on: https://chromium-review.googlesource.com/1224390Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Reviewed-by:
Carlos IL <carlosil@chromium.org> Reviewed-by:
Andy Paicu <andypaicu@chromium.org> Reviewed-by:
Adam Rice <ricea@chromium.org> Commit-Queue: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#591326}
 - 
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/e899629be4d8..af6c139eb6ff git log e899629be4d8..af6c139eb6ff --date=short --no-merges --format='%ad %ae %s' 2018-09-14 saza@webrtc.org Drop legacy AEC metrics interface from ApmTest.Process 2018-09-14 maxmorin@webrtc.org Revert "Reland Profile 2 to default profiles" 2018-09-14 henrik.lundin@webrtc.org Let NetEq use the PLC output from a decoder Created with: gclient setdep -r src/third_party/webrtc@af6c139eb6ff 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: I5c07cff51ee5949db9b7a29121fff98a60a7990d Reviewed-on: https://chromium-review.googlesource.com/1226378Reviewed-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@{#591325}
 - 
Tomasz Moniuszko authored
Potentially dangerous situation is possible when user is performing double-click on UI element. If bubble is being shown as a result of the first click, the control under the mouse cursor (button on the bubble) can be activated with the second click. This wasn't the intention of the user as the time between clicks was too short to read the contents in the bubble that appeared. For example, user can accidentally click "Accept" button on the permission prompt bubble. This CL adds protection against such unintended clicks. Mouse and touch events are ignored for a short period of time after bubble has been shown. Bug: 864530 Change-Id: I54d229bf39dd000079b9eabd8de1cfba5103a022 Reviewed-on: https://chromium-review.googlesource.com/1140307 Commit-Queue: Tomasz Moniuszko <tmoniuszko@opera.com> Reviewed-by:
Michael Wasserman <msw@chromium.org> Cr-Commit-Position: refs/heads/master@{#591324}
 - 
Mirko Bonadei authored
Not a real change to libsrtp itself but just a rename of //third_party/libsrtp/VERSION to //third_party/libsrtp/LIBSRTP_VERSION in order to avoid issues with libc++. Bug: 883897 Change-Id: Iccd0dcc5ee1e3e9339ecbf96f3b6d7844d8fc135 Reviewed-on: https://chromium-review.googlesource.com/1225873 Commit-Queue: Nico Weber <thakis@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#591323}
 - 
Matthew Cary authored
This is helpful for local testing, where our older devices are getting flaky, and will eventually be necessary when the bot upgrades. Bug: 758566 Change-Id: If1d36f17c3ffd8605d14ab1aa30d4df0acafc3ad Reviewed-on: https://chromium-review.googlesource.com/1219688Reviewed-by:
Egor Pasko <pasko@chromium.org> Reviewed-by:
Benoit L <lizeb@chromium.org> Commit-Queue: Matthew Cary <mattcary@chromium.org> Cr-Commit-Position: refs/heads/master@{#591322}
 - 
jchen10 authored
This exposes KHR_parallel_shader_compile extension to WebGL. With this extension, applications may benefit from background shader compilation and program linking, avoiding main thread long blocking for complex shaders. BUG=849576 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 Change-Id: I6b62142d28dc14f85d50a820e6a87409d5a371c8 Reviewed-on: https://chromium-review.googlesource.com/1161747Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Jie A Chen <jie.a.chen@intel.com> Cr-Commit-Position: refs/heads/master@{#591321}
 - 
Gauthier Ambard authored
This CL adds a snackbar for the copy action from the share menu. It also consolidates metrics for the different actions of the share menu. Bug: 880030, 883642 Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs Change-Id: I9ad39ad2f4f9b34e4d26aacc12a9db1fb2364bb6 Reviewed-on: https://chromium-review.googlesource.com/1224311Reviewed-by:
Mark Pearson <mpearson@chromium.org> Reviewed-by:
Peter Lee <pkl@chromium.org> Commit-Queue: Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#591320}
 - 
Michael van Ouwerkerk authored
There's a sample crash report at crash/29c8dbdcacdc72b1 see Fields > Product data > loaded_dynamic_module Bug: 865935 Change-Id: Iceef1eea20064565e08712cb087850818a34f581 Reviewed-on: https://chromium-review.googlesource.com/1216363Reviewed-by:
Peter Conn <peconn@chromium.org> Commit-Queue: Michael van Ouwerkerk <mvanouwerkerk@chromium.org> Cr-Commit-Position: refs/heads/master@{#591319}
 - 
Chromium WPT Sync authored
Using wpt-import in Chromium f861aa1a. With Chromium commits locally applied on WPT: d8d86dd3 "Implement Feature-Policy: lazyload" Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/24692 Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md NOAUTOREVERT=true TBR=markdittmer No-Export: true Change-Id: Ia8b9f6ea7856428a7574f7435da9eb936deabd0c Reviewed-on: https://chromium-review.googlesource.com/1226814 Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Reviewed-by:
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Cr-Commit-Position: refs/heads/master@{#591318}
 - 
Eric Seckler authored
This makes ThreadWatcherTest compatible for use of TestBrowserThreadBundle to prepare for the upcoming PostTask refactor. The TestBrowserThreadBundle initializes globals that will be required to post a task to or obtain a TaskRunner for a BrowserThread. This is a more involved change, since ThreadWatcherTest currently runs the UI thread on a separate thread from the main thread. Since this is not supported by TBTB, this change also refactors the test architecture. The tests now use the WatchDogThread to verify expectations and wait for state changes on the ThreadWatcher objects. This is closer to the way ThreadWatcher would be used in practice. State changes are now observed on the WatchDogThread, too, eliminaing the need for some locking, and signalling uses nested RunLoops instead of condition variables where possible. Bug: 878356 Change-Id: I6e759b140c7544b7abbdb8fd59f6a51163dc31e4 Reviewed-on: https://chromium-review.googlesource.com/1222891Reviewed-by:
Ilya Sherman <isherman@chromium.org> Commit-Queue: Eric Seckler <eseckler@chromium.org> Cr-Commit-Position: refs/heads/master@{#591317}
 - 
Alex Clarke authored
This class's job is to map base::TaskTraits to actual task queues for the browser process. This was split off from https://chromium-review.googlesource.com/c/chromium/src/+/1214223 and is a pre-requisite for the BrowserUIThreadScheduler. Design doc: https://docs.google.com/document/d/1z1BDq9vzcEpkhN9LSPF5XMnZ0kLJ8mWWkNAi4OI7cos/edit# BUG=863341, 872372 Change-Id: Ic80e8f66cf245cca136c29387031d111e57fa713 Reviewed-on: https://chromium-review.googlesource.com/1224115 Commit-Queue: Alex Clarke <alexclarke@chromium.org> Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Reviewed-by:
Eric Seckler <eseckler@chromium.org> Cr-Commit-Position: refs/heads/master@{#591316}
 - 
Philip Jägenstedt authored
In preparation for removing document.origin. Bug: 692084 Change-Id: I24b73ef0e6e5ab0317d2d6c25faec5a4c8a54512 Reviewed-on: https://chromium-review.googlesource.com/1170686Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Commit-Queue: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#591315}
 - 
Matthew Cary authored
There are frequently a small number of symbols that are repeated with different offsets. These are benign but cause some annoyances, for example they can make it appear that a binary is not ordered correctly, necessitating the threshold used in check_orderfile.py (q.v.). This CL adds a small amount of logging for the repeated symbols that will make it easier to see the cause if a larger number of symbols get repeated. Bug: 758566 Change-Id: I04038bebec38b1b38e5667a578e7b4e06ac6060d Reviewed-on: https://chromium-review.googlesource.com/1201853Reviewed-by:
Benoit L <lizeb@chromium.org> Commit-Queue: Matthew Cary <mattcary@chromium.org> Cr-Commit-Position: refs/heads/master@{#591314}
 - 
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/c12805f8..9e11a283 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;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: Ieee24a047a868e919a019dbf6a66d60f4f013fc0 Reviewed-on: https://chromium-review.googlesource.com/1226528Reviewed-by:
V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#591313}
 - 
Kuo-Hsin Yang authored
The serving dir is also included by the pages. Bug: chromium:883798 Change-Id: Ifb67e19b03303e4929a0e588f5450707adec4835 Reviewed-on: https://chromium-review.googlesource.com/1226484Reviewed-by:
Ned Nguyen <nednguyen@google.com> Commit-Queue: Vovo Yang <vovoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#591312}
 - 
Philipp Hancke authored
BUG=webrtc:7063 Change-Id: I6436a1f9ebcb34bbc770ee4f1792e6636aa8efa4 Reviewed-on: https://chromium-review.googlesource.com/1204097 Commit-Queue: Henrik Boström <hbos@chromium.org> Reviewed-by:
Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#591311}
 - 
Kent Tamura authored
This CL introduces mojo struct FileChooserParams, and replaces content::FileChooserParams with it. - We transfer the mojo struct over a legacy IPC message temporarily. Following CLs will remove the legacy IPC message. - Update blink::WebFileChooserParams so that it matches to the mojo struct. FYI: All-in-one CL: https://chromium-review.googlesource.com/1170454 Bug: 869257 Change-Id: If9ebd72bb1d69cb1a6d2b282d82ec940ae103748 Reviewed-on: https://chromium-review.googlesource.com/1195242Reviewed-by:
Richard Coles <torne@chromium.org> Reviewed-by:
Istiaque Ahmed <lazyboy@chromium.org> Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#591310}
 - 
Oskar Sundbom authored
There's no point in registering before having gotten an AudioProcessorControls to proxy to. Registering too early means it'll discard the request to start an AEC dump. I also simplified SetControls, as it should only be called once. The current structure was left behind from when the plan was to call it with nullptr to detach from the controls. Bug: 851959 Change-Id: I4470a127fb6e22aa1b6fe4dd8a0b9bd0866514a4 Reviewed-on: https://chromium-review.googlesource.com/1224930Reviewed-by:
Max Morin <maxmorin@chromium.org> Commit-Queue: Oskar Sundbom <ossu@chromium.org> Cr-Commit-Position: refs/heads/master@{#591309}
 - 
Lei Zhang authored
Some users with Cinnamon use gnome-control-center for native printer management. So try launching it for Cinnamon users. BUG=869845 Change-Id: Icbb73dd4db72c5151175015ffd8e6d0aaae76cf4 Reviewed-on: https://chromium-review.googlesource.com/1226529Reviewed-by:
Christian Dullweber <dullweber@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#591308}
 - 
David Jean authored
Added handling of multiple edits by showing navigation bar when results are visible and handling any operation that would use the original root_node. Bug: 879570 Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs Change-Id: I451006aa456bcc494583aed58820e405d04852c0 Reviewed-on: https://chromium-review.googlesource.com/1213174 Commit-Queue: David Jean <djean@chromium.org> Reviewed-by:
Sergio Collazos <sczs@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#591307}
 - 
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/64b0fb599517..66261f1ac2b7 git log 64b0fb599517..66261f1ac2b7 --date=short --no-merges --format='%ad %ae %s' 2018-09-14 csmartdalton@google.com ccpr: Don't release the stashed atlas proxy inside CopyAtlasOp Created with: gclient setdep -r src/third_party/skia@66261f1ac2b7 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=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=caryclark@chromium.org Change-Id: I81d568ed3c405536bd8a237635e39e55ff90b91d Reviewed-on: https://chromium-review.googlesource.com/1226376Reviewed-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@{#591306}
 - 
Kunihiko Sakamoto authored
In b2 format, CBOR header no longer appears at the first line of the xxd output. Bug: 803774 Change-Id: I57b8a3833cbc2ec7339346244fe23099680f6a86 Reviewed-on: https://chromium-review.googlesource.com/1226754Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#591305}
 - 
Rune Lillesveen authored
Style invalidation, style recalc, and layout tree rebuild all starts from the document root looking for dirty nodes which needs updating. That means we have unnecessary overhead traversing down to the dirty nodes, in particular when the number of dirty nodes are few and they have ancestors with many siblings. The overhead is mlog(n), if the depth to the dirty node(s) is n and the number of siblings for each ancestor is m. In particular, this overhead was noticed for the whatwg single page HTML spec where a lot of the time spent on updating hover style was spent in traversal. In this CL we introduce common ancestors for dirty nodes through the StyleTraversalRoot class which is specialized for dirtiness for needing style invalidation, style recalc, and layout tree rebuild. The common ancestor is updated as part of marking ancestors child-dirty which is when we hit an ancestor which is already marked child-dirty which then becomes a candidate for being a common root. We start traversal from this common root which means we will only have to traverse ancestors (for cleaning dirty bits and other functionality we rely on being called on ancestors) and not any of their siblings. Note that in some cases we need to start at a node higher up the ancestor chain to make sure we have enough context like for WhitespaceAttacher. Local testing measuring performance using devtools of hovering section headings and links in the single page HTML spec shows that the RecalcStyle time is reduced by ~90%. Although that's an extreme case, we hope to see reduction in UMA numbers for Style.* performance for the 50th percentile. Bug: 868810 Change-Id: I1e2cea742348f35a07f89d31e8938e857d7405d8 Reviewed-on: https://chromium-review.googlesource.com/1149300 Commit-Queue: Rune Lillesveen <futhark@chromium.org> Reviewed-by:
Anders Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#591304}
 - 
Momoko Sumida authored
After discussions in https://github.com/WICG/construct-stylesheets/issues/23, we concluded that using the same constructable stylesheet in multiple Documents should not be allowed, as it can raise security risk. This CL bans the use of CSSStyleSheets in different Documents by introducing associated_document_ in CSSStyleSheet and checking if the style is applied to the same Document when it's added to AdoptedStyleSheets of any TreeScope. Link to the issue: https://github.com/WICG/construct-stylesheets/issues/23 Link to related CLs: crrev.com/c/1197002 ^ Bring back moreStyleSheets as adoptedStyleSheets crrev.com/c/1160422 ^ Implement Document.createEmptyCSSStyleSheet Bug: 807560 Change-Id: Ia0ff0af8f9baeca09b14bcbeb10897cc99b5a0bf Reviewed-on: https://chromium-review.googlesource.com/1220527 Commit-Queue: Momoko Sumida <momon@google.com> Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Reviewed-by:
Rakina Zata Amni <rakina@chromium.org> Cr-Commit-Position: refs/heads/master@{#591303}
 - 
Mike West authored
Bug: 787905 Change-Id: Icbf2459fbd8bd60f6fc016624f72ec704491897b Reviewed-on: https://chromium-review.googlesource.com/1223368Reviewed-by:
Steven Holte <holte@chromium.org> Commit-Queue: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#591302}
 - 
Kuo-Hsin Yang authored
The serving dir is also included by the page. Bug: chromium:883798 Change-Id: I1d1a512774b69312642b6226a80023ac88ff3293 Reviewed-on: https://chromium-review.googlesource.com/1226752Reviewed-by:
Ned Nguyen <nednguyen@google.com> Commit-Queue: Vovo Yang <vovoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#591301}
 - 
Daniel Bratell authored
This adds support for jumbo compilation of services/network. Jumbo is a unity build implementation where many files are compiled together in the same translation unit. That is usually much faster, and more efficient, than compiling one file at a time, but it requires the code to be compatible with such treatment. In services/network there were two problems, one duplicated function which this patch unduplicates, and the IPC/ParamTraits system which is sensitive to include header ordering. In total, on the build time reference test, this saves 7 CPU minutes (from 12 to 4), or roughly 1 minute on an 8 core machine. Cq-Include-Trybots: luci.chromium.try:linux_mojo Change-Id: I997cc61159ccf9f23eb22f3b954b888b498e3862 Reviewed-on: https://chromium-review.googlesource.com/1221946Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Daniel Bratell <bratell@opera.com> Cr-Commit-Position: refs/heads/master@{#591300}
 - 
Takashi Toyoshima authored
Currently, we show console info when a throttling happens. I expect console's feature to gather similar messages omits repeating messages. But it does not work well if users' JavaScript put own logs. This patch adds a boolean flag to omit repeating messages. The flag will be reset when SchedulingLifecycleState changes. This should not happen so frequently. Bug: 883294 Change-Id: I3e7844a7d4456fde88e198f500e21cb74c2ada64 Reviewed-on: https://chromium-review.googlesource.com/1226482Reviewed-by:
Kunihiko Sakamoto <ksakamoto@chromium.org> Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> Cr-Commit-Position: refs/heads/master@{#591299}
 - 
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://autoroll.skia.org/r/afdo-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=gbiv@chromium.org Change-Id: I86b7b1b4a6d52f080a16980860111423919ebfd9 Reviewed-on: https://chromium-review.googlesource.com/1226013 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@{#591298}
 - 
Han Leon authored
After https://chromium-review.googlesource.com/c/chromium/src/+/1214709, now we send ClaimClients Mojo message from within Blink, no longer need this WebServiceWorkerClientsClaimCallbacks to cross boundary of Content and Blink. BUG=879019 Change-Id: I755958f10b9cc3d049f89dec59eb2491bef31c1e Reviewed-on: https://chromium-review.googlesource.com/1220328 Commit-Queue: Leon Han <leon.han@intel.com> Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#591297}
 - 
Manuel Rego Casasnovas authored
These tests had issues that have been fixed in WPT so they now pass: * contain-layout-cell-001 and contain-layout-cell-002 fixed by https://github.com/web-platform-tests/wpt/pull/12926 * contain-size-025 fixed by https://github.com/web-platform-tests/wpt/pull/12960 * contain-layout-formatting-context-margin-001.html fixed by https://bugzilla.mozilla.org/show_bug.cgi?id=1490111 Change-Id: I238fd8df20a99536d65815061e10b32b0d59f21f Reviewed-on: https://chromium-review.googlesource.com/1226591 Commit-Queue: Emil A Eklund <eae@chromium.org> Reviewed-by:
Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#591296}
 - 
Marc Treib authored
Bug: none Change-Id: I5ea4c8dbc6cb3f6385fdd27ed94a5a3faf61edf2 Reviewed-on: https://chromium-review.googlesource.com/1224034Reviewed-by:
Peter Kasting <pkasting@chromium.org> Commit-Queue: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#591295}
 - 
Sam McNally authored
Bug: 826090 Tbr: tzik@chromium.org Change-Id: I987999c5a0256609bde868e891f520611d008317 Reviewed-on: https://chromium-review.googlesource.com/1220872 Commit-Queue: Sam McNally <sammc@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Reviewed-by:
Stuart Langley <slangley@chromium.org> Cr-Commit-Position: refs/heads/master@{#591294}
 
 -