GitLab

This reverts commit 951544c9.

Reason for revert: Suspected performance regression.

Original change's description:
> Separate out the four classes contained in CSSPropertyValueSet.h into four different files
>
> Bug: 752745
> Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
> Change-Id: I43c650c37c33cb92d500e5e82d437f24faf6287a
> Reviewed-on: https://chromium-review.googlesource.com/795515
> Reviewed-by: Kentaro Hara <haraken@chromium.org>
> Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
> Reviewed-by: Bugs Nash <bugsnash@chromium.org>
> Commit-Queue: meade_UTC10 <meade@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#522385}

TBR=ericwilligers@chromium.org,haraken@chromium.org,senorblanco@chromium.org,meade@chromium.org,bugsnash@chromium.org
BUG=794983,752745

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I2a5cd1bde00080ad50c963f09627dcbeab5c6ba8
Reviewed-on: https://chromium-review.googlesource.com/831372
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524633}

Using wpt-import in Chromium ba99d192.

Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/8068

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

Directory owners for changes in this CL:
drott@chromium.org, kojii@chromium.org:
  external/wpt/css/css-fonts

TBR=foolip

No-Export: true
Change-Id: Iac278f92a962d13def4e8b8c00e2fb0bf1265c8b
Reviewed-on: https://chromium-review.googlesource.com/831268
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@{#524632}

Change-Id: Ib0a76cc5919b1e4242b75180c749a13cf81346a4
Reviewed-on: https://chromium-review.googlesource.com/831371Reviewed-by: Matt Giuca <mgiuca@chromium.org>
Reviewed-by: Piotr Swigon <piotrs@chromium.org>
Commit-Queue: Piotr Swigon <piotrs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524631}

It is an effort to make changing API easier.

BUG=chromium:785956

Change-Id: If65bb11804a6ff84ea960bda4178c5a48ddae98c
Reviewed-on: https://chromium-review.googlesource.com/829813Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Roman Sorokin <rsorokin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524630}

This reverts commit fa8dfaa6.

Reason for revert:

Findit (https://goo.gl/kROfz5) identified CL at revision 524627 as the
culprit for failures in the build cycles as shown on:
https://findit-for-me.appspot.com/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtL2ZhOGRmYWE2MjFjMTcwMWRjZTg0MWY3NmVmZmVjZDA2NGZmMzc1M2UM

Sample Failed Build: https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-dbg/3252

Original change's description:
> Display mirroring persistency changes
> 
> Changes:
> 1. Change mirroring persistency rule to:
> If previous mirror mode is not set (e.g. no external display in previous
> configuration), turn on mirror mode if at least one of the external
> displays was in mirror mode before and turn off mirror mode otherwise.
> If previous mirror mode is set, mirror mode remains its previous value
> as long as there are more than 1 displays.
> For example:
> Case 1: Connect display A; Turn on mirror mode; Connect display B. B
> should be in mirror mode as well.
> Case 2: Connect display A; Turn on mirror mode; Remove A; Reconnect A; A
> should be in mirror mode.
> Case 3: Connect display A; Turn on mirror mode; Remove A; Connect
> display B. B should not be in mirror mode.
> Case 4: Connect display A; Turn on mirror mode; Connect display B;
> Remove B; Remove A; Reconnect B; B should be in mirror mode.
> 
> 2. Fix a bug in MirrorWindowController: mirroring source display may be
> changed in mirror mode (e.g. Connect two external displays; Turn on
> mirror mode; Close internal display lid; Then the internal display will
> be replaced with one external display as the mirroring source.),
> reflector and mirror windows should be updated in this case.
> 
> 3. Fix broken test.
> 
> Bug: 785416,792207
> Test: MultiMirroringTest.*
> Change-Id: Ia1da9f25df2bcc04f98ab087478a14685fff7708
> Reviewed-on: https://chromium-review.googlesource.com/804647
> Commit-Queue: Weidong Guo <weidongg@chromium.org>
> Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
> Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#524627}

Change-Id: Ie18b8dc47d031984590ed98af331fdb659b17941
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 785416,792207
Reviewed-on: https://chromium-review.googlesource.com/831290
Cr-Commit-Position: refs/heads/master@{#524629}

Constraint spaces for inline nodes also need to support block
fragmentation, due to floats.

We need to allow a (0,0) inline break token if we break before the first
line. If there's no break token for the inline layout context, it means
that we have finished all lines. Which is quite the opposite of being at
the very beginning.

There are some new test failures. One source is that we don't yet
support column-span:all, and now that we break between lines, what used
to pass by accident may no longer pass.

Making floats in an inline formatting context play along was tricky, and
I'm pretty sure that the solution I came up with needs to be improved.
For now, skip floats associated with the line when we resume layout at.
Floats that got broken inside will create break token children of the
token created for the containing block node, and will be break token
siblings of the inline break token to resume at (although they are not
siblings, node-wise).

The legacy layout write-back code doesn't work too great, especially
with LayoutNGPaintFragments enabled (but there are problems if that flag
is disabled too).

Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I01634daf75a7d80a663ec24991eec8b4094aeeda
Reviewed-on: https://chromium-review.googlesource.com/829376
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524628}

Changes:
1. Change mirroring persistency rule to:
If previous mirror mode is not set (e.g. no external display in previous
configuration), turn on mirror mode if at least one of the external
displays was in mirror mode before and turn off mirror mode otherwise.
If previous mirror mode is set, mirror mode remains its previous value
as long as there are more than 1 displays.
For example:
Case 1: Connect display A; Turn on mirror mode; Connect display B. B
should be in mirror mode as well.
Case 2: Connect display A; Turn on mirror mode; Remove A; Reconnect A; A
should be in mirror mode.
Case 3: Connect display A; Turn on mirror mode; Remove A; Connect
display B. B should not be in mirror mode.
Case 4: Connect display A; Turn on mirror mode; Connect display B;
Remove B; Remove A; Reconnect B; B should be in mirror mode.

2. Fix a bug in MirrorWindowController: mirroring source display may be
changed in mirror mode (e.g. Connect two external displays; Turn on
mirror mode; Close internal display lid; Then the internal display will
be replaced with one external display as the mirroring source.),
reflector and mirror windows should be updated in this case.

3. Fix broken test.

Bug: 785416,792207
Test: MultiMirroringTest.*
Change-Id: Ia1da9f25df2bcc04f98ab087478a14685fff7708
Reviewed-on: https://chromium-review.googlesource.com/804647
Commit-Queue: Weidong Guo <weidongg@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524627}

When the BVC presentation experiment is enabled and the last incognito tab is
closed, transition animations continue to run even after the incognito
BrowserState is destroyed.  Variables that are cleared in
|browserStateDestroyed| must be tested for nullptr before use.

BUG=787821

Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: Ic5443690337d311e1ce3e347e563d3111cc06f5e
Reviewed-on: https://chromium-review.googlesource.com/831095
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Reviewed-by: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524626}

Bug: 794273
Change-Id: I340114ad83e2dcdd5fd2b8d0dea721d0705e53b3
Reviewed-on: https://chromium-review.googlesource.com/822820Reviewed-by: Toni Barzic <tbarzic@chromium.org>
Commit-Queue: Luke Sorenson <lasoren@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524625}

Bug: 789905
Test: CrOS OOBE language menu does not have ar-001 and en-150.
Change-Id: I5f9489edf5819e789558bf53ddb4ecbb389e6a45
Reviewed-on: https://chromium-review.googlesource.com/828070Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Commit-Queue: Jungshik Shin <jshin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524624}

Following bot results are included.
2493 2495 2496 2498 2499 2500 2502 2505 2508 2511 2512 2513 2524 2526

16 lines were removed by consecutive passes since 2485.

TBR=eae@chromium.org
NOTRY=true

Bug: 591099
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I1c0ecfac97903ff168d97597290ebf7f17037de9
Reviewed-on: https://chromium-review.googlesource.com/831309
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524623}

TBR=nednguyen@chromium.org
BUG=795585

Change-Id: Idbe16201235a53ad7669478d58611708e607d5bc
Reviewed-on: https://chromium-review.googlesource.com/831508Reviewed-by: oysteine <oysteine@chromium.org>
Commit-Queue: oysteine <oysteine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524622}

We would like to sync this data in order to make sync-ed history entries
corresponding to history.replaceState() and similar Javascript events
distinguishable from user-initiated events (typed URLs or clicks on
bookmarks).

Most notably, this solves the problem of duplicates in the NTP for
server-side suggestions, which otherwise may count the URL after
replaceState() as being typed by the user and hence worth suggesting.

Design Doc (accessible to Google employees only):
https://docs.google.com/document/d/1g8w7VkLjI1V1f5N_Hkn3Lb66C3iUbV91SufFu2vEBSk/

Bug: 751023
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_site_isolation
Change-Id: I7616d5f1782c0ee9af779d2c102a29b042ce44a1
Reviewed-on: https://chromium-review.googlesource.com/738095Reviewed-by: Stefan Kuhne <skuhne@chromium.org>
Reviewed-by: Nicolas Zea <zea@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Commit-Queue: Mikel Astiz <mastiz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524621}

This patch adds support for clang-based AFDO to Chromium.

AFDO stands for Automatic Feedback Directed Optimization. In short, it
allows you to use the postprocessed output of a special `perf` command
to inform the compiler of hot/cold code, among other things.

This allows users to easily specify a profile to use, and allows for
platforms to specify default profiles. It turns none of this on on its
own.

At the moment, this is very sharp and pointy, since the sample profile
isn't a dependency for anything. Ideally, anything built with AFDO
should depend on the profile. I have a CL to make this easily possible
(CL:827560), but think this is useful enough (given care) to get in now.

(and with clang_use_default_sample_profile set to true). We built
with profiles and failed to `gn gen`, respectively. Patch seemed to be
a nop running on an otherwise "regular" build.

Bug: 794750
Test: Ran the build with and without clang_default_afdo_profile defined
Change-Id: I7b2730d52875f108681232f4d8ce7e82e7570a74
Reviewed-on: https://chromium-review.googlesource.com/828277Reviewed-by: agrieve <agrieve@chromium.org>
Commit-Queue: George Burgess <gbiv@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524620}

Adding UMA for saving and deleting pages:
- Refactored DeletePageTask for metric collection.
- Added new histogram names and made old ones obsolete.
- Updated related tests with histogram tester.

This CL also contains:
- Renamed test_util to test_utils for consistency.
- Added offline_pages::model_utils for utility methods used across all
  tasks and model itself.
- Updated OfflinePageItemGenerator for testing support

Bug: 772204
Change-Id: I894da05d510addbf01f3dd9b7ccda29b27404752
Reviewed-on: https://chromium-review.googlesource.com/811829Reviewed-by: Mark Pearson <mpearson@chromium.org>
Reviewed-by: Filip Gorski <fgorski@chromium.org>
Reviewed-by: Dmitry Titov <dimich@chromium.org>
Commit-Queue: Yafei Duan <romax@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524619}

TBR=chrome-os-gardeners@google.com

Change-Id: I118b5e3c5799130dc23cde5ee601d50b7f331631
Reviewed-on: https://chromium-review.googlesource.com/831566Reviewed-by: ChromeOS Commit Bot <chromeos-commit-bot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524618}

TBR=govind@chromium.org

Change-Id: I98fdf9497b8e9ac33ff1554c02898296e590a16c
Reviewed-on: https://chromium-review.googlesource.com/830791Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524617}

Previously VoiceInteractionControllerClient has the same life cycle as
ArcVoiceInteractionFrameworkService, which is only alive when primary
profile running and has ARC++ enabled.  This life cycle isn't a good
fit for VoiceInteractionControllerClient since it is used to update
Ash states, which has a global life time.  It caused bugs like in multi-
profile, and restricted profile, Ash UI wasn't properly rendered.

BUG=b:68664196
TEST=unit tests and locally build and manually test multi-profile

Change-Id: I8495e2c41274db385741b86d778c96e15a25b977
Reviewed-on: https://chromium-review.googlesource.com/827540
Commit-Queue: Xiaohui Chen <xiaohuic@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524616}

This change adds a class which shows a Presentation API receiver page in
a popup-style window that is started fullscreen on a specific wired
display.

It also changes the handling of one-off OTR profiles used by
presentations, which affects this class and offscreen tabs.  Previously,
offscreen tabs assumed ownership of their OTR profiles.  However, it was
possible for this to be violated by opening a DevTools window and
Browser would think that it could destroy the profile.  Additionally,
there was no handling of the original profile being destroyed, which
would leave dangling references in the OTR profile.  This has been
addressed by adding an IndependentOTRProfileManager class, which helps
both offscreen tabs and PresentationReceiverWindow manage the lifetime
of these one-off OTR profiles.

Bug: 777654, 786158, 664351, 727487
Change-Id: I64d032419d341affbdde4ee80b57d45c99648588
Reviewed-on: https://chromium-review.googlesource.com/742122
Commit-Queue: Brandon Tolsch <btolsch@chromium.org>
Reviewed-by: mark a. foltz <mfoltz@chromium.org>
Reviewed-by: Derek Cheng <imcheng@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Yuri Wiitala <miu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524615}

Bug: none
Change-Id: I4bce34a6169cf655a02129f5ff0a265a3f6b89a3
Reviewed-on: https://chromium-review.googlesource.com/831060Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524614}

This reverts commit 86c790e6.

Reason for revert: This is causing performance / memory regressions that are trickier to address than expected. Reverting this for now.

Original change's description:
> Remove use of DeferredTextureImageData APIs and Support Decode to Scale
> 
> We aren't benefitting from the complexity added by the
> DeferredTextureImageData APIs, and this API blocks us from using
> PaintImage::Decode's decode-to-scale functionality.
> 
> This change removes our usage of DeferredTextureImageData APIs,
> instead using SkImage::makeTextureImage to handle upload. Additionally,
> we now use the PaintImage::Decode API, adding decode-to-scale support.
> 
> Bug: 773799
> Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel
> Change-Id: Ia5f480213c3a5c8225ccd289aa2c081056840f94
> Reviewed-on: https://chromium-review.googlesource.com/713593
> Reviewed-by: vmpstr <vmpstr@chromium.org>
> Commit-Queue: Eric Karl <ericrk@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#517206}

TBR=vmpstr@chromium.org,ericrk@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 773799
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: Ie4493559e334100f03dfed1dfb7a408fc26a33e0
Reviewed-on: https://chromium-review.googlesource.com/830587
Commit-Queue: Eric Karl <ericrk@chromium.org>
Reviewed-by: Eric Karl <ericrk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524613}

Now that we have compression enabled, system tracing doesn't cause
flakes due to filling up /tmp, and we should be able to safely turn
it on by default.

Also increase the websocket timeout, since very large traces might take
more than 10s to compress.

BUG=786091
TEST=trace.py

Change-Id: I65726a723eb4b28466f4bff0dd818db916165227
Reviewed-on: https://chromium-review.googlesource.com/830916Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Commit-Queue: Michael Spang <spang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524612}

TBR=zea@chromium.org

Change-Id: I84aa98d03d40cb98f7f43788389e6aa9a9607249
Reviewed-on: https://chromium-review.googlesource.com/831250Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524611}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/99da619f6cdc..454acc12ef55

$ git log 99da619f6..454acc12e --date=short --no-merges --format='%ad %ae %s'
2017-12-15 iannucci [vpython] Bump depot_tools version of vpython.

Created with:
  roll-dep src/third_party/depot_tools


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=phajdan.jr@chromium.org

Change-Id: I5273810e26fe3a0728b9decfa0e73ab3f2403b56
Reviewed-on: https://chromium-review.googlesource.com/830518Reviewed-by: depot-tools-roller . <depot-tools-roller@chromium.org>
Commit-Queue: depot-tools-roller . <depot-tools-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524610}

This CL is part of VectorMath code clean up series:
[1/4] https://chromium-review.googlesource.com/c/824046
[2/4] https://chromium-review.googlesource.com/c/824047
[3/4] this CL
[4/4] https://chromium-review.googlesource.com/c/824049

Bug: 778262
Change-Id: I26f4e6cf672e2739e93cbf2a52dc44d776deec70
Reviewed-on: https://chromium-review.googlesource.com/824048Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Raymond Toy <rtoy@chromium.org>
Commit-Queue: Eero Häkkinen <eero.hakkinen@intel.com>
Cr-Commit-Position: refs/heads/master@{#524609}

This changes the gclient hook to run only conditionally on
linux, which keeps it from running and printing stuff on
the other platforms.

R=jbudorick@chromium.org

Change-Id: Id1dbfb50f139308b3c39875e00294ea9a0a76016
Reviewed-on: https://chromium-review.googlesource.com/831219Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524608}

This CL is part of VectorMath code clean up series:
[1/4] https://chromium-review.googlesource.com/c/824046
[2/4] this CL
[3/4] https://chromium-review.googlesource.com/c/824048
[4/4] https://chromium-review.googlesource.com/c/824049

Bug: 778262
Change-Id: If74c8bc5761b73a4282de20ae4c72e6ad839e464
Reviewed-on: https://chromium-review.googlesource.com/824047Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Raymond Toy <rtoy@chromium.org>
Commit-Queue: Eero Häkkinen <eero.hakkinen@intel.com>
Cr-Commit-Position: refs/heads/master@{#524607}

https://skia.googlesource.com/skia.git/+log/594706566a62..ef0384835757

$ git log 594706566..ef0384835 --date=short --no-merges --format='%ad %ae %s'
2017-12-16 reed remove deprecated SkPixelSerializer

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=liyuqian@chromium.org

Change-Id: Ic32ec8ddd05a47ae5eeb0c1725a654f60dcf1acc
Reviewed-on: https://chromium-review.googlesource.com/831467Reviewed-by: Skia Deps Roller <skia-deps-roller@chromium.org>
Commit-Queue: Skia Deps Roller <skia-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524606}

https://skia.googlesource.com/skia.git/+log/dd821bc56488..594706566a62

$ git log dd821bc56..594706566 --date=short --no-merges --format='%ad %ae %s'
2017-12-16 reed remove dead SK_SUPPORT_LEGACY_IMAGEDESERIALIZER code

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=liyuqian@chromium.org

Change-Id: Ica74a7dd036510eeb431ce38ed498156d2039b23
Reviewed-on: https://chromium-review.googlesource.com/831351Reviewed-by: Skia Deps Roller <skia-deps-roller@chromium.org>
Commit-Queue: Skia Deps Roller <skia-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524605}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/7be4ef7e..62729327

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: Ia7c0b1871759681d9ec6b362c1ebc6941a3be89f
Reviewed-on: https://chromium-review.googlesource.com/830932Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524604}

Dereferencing a null extension(), change it to use extension_id_safe()

bug: chromium:795399
Change-Id: If072049509dca199707c48ff374c6a296b45625a
Reviewed-on: https://chromium-review.googlesource.com/831186Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: Ivan Šandrk <isandrk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524603}

Record the time elapsed since last time there is no partner
bookmark. This will help tune the banning duration and skipping
rate.

Bug: 787132
Change-Id: I70864105f19a315674b4f525ecc7cfe3905b01c9
Reviewed-on: https://chromium-review.googlesource.com/826365Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524602}

Record time spent on reading partner bookmarks, since this is part of
the critical path of showing bookmark UI.

Bug: 787132
Change-Id: I8aa68436b0d762d644691992bde0e2df095259f0
Reviewed-on: https://chromium-review.googlesource.com/825004Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524601}

https://pdfium.googlesource.com/pdfium.git/+log/175f01bb081b..682118834b3c

$ git log 175f01bb0..682118834 --date=short --no-merges --format='%ad %ae %s'
2017-12-16 thestig Fix null-dereference in CPDF_ShadingPattern::Load().

Created with:
  roll-dep src/third_party/pdfiumBUG=795490


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: I6ddeaa08056edde34d2469221124f90d704dec0f
Reviewed-on: https://chromium-review.googlesource.com/831116
Reviewed-by: <pdfium-deps-roller@chromium.org>
Commit-Queue: <pdfium-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524600}

TBR=chrome-os-gardeners@google.com

Change-Id: I3fd9414ddcfd6910226f841e998837028a8ff573
Reviewed-on: https://chromium-review.googlesource.com/831076Reviewed-by: ChromeOS Commit Bot <chromeos-commit-bot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524599}

Only 6 new events that ChromeVox actually uses are migrated by this
change. I added comments to the other events to keep track of which
ones are candidates for migration or for removal in the future.

Bug: 699438, 788893
Change-Id: Ica13cd36369770242a20954c020e80f0f1fbff63
Reviewed-on: https://chromium-review.googlesource.com/820353
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524598}

Expose renderer hit test API to the browser
with a mojo interface. With this API browser
can ask a renderer about the target frame
of a given point. The API returns the sink id
of the target frame. The result frame could be
either a remote or local frame from the
renderer's point of view.

Bug: 732405
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_site_isolation
Change-Id: I2606dbeb71eb0cc7d593c80eb73cbcb24d2774ad
Reviewed-on: https://chromium-review.googlesource.com/751721Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: Navid Zolghadr <nzolghadr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524597}

http://crrev.com/524139 moved WatchTimeRecorderProvider and
VideoDecodeStatsRecorder into MediaMetricsProvider, but forgot
to update the manifest.

BUG=779192
TEST=no more connection errors

Change-Id: I5cc2c4401545979b788dd028fee9a76c8584edbd
Reviewed-on: https://chromium-review.googlesource.com/831220
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524596}

BUG=521776

Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I166b8e48a70cfbbc37f72490b4bcedc383653123
Reviewed-on: https://chromium-review.googlesource.com/674751
Commit-Queue: Lei Zhang <thestig@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524595}

https://chromium.googlesource.com/catapult.git/+log/cb66d9d95233..ad4583d06ecd

$ git log cb66d9d95..ad4583d06 --date=short --no-merges --format='%ad %ae %s'
2017-12-15 dtu [pinpoint] Defer Commit creation when resolving DEPS.

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: Ia7b193f41ca6a1894ee6541d2e19013ea330b5e1
Reviewed-on: https://chromium-review.googlesource.com/831388
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524594}