GitLab

We're (unintentionally?) triggering linear sRGB 8888 drawing
here by copying the color space directly off the source image
for our resized surfaces.

That we don't notice this is a testament to the perfect
round tripping of our from_srgb and to_srgb conversion functions.

I'm trying to land https://skia-review.googlesource.com/c/skia/+/132261
to intentionally break linearly blended sRGB 8888, to flush out
accidental uses just like this one.  With that CL applied, our drawing
pipeline for linear-blended sRGB 8888 is intentionally _very_ broken,
and will do broken things like linearize sources but not linearize the
destination or re-encode the result of the blend.

We caught this with layout tests,
https://test-results.appspot.com/data/layout_results/linux_trusty_blink_rel/30657/layout-test-results/results.html

Change-Id: I5814c43d861deab8a2720790fb826ed2f0a9b2bf
Reviewed-on: https://chromium-review.googlesource.com/1089135Reviewed-by: Mohammad Reza Zakerinasab <zakerinasab@chromium.org>
Commit-Queue: Mike Klein <mtklein@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564994}

The original implementation needs readback from the FBO, it doesn't work
with SkDDL, because the FBO will not have the content until the recorded
SkDDL is played back on the Gpu thread. This CL uses SkCanvas::saveLayer()
to implement the backdrop effect. It doesn't need read the FBO.


Test: Passed layeout tests css3/filters/*.html with and without SkDDL
Bug: 822857
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: I213fdff5f73c13af34a0295c666b80353642de96
Reviewed-on: https://chromium-review.googlesource.com/1073664
Commit-Queue: Peng Huang <penghuang@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564993}

Since Refresh removes the avatar button in the frame area, the test is
no longer needed.

Bug: 846410
Change-Id: I58d40e94aa4e4f909ebec0674c923a0a9a7f0f82
Reviewed-on: https://chromium-review.googlesource.com/1087435Reviewed-by: Allen Bauer <kylixrd@chromium.org>
Commit-Queue: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564992}

Bug: 848861
Change-Id: I9e34aeca5ba01199f276a4d6fec76183eda0d40a
Reviewed-on: https://chromium-review.googlesource.com/1082432
Commit-Queue: Will Harris <wfh@chromium.org>
Reviewed-by: Will Harris <wfh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564991}

https://pdfium.googlesource.com/pdfium.git/+log/8ae3209..ce4b14e


git log 8ae3209..ce4b14e --date=short --no-merges --format='%ad %ae %s'
2018-06-06 art-snake@yandex-team.ru Simplify check info availability.


Created with:
  gclient setdep -r src/third_party/pdfium@ce4b14e

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: I35f52886eab5910de9d3cdbca3b4aa89a46bdc30
Reviewed-on: https://chromium-review.googlesource.com/1089171Reviewed-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@{#564990}

In gen_fuzzer_owners.py, GetSourcesFromDeps() receives a list of
dependencies based on the fuzzer_tests in the GN build configuration.
Existing configurations are fairly simple, with source_sets as direct
dependencies. Introducing a GN group into a fuzzer_test will break
gen_fuzzer_owners.py.

This CL augments GetSourcesFromDeps() to look through the list of
dependencies for groups and replace the groups with their direct
dependencies. Since groups can depend on other groups, traverse the
dependencies graph until all groups have been replaced.

Change-Id: Ib0e15a18c7916af6790f41b1c752ab18bda970d9
Reviewed-on: https://chromium-review.googlesource.com/1077071Reviewed-by: Max Moroz <mmoroz@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564989}

Bug: 850080
Change-Id: Iec8fdc70bb943fa153a4ffbacadda9ea3478370e
Reviewed-on: https://chromium-review.googlesource.com/1088755Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Commit-Queue: Fabio Tirelo <ftirelo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564988}

It's failing consistently on the Network Service bot, probably due to DCHECK.

Sample Build:
https://ci.chromium.org/buildbot/chromium.fyi/Mojo%20Linux/14273

TBR=falken@chromium.org,horo@chromium.org

Bug: 849670, 789111
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: I3d9da983aa3ba2006a75c27639da8e6fe716875c
Reviewed-on: https://chromium-review.googlesource.com/1089356
Commit-Queue: Chong Zhang <chongz@chromium.org>
Reviewed-by: Chong Zhang <chongz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564987}

This reverts commit 4da4d1e4.

Reason for revert: linkage failures:
bin/ld.lld: error: undefined symbol: NotificationUIManager::Create()
>>> referenced by browser_process_impl.cc:1198 (../../chrome/browser/browser_process_impl.cc:1198)
>>>               browser/browser_process_impl.o:(BrowserProcessImpl::CreateNotificationUIManager()) in archive obj/chrome/browser/libbrowser.a
clang: error: linker command failed with exit code 1 (use -v to see invocation)
ninja: build stopped: subcommand failed.

Original change's description:
> Chrome OS: remove non-native notifications codepaths.
> 
> Only support native notifications, i.e. those passed over mojo.
> 
> Some tests are permanently removed on Chrome OS. Some tests are
> migrated to message_center_unittests.
> 
> Bug: 578868
> Change-Id: Ibd4edcd1968c94af2d24b15ed3c1329ea7bf49b1
> Reviewed-on: https://chromium-review.googlesource.com/1083937
> Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
> Reviewed-by: Scott Violet <sky@chromium.org>
> Commit-Queue: Evan Stade <estade@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#564928}

TBR=stevenjb@chromium.org,sky@chromium.org,estade@chromium.org

Change-Id: I91f175ba1d9d23545c4377c8c131d6c0170431db
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 578868
Reviewed-on: https://chromium-review.googlesource.com/1089471Reviewed-by: Evan Stade <estade@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564986}

Change-Id: Ib56a9240c13723d5a4a2f3bb3a5ca16e6d1acaa6
Reviewed-on: https://chromium-review.googlesource.com/1087670
Commit-Queue: Cathy Li <chili@chromium.org>
Reviewed-by: Dmitry Titov <dimich@chromium.org>
Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564985}

On hosts that support both IPv4 and IPv6, ChromeDriver now listens on
both protocols.

Bug: chromedriver:779
Change-Id: I4a115cc0ca5cf0396acdad8d4c1a72f169120368
Reviewed-on: https://chromium-review.googlesource.com/1080448Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564984}

This CL converts the Night Light command-line switch
to a feature and makes it enabled by default

BUG=705611,749250

Change-Id: Ie7dcfbf5539c212b964b8824c99aae44a425548e
Reviewed-on: https://chromium-review.googlesource.com/1088132
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564983}

Bug: 715355
Change-Id: Id2a1d0fc88d510395ee8c20acca55571638f4fa5
Reviewed-on: https://chromium-review.googlesource.com/1084138
Commit-Queue: Stuart Langley <slangley@chromium.org>
Reviewed-by: Sasha Morrissey <sashab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564982}

This change updates the existing web platform tests for WebUSB to use
multi-global tests to test the API in the supported contexts. The
change updates the following tests:
* idlharness
* usb
* usbConnectionEvent

Bug: 841510
Change-Id: I6b118aa4121109cd6a48054c2ebc69b831660afc
Reviewed-on: https://chromium-review.googlesource.com/1087209Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Ovidio Henriquez <odejesush@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564981}

Bug: 845576
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I013e873ac05616d6470282e71767f30eb1eee0ea
Reviewed-on: https://chromium-review.googlesource.com/1083625
Commit-Queue: Esmael El-Moslimany <aee@chromium.org>
Reviewed-by: Scott Chen <scottchen@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564980}

Specifically when passing in targets manually. The `--all` flag (on by
default) already takes care of this case.

Bug: 620034
Change-Id: Ie5c679c6cf9b75e36415d2868f7fff46e9e81ad1
Reviewed-on: https://chromium-review.googlesource.com/1089121
Commit-Queue: Peter Wen <wnwen@chromium.org>
Commit-Queue: Eric Stevenson <estevenson@chromium.org>
Reviewed-by: Eric Stevenson <estevenson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564979}

Preparation for fixing the DSF that is used for querying render style
for strike, see crbug.com/849877.

If one renderer maintains multiple views, we need to inform the font
cache about this view's DSF before performing layout. This is because
FontPlatformData on Linux / CrOS needs the DSF for querying the
RenderStyle for fonts in this view correctly from out of process.

Prepare the FontCache for including the DSF in GetFontplatformData
queries.

Bug: 845468
Change-Id: Ib3de63dcdb18261502837905a04e563a30bcb42e
Reviewed-on: https://chromium-review.googlesource.com/1087908Reviewed-by: Becca Hughes <beccahughes@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564978}

Change-Id: I7f467623d5476f717d73aeeaecdc69399c6b65f5
Reviewed-on: https://chromium-review.googlesource.com/1074584
Commit-Queue: Alice Boxhall <aboxhall@chromium.org>
Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564977}

Leave the flag in place so we can revert the state in case we have any blockers.

R=escordeiro@chromium.org, xiyuan@chromium.org

Bug: 848827
Change-Id: I448a6e695b9e01ba232ee832e239074a0bd397b6
Reviewed-on: https://chromium-review.googlesource.com/1089134Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: B. Menegola <menegola@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564976}

Adds lots of comments explaining how to hold cc::Layer and what various
methods do or values mean.

Some cleanup while there, removing redundant child_at() and unused
SetChildren().

Also noticed SafeOpaqueBackgroundColor() is not safe if the root color
is non-opaque since that is what it inherits from. That occurs on the
ChromeOS lock screen, but there are no opaque layers there since
everything is trying to appear like widgets over the transparent space
so we're lucky right now. It would be a bug to try use non-opaque
colors to clear an "opaque" PictureLayer though, so I fixed it to
ensure the color is opaque even coming from the root layer.

R=enne@chromium.org

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I325e3b03c4b4090068bbd1f453bf99a8cbfcd91c
Reviewed-on: https://chromium-review.googlesource.com/1087419Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Commit-Queue: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564975}

This ensures that the memory and clang tot bots run the same tests as the
main waterfall bots.

Everything running on the main waterfall should also be tested under ASan,
and it must be tested with clang/tot too to make sure compiler updates don't
break anything. This change makes it impossible for things to get out of sync
(on mac).

If https://chromium-review.googlesource.com/c/chromium/src/+/1088754 hadn't
been reverted, this would've been behavior-preserving. As-is, it adds
headless_browsertests and headless_unittests to the mac asan bot and the
clang tot bots (which is fine).

Bug: 843511
Change-Id: I5e3cea35d99d630d7eb41154984abc23defe6219
Reviewed-on: https://chromium-review.googlesource.com/1089136
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564974}

Changes:
1. Load item list with "page break" items into paged view structure
   which will be displayed to the user.
2. Add "page break" item based on the changed paged view structure after
   user operations (Add, Remove, Move an item).
3. Since model index (item view's index in view model) is no longer the
   same as item index (item's index in item list), separate them.

BUG=848917

Change-Id: I5d4c750ab87045a0e4930e549a066f24a1c1cf66
Reviewed-on: https://chromium-review.googlesource.com/1083492Reviewed-by: Michael Wasserman <msw@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Weidong Guo <weidongg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564973}

This is a new metric added in http://aosp/681827.

Bug: b:77884453
Change-Id: I0035cd3e50c440564640aae90e68d2ad7a891017
Reviewed-on: https://chromium-review.googlesource.com/1086280Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Sen Jiang <senj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564972}

This reverts commit f832578e.

Reason for revert: GetOverflowStringName is firing a DCHECK on audio elements. Note that audio elements have the picture-in-picture button (it's just hidden), so the code will need to handle that case

Original change's description:
> [Media Controls] Add Exit Picture-in-Picture button.
> 
> This makes sure clicking the native Picture-in-Picture button (after
> entering Picture-in-Picture) exits Picture-in-Picture and that video
> controls are reflected when entering and exiting Picture-in-Picture.
> 
> Screenshot: https://i.imgur.com/081Xbmb.png
> 
> Bug: 840516, 806249
> Change-Id: I410a4a06cc4eea62dae8e1d368e4d05394f13c86
> Reviewed-on: https://chromium-review.googlesource.com/1084833
> Commit-Queue: François Beaufort <beaufort.francois@gmail.com>
> Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
> Reviewed-by: Jochen Eisinger <jochen@chromium.org>
> Reviewed-by: apacible <apacible@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#564807}

TBR=beaufort.francois@gmail.com,mlamouri@chromium.org,apacible@chromium.org,jochen@chromium.org

Change-Id: Ie6373e9c2e77bb41ac6a5e9a32f59a2b6ce3bf03
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 840516, 806249
Reviewed-on: https://chromium-review.googlesource.com/1089209Reviewed-by: Tommy Steimel <steimel@chromium.org>
Commit-Queue: Tommy Steimel <steimel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564971}

Implements two fixes that were causing testStartActivityTriggersDoff* to
fail 100% of the time.

1. Waits until the UI is quiescent after starting the activity, as
previously, clicks were being sent before the DOFF prompt was visible,
causing the test to time out.

2. Applies a small deadzone to the head offset used for repositioning
the VR controller on 6DOF devices. Even on 3DOF devices, the offset
drifted within a very tiny area, which cause the controller to be
perpetually dirty and prevent the UI from reaching quiescence.

Bug: 831589, 848074
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;master.tryserver.chromium.linux:linux_vr
Change-Id: Ic912dd3aa92ac2102c34e4acc330447a3ce0ca8d
Reviewed-on: https://chromium-review.googlesource.com/1087723
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564970}

https://chromium.googlesource.com/webm/libvpx.git/+log/3f7e6cc02044..87386826a95f

$ git log 3f7e6cc02..87386826a --date=short --no-merges --format='%ad %ae %s'
2018-06-05 jianj vp9: Move up reset of cyclic refresh under dynamic resize.
2018-05-25 lu_zero force-inline the convolve functions
2018-06-01 jzern test,cosmetics: fix func/member naming, decl order
2018-06-01 jianj vp9-svc: Allow usage of second (long term) temporal reference.
2018-05-28 lu_zero Unbreak the force inline directive for gcc

Created with:
  roll-dep src/third_party/libvpx/source/libvpx
R=johannkoenig@google.com

Change-Id: I0cf5ac87ea7b6477a0fe18d1e4ebe371fc923e87
Reviewed-on: https://chromium-review.googlesource.com/1089192Reviewed-by: Johann Koenig <johannkoenig@google.com>
Commit-Queue: Jerome Jiang <jianj@google.com>
Cr-Commit-Position: refs/heads/master@{#564969}

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

This does not enable the whole feature, which also requires being in a
server-side whitelist.

Bug: 836246
Change-Id: I6be61a5a18ba1e102d9dceaf801ecdf24931dd9d
Reviewed-on: https://chromium-review.googlesource.com/1088930Reviewed-by: Yury Khmel <khmel@chromium.org>
Commit-Queue: Bruno Kim Medeiros Cesar <brunokim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564967}

BUG=837700
TEST=covered by tests

Change-Id: Ie188a430a9596a520e0643083d89aaf4f09f4215
Reviewed-on: https://chromium-review.googlesource.com/1089112
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564966}

BUG=chromium:721891

Change-Id: Ief16bef5e035b3a8cc767395cd220938c7cbf329
Reviewed-on: https://chromium-review.googlesource.com/1081428
Commit-Queue: Jonathan Brandmeyer <jbrandmeyer@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564965}

https://chromium.googlesource.com/angle/angle.git/+log/096a6c8..2bd1fab


git log 096a6c8..2bd1fab --date=short --no-merges --format='%ad %ae %s'
2018-06-06 geofflang@chromium.org Update dEQP expectations after June 2018 roll.
2018-06-06 jiajia.qin@intel.com Fix the divide by zero exception in BindBufferRange


Created with:
  gclient setdep -r src/third_party/angle@2bd1fab

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

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

With this CL, the KeyboardAccessory uses the 'uifood' flag next to the
already existing 'passwords-keyboard-accessory' flag to enable all
passwords-related keyboard accessory activity.
(Currently, that is only the PWD generation and a still invisible
bottom sheet.)

In order to do that, the uifood flag was exposed to Android.

Also: one-line (maybe temporary) null check to prevent crashes for the
experimental implementation of the generation feature.

Bug: 828832, 811747
Change-Id: I8cd2645dff6a4cc760e8309e60ba5190d6da25e1
Reviewed-on: https://chromium-review.googlesource.com/1085464
Commit-Queue: Friedrich Horschig <fhorschig@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564963}

base::Time already has a null value, so adding mojo's nullable type
support on top of base::Time is more confusing than useful.

Bug: 729800
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: I6016a46b48b4efc4e9b584bc5c3062849dab60a0
Reviewed-on: https://chromium-review.googlesource.com/1087539Reviewed-by: Tom Sepez <tsepez@chromium.org>
Commit-Queue: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564962}

Rationale for owner choices: keep-alive seem mostly related to browser
UI and Chrome apps. I eliminated OWNERS from chrome/browser/ui who were
already listed in >20 OWNERS files.

Bug: None
Change-Id: I4769e2c5dafc809d500b1e71669decfd745adda6
Reviewed-on: https://chromium-review.googlesource.com/1086303Reviewed-by: Colin Blundell <blundell@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Reviewed-by: Ben Wells <benwells@chromium.org>
Commit-Queue: Michael Giuffrida <michaelpg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564961}

Using wpt-import in Chromium 94392859.
With Chromium commits locally applied on WPT:
e8832df8 "webrtc wpt: remove test_state_change_event"


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

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:
kojii@chromium.org:
  external/wpt/css/css-text/overflow-wrap

TBR=foolip

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

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/830256ae..9930a7e4

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

Bug: 834392
Change-Id: I4b7f51e74b08e49199b8fd88137b15184db77043
Reviewed-on: https://chromium-review.googlesource.com/1086600Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Manu Cornet <manucornet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564958}

Bug: 839610
Change-Id: I4a4ee5e8c80a57a32f8368fe3716803c82148183
Reviewed-on: https://chromium-review.googlesource.com/1086068Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Commit-Queue: Quan Nguyen <qnnguyen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564957}

After this CL, the CORB warning should be suppressed for:
- Responses with 'Content-Length: 0' response header
- Responses with 204 http status.

Bug: 844178
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: I320c9e221d94c3deeef26b96a5ff70b41ea1c2a8
Reviewed-on: https://chromium-review.googlesource.com/1070551
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564956}

When the page zooms, for example, to 200%, the offset of the shadow
remains the same as when the page scale is 100%. The problem here is
that whenever we zoom the page, we queue a paint call back. Then the
new paint call back will set the shadow offset with the size that doesn't
account for the page zoom.

The fix is to override the BaseRenderingContext2d::setShadowOffset
method with the zoom.

This CL also includes a layout test to verify the correctness of the fix.

Bug: 849706
Change-Id: I427209fca397a7540936bccd9e8fb18ba7c018ba
Reviewed-on: https://chromium-review.googlesource.com/1087874Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#564955}