GitLab

BUG=762641
TBR=oshima@chromium.org

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

TBRing trivial call site update in avatar_button_error_controller.cc
TBR=msarda

Bug: 839834
Change-Id: I3f01a7fd80d4699101e6d7002e85b9829d0aa881
Reviewed-on: https://chromium-review.googlesource.com/1057672
Commit-Queue: Marc Treib <treib@chromium.org>
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558635}

To merge common processes into one place, this CL make CodeGeneratorV8
inheritances to use CodeGeneratorBase.render_templates(), which was
renamed from render_template().
This CL also make normalize_and_sort_includes() to use set() type
to avoid include duplicates.


Bug: 830255
Change-Id: I7e723153930ae55cab04d5a5fdb38b51c3494434
Reviewed-on: https://chromium-review.googlesource.com/1058743Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Commit-Queue: Hitoshi Yoshida <peria@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558634}

https://pdfium.googlesource.com/pdfium.git/+log/08d96f1cadb1..473b4ae489e8

$ git log 08d96f1ca..473b4ae48 --date=short --no-merges --format='%ad %ae %s'
2018-05-15 thestig Lower the limit of image dimensions for fax codecs.
2018-05-15 thestig Read data in bigger chunks in fax codec code.
2018-05-15 thestig Clean up CBC_ASCIIEncoder.
2018-05-15 thestig Return earlier in CPDF_TextPage::ProcessInsertObject() when possible.

Created with:
  roll-dep src/third_party/pdfium
BUG=chromium:834633,chromium:834633


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: I67c2cecc2867cf1ea9506e502702c67a3b1f5843
Reviewed-on: https://chromium-review.googlesource.com/1058927Reviewed-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@{#558633}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/7e9e7b065a98..c8e4e795ed75

$ git log 7e9e7b065..c8e4e795e --date=short --no-merges --format='%ad %ae %s'
2018-05-14 bpastene Revert "[chromite] Capture job_name and git timing for ts_mon in cbuildbot runs."

Created with:
  roll-dep src/third_party/chromite
BUG=chromium:829289


The AutoRoll server is located here: https://chromite-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=chrome-os-gardeners@chromium.org

Change-Id: Ifcc9ffe22c45cf58facf0522b1e9604c3638b9b9
Reviewed-on: https://chromium-review.googlesource.com/1058980Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#558632}

Using wpt-import in Chromium 60f2c3c7.

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

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:
yhirano@chromium.org, mkwst@chromium.org, japhet@chromium.org:
  external/wpt/fetch

TBR=markdittmer

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

They have been reordered to match the header file.

Bug: None
Change-Id: Ia3ff219d28c4b99d88235447672168cdc4f4cde8
Reviewed-on: https://chromium-review.googlesource.com/1056900Reviewed-by: Timothy Loh <timloh@chromium.org>
Commit-Queue: Ben Wells <benwells@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558630}

Now we have no Blink-relative #includes.

Bug: 836071
Change-Id: I33bbab6340def20dcd07a72fcc5d1a4d08254a1b
Reviewed-on: https://chromium-review.googlesource.com/1058876Reviewed-by: Hitoshi Yoshida <peria@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558629}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/eb85cead4784..3136ebfa0a62

$ git log eb85cead4..3136ebfa0 --date=short --no-merges --format='%ad %ae %s'

Created with:
  roll-dep src-internal
BUG=chromium:819426,chromium:807366


The AutoRoll server is located here: https://src-internal-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=mmoss@chromium.org

Change-Id: I494cef0cc7c8557a2d3b99c72af41bc4efd7b0c4
Reviewed-on: https://chromium-review.googlesource.com/1058720Reviewed-by: src-internal-chromium-autoroll <src-internal-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: src-internal-chromium-autoroll <src-internal-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#558628}

Crostini multiprofile support is going to wait until the successor for
multiprofile is landed on ChromeOS. Until then, we restrict Crostini to the
primary (i.e. first signed in) profile per session. This means that you can
still have Linux containers per profile, but to use then you need to sign out
then sign in to the desired profile.

Note, this prevents UI from being shown to the non-primary profile. It doesn't
prevent non-primary users from using crosh and vmc.

Bug: 842561
Change-Id: I119359b332e7a3afa02071c1e9d9e6f41164fe4d
Reviewed-on: https://chromium-review.googlesource.com/1058738
Commit-Queue: Nicholas Verne <nverne@chromium.org>
Reviewed-by: Timothy Loh <timloh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558627}

TBR=rdevlin.cronin@chromium.org

Bug: 833655
Change-Id: Iace4691833cde898e1545601fee1444139ae717a
Reviewed-on: https://chromium-review.googlesource.com/1058878Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558626}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/493cfb68..558cf7d7

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,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org

Change-Id: Ic22cf44bc99d3d48b3e4b1493e372d80495d4902
Reviewed-on: https://chromium-review.googlesource.com/1058908Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558625}

While going over the code I found an old TODO indicating I should
replace a `CHECK` with a `DCHECK` if no crash report would come in.
Since the `CHECK` landed 17 months ago, I think it's now safe to replace
it.

Change-Id: Ic133f6a8ecdb654120a5ae4fb34f6f990ff34ca4
Reviewed-on: https://chromium-review.googlesource.com/1058788Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Commit-Queue: Yoav Weiss <yoav@yoav.ws>
Cr-Commit-Position: refs/heads/master@{#558624}

Bug: 790520
Change-Id: I86c5a81b8b5872a2397621cb631a9b820eb28d8d
Reviewed-on: https://chromium-review.googlesource.com/1056228
Commit-Queue: Zhiling Huang <hzl@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558623}

This reverts commit 640eb0c2.

Reason for revert: Broke the build.

https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-dbg/5678

Original change's description:
> media: implement TakePhoto in Chrome OS camera HAL VideoCaptureDevice
> 
> This CL implements the TakePhoto() API for the Chrome OS camera HAL
> VideoCaptureDevice, including the following features:
> 
>   - Full size still capture
>   - Auto-focus, auto-exposure, and auto-white-balancing stabilization
> 
> BUG=chromium:832772
> TEST=Run capture_unittests on DUT
> TEST=Make sure TakePhoto() API works on
> https://googlechrome.github.io/samples/image-capture/grab-frame-take-photo.html
> 
> Change-Id: I99e44087006cac28eac7e73c6764f522dac57cfa
> Reviewed-on: https://chromium-review.googlesource.com/1018641
> Reviewed-by: Emircan Uysaler <emircan@chromium.org>
> Reviewed-by: Wu-Cheng Li <wuchengli@chromium.org>
> Commit-Queue: Ricky Liang <jcliang@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#558603}

TBR=jcliang@chromium.org,wuchengli@chromium.org,emircan@chromium.org,shenghao@google.com,hywu@chromium.org,chfremer@chromium.org

Change-Id: Ibc2b4547f33d4a505b546079dd118e1d4401a9cf
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: chromium:832772
Reviewed-on: https://chromium-review.googlesource.com/1058568Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558622}

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://afdo-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=gbiv@chromium.org

Change-Id: Ifc78d42372052bb8b6261021d2d39bf9588c1a4a
Reviewed-on: https://chromium-review.googlesource.com/1058846Reviewed-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@{#558621}

This CL creates a new cr-radio-button element with the MD-refresh spec.
This CL also replaces all paper-radio-button within Settings with
cr-radio-button.

Most of the cr-radio-button's functionalities and styles are encapsulated
in separate files in a shared location, so that the controlled-radio-button
element in settings can reuse them.

There will be a follow-up CL to then replace all of paper-radio-button's
usage outside of Settings.

Bug: 840527
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I4fc47fa0b8186b5d6ef0a3b678cc68bbc58a8e3d
Reviewed-on: https://chromium-review.googlesource.com/1053299
Commit-Queue: Scott Chen <scottchen@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558620}

Broadcast is currently implemented as a cast URL with a special
broadcast query parameter. When this URL is received, it is treated as
a request to broadcast a message to all cast devices instead of a
regular sink query.

Bug: 698940
Change-Id: I25cfa6f84c2957f4fb63ec75b7a30007bfe47850
Reviewed-on: https://chromium-review.googlesource.com/944902Reviewed-by: Brandon Tolsch <btolsch@chromium.org>
Commit-Queue: Derek Cheng <imcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558619}

https://chromium.googlesource.com/angle/angle.git/+log/5730c0bf431e..a00ef3144f70

$ git log 5730c0bf4..a00ef3144 --date=short --no-merges --format='%ad %ae %s'
2018-05-14 geofflang Add more dEQP EGL expectations for Linux and Android.

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=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=ynovikov@chromium.org

Change-Id: I0387e6d674f7447b2cc164df32ab60cb1ca50f8e
Reviewed-on: https://chromium-review.googlesource.com/1058678Reviewed-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@{#558618}

When the network service is disabled, we are using the same request ID
for the preflight request and the actual request as we cannot assign
separate IDs. We need to tear down the preflight request first, and
then make the actual request: Otherwise we will see a renderer crash
caused by RDH_INVALID_REQUEST_ID.

Currently we cancel the request by resetting the SimpleURLLoader for
the preflight request: That is not enough because destroying a
SimpleURLLoader asynchronously cancels a request, and we don't know
when it's actually destroyed. This is especially problematic when
a server returns a preflight with a long body.

This CL fixes the problem by adding a function which cancels the
request synchronously. This is a workaround, and we won't need the
logic in the end.


Bug: 838136, 614281, 842593
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Ic9d20cfbecc7c5b8749e0dc664d12c6d07e8c673
Reviewed-on: https://chromium-review.googlesource.com/1056941
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558617}

TBR: 
Change-Id: I1b488783f04a3bcc20b82feddb079e3f0519d2cb
Reviewed-on: https://chromium-review.googlesource.com/1058931Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Commit-Queue: Pavel Feldman <pfeldman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558616}

This patch adds a new attribute to the InputContext object in the IME
API called 'shouldDoLearning'. Textfields in incognito tabs will return
false for shouldDoLearning so that the IME can keep incognito and
non-incognito profiles separate.

To implement this, we add a new TextInputClient::ShouldDoLearning()
method that is implemented by various types of text fields. The most
interesting case is views::Textfield, which doesn't have any notion
of incognito, so it should be up to owner of the textfield to decide
if it's incognito or not. However, there are ~90 places where we
construct a views::Textfield, so to prevent this CL getting too large,
we default to 'false' for ShouldDoLearning and then we'll add support
for learning on all the different textfields as needed.

Bug: 311180
Change-Id: Id33b11505a2eb3154fed8c4747c05205c7bf7c77
Reviewed-on: https://chromium-review.googlesource.com/1049405Reviewed-by: Yusuke Sato <yusukes@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Shu Chen <shuchen@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558615}

This patch implements painting selection line break.
Design doc: https://goo.gl/ovMr8x

This patch changes LayoutSelection::SelectionStartEndForNG(
text_fragment) to return LayoutSelectionStatus which has
selection |start|,|end| and new boolean member |has_line_break|,
which means we need expand selection rect of the fragment to
paint line break.

The caller NGTextFragmentPainter paints line break selection by
extending existing selection rect when selection wraps line.

This patch fixes 4 selection painting test.

Bug: 708452
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_layout_ng;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Idef2d7135a5d7f27a217365cc3e8d55b191fa60b
Reviewed-on: https://chromium-review.googlesource.com/896780Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Yoichi Osato <yoichio@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558614}

Fix some lint errors as well.

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I3dc89035a5bf2cd6b092512d0aa6eb2022704792
Reviewed-on: https://chromium-review.googlesource.com/1039150Reviewed-by: David Reveman <reveman@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Reviewed-by: Alice Boxhall <aboxhall@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558613}

When computing caret rect for a caret position before/after an atomic inline
box, whether the caret rect is to the left or right of the box depends on the
resolved direction of the atomic inline, not the CSS 'direction' property.

This patch changes the implementation to check the resolved direction.

Bug: 822575
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: Ibc09e6679faf94ad7882bfba7560d44fd36fd7d8
Reviewed-on: https://chromium-review.googlesource.com/1056395Reviewed-by: Emil A Eklund <eae@chromium.org>
Reviewed-by: Yoichi Osato <yoichio@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558612}

bindings: Qualify #includes in generated V8GeneratedCoreBindings.cpp, initPartialInterfacesInModules.cpp, and V8ContextSnapshotExternalReferences.cpp.

Bug: 830255
Change-Id: I8c833ac805de7e378e5983f204022f7fdc72794e
Reviewed-on: https://chromium-review.googlesource.com/1058870Reviewed-by: Hitoshi Yoshida <peria@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558611}

Certificate Transparency is now required by policy for all new
certificates issued after April 2018 - that is, on or after
2018-05-01 00:00:00 UTC, as measured by the certificate's notBefore.

In order to ensure compliance to this policy, actually enforce it
in code.

This restructures the CTPolicyManager, which originally was a
pimpl'd bridge between the UI and IO threads, into the
ChromeRequireCTDelegate, now that it's solely single threaded and
has a defined interaction. To maintain existing behaviour, one can
enable CT policies without enforcing the April 2018 requirement, or
can enable new cert enforcement as well.

BUG=838680

Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: I939bc2ee6fde58f877a669278c92678153f61fdc
Reviewed-on: https://chromium-review.googlesource.com/1054947
Commit-Queue: Ryan Sleevi <rsleevi@chromium.org>
Reviewed-by: Eran Messeri <eranm@chromium.org>
Reviewed-by: Mustafa Emre Acer <meacer@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558610}

Adding http_rtt_observation in ReadCachedNetworkQualityEstimate
causes notifying observers.
That can lead to calling ReadCachedNetworkQualityEstimate again.
So some observations can be added between adding
http_rtt_observation and adding transport_rtt_observation.
That ends up to breaking observations timestamp increasing.
To fix this we can use new timestamp each time when add
observation.
Same logic is used in AddDefaultEstimates for example.

R=ryansturm@chromium.org, tbansal@chromium.org

Bug: 841681
Change-Id: Ibed7d5e8e3efca82915d37b1de58df50ae43ff58
Reviewed-on: https://chromium-review.googlesource.com/1052690Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558609}

Remove old platform-specific desktop Java test filters for failusres
that no longer repro.

TBR=kereliuk@chromium.org

Change-Id: Ic0ccb93f6bd03bc200b54452f1fb11d8c5c5d057
Reviewed-on: https://chromium-review.googlesource.com/1058842Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558608}

This is a preparation of launching incremental shadow dom.

After I confirm that this doesn't cause any regression in bots,
I'll ship this, announcing it to blink-dev briefly, in a few days.

Bug: 776656
Change-Id: I2632a42c2cb9acaf6462600ac236dc9b8bff32ed
Reviewed-on: https://chromium-review.googlesource.com/1056896
Commit-Queue: Hayato Ito <hayato@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558607}

Using wpt-import in Chromium a7f5d9df.

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

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:
bjonesbe@adobe.com:
  external/wpt/css/css-shapes
cvazac@akamai.com, igrigorik@chromium.org:
  external/wpt/server-timing
drott@chromium.org, kojii@chromium.org:
  external/wpt/css/css-fonts
ericwilligers@chromium.org:
  external/wpt/css/motion
rego@igalia.com:
  external/wpt/css/css-ui

TBR=markdittmer

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

- Interface change has happend at https://crrev.com/c/844052 around the
  end of February. It should be fine to remove backward compat code now.

Bug: 768439
Test: unit_tests:ArcAccessibilityHelperBridgeTest
Change-Id: Ibac321f3889d605393928839b5292e64d27b0094
Reviewed-on: https://chromium-review.googlesource.com/1039405Reviewed-by: Evan Stade <estade@chromium.org>
Reviewed-by: David Tseng <dtseng@chromium.org>
Commit-Queue: Yuki Awano <yawano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558605}

SignedExchangeHandler parses the content-type header to determine the
version of signed exchange (currently it accepts only version b0), and
passes the version enum to other classes that need versioned code.

Bug: 803774
Change-Id: I90fe2c94d4a5dec61000650338ff4cd0461d2c7d
Reviewed-on: https://chromium-review.googlesource.com/1056940Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558604}

This CL implements the TakePhoto() API for the Chrome OS camera HAL
VideoCaptureDevice, including the following features:

  - Full size still capture
  - Auto-focus, auto-exposure, and auto-white-balancing stabilization

BUG=chromium:832772
TEST=Run capture_unittests on DUT
TEST=Make sure TakePhoto() API works on
https://googlechrome.github.io/samples/image-capture/grab-frame-take-photo.html

Change-Id: I99e44087006cac28eac7e73c6764f522dac57cfa
Reviewed-on: https://chromium-review.googlesource.com/1018641Reviewed-by: Emircan Uysaler <emircan@chromium.org>
Reviewed-by: Wu-Cheng Li <wuchengli@chromium.org>
Commit-Queue: Ricky Liang <jcliang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558603}

Bug: 832374
Change-Id: I13d52c97809ec4da1e2f2987d0b76c9d9be91810
Reviewed-on: https://chromium-review.googlesource.com/1058507Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558602}

R=zmo

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: I44688d6daa071b9ab61d5aa79b0e3a75fd726f27
Reviewed-on: https://chromium-review.googlesource.com/1058434Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558601}

https://chromium.googlesource.com/catapult.git/+log/dd13313c34d3..075ca3000abf

$ git log dd13313c3..075ca3000 --date=short --no-merges --format='%ad %ae %s'
2018-05-14 kendaljharland Support fuchsia project revisions in tooltips.
2018-05-14 szager Rename browser_simpleperf_controller to browser_interval_profiling_controller.

Created with:
  roll-dep src/third_party/catapult
BUG=chromium:839645


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.


TBR=sullivan@chromium.org

Change-Id: If1d98d42fab9b95555eb658fcda29abf3740a075
Reviewed-on: https://chromium-review.googlesource.com/1058683
Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#558600}

This CL rounds the corners of Rich images with a roundRect clip path.

Bug: 842399
Change-Id: I057d9cabcc46a71efc64145e6b90041e6d1067be
Reviewed-on: https://chromium-review.googlesource.com/1056397Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Commit-Queue: Dave Schuyler <dschuyler@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558599}

# This is an automated release commit.
# Do not revert without consulting chrome-pmo@google.com.
NOAUTOREVERT=true
TBR=mmoss@chromium.org

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

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/d527ddce..493cfb68

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,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org

Change-Id: Ib60a019cbc2ed0942d7d9805b9e08c70aca0876e
Reviewed-on: https://chromium-review.googlesource.com/1058627Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558597}