GitLab

Originally GpuVideoAcceleratorFactoriesImpl get HW encoder
capabilities by referencing values stored GpuInfo instance.
However, the values are not updated after GPU process boots up.
Even if a new hw encoder is available after GPU process is
initialized, the hw encoder is not detected.

This fixes the problem by querying GPU process the hw encoder
capabilities when a render process is created. e.g. open the
page.

Bug: b:147404923
Test: HW encoder is used at appr.tc
Test: tast run webrtc.* on krane
Change-Id: Ibca82b6e54e9b5d585037c8e63f4c663d085db0e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994849Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Commit-Queue: Hirokazu Honda <hiroh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735339}

The CL that was causing the failure has been reverted in
8d4d0ff0. Re-enabling the tests.

This reverts commit 1ea2a91b.

Bug: 1043665
Change-Id: Idd8d15db36bb35cf76b9172baff381ac2f78c8d5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2019368Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: Monica Basta <msalama@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735338}

This fixes paint invalidation problem, because this function
is used in |LayoutObject::AdjustStyleDifference| to optimize
invalidations.

Fixes ~45 failures.

Bug: 982194
Change-Id: I2c749aed856bdbf8e06b2fb5c1f50b266a68efb9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2022444
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735337}

The original code of VaapiVEA expects the dimension of the GMB-based
VideoFrame on Encode() to be the same as the one aligned by minigbm.
This is wrong; GMB-based VideoFrame has a dimension specified by
an application (e.g. webrtc app). In other words, the size is not
aligned at all.

This fixes the wrongness. See https://tinyurl.com/frame-dimension-in-VEA
for the detail.

Bug: 982201
Test: Hangout Meet on atlas
Test: video.EncodeAccel.*
Change-Id: I7b42c9e1b2486cb7b95715185e071f0cefcf7597
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1997426Reviewed-by: David Staessens <dstaessens@chromium.org>
Reviewed-by: Alexandre Courbot <acourbot@chromium.org>
Commit-Queue: Hirokazu Honda <hiroh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735336}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/05d914745a97..5a0e94681cf8


Created with:
  gclient setdep -r src-internal@5a0e94681cf8

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll
Please CC jbudorick@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome
Bug: None
Tbr: jbudorick@google.com
Change-Id: Ia90648bc57068a221102c379ac005efd0f5464dd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2022608Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#735335}

crrev.com/c/1982499 started passing NativePixmapHandles to the GL import
methods instead of raw DMAbuf FDs without layout information. But
creating a NativePixmapHandles involves duplicating the FDs of a frame ;
something that would fail on Tegra which passed invalid FDs that were to
be ignored during import.

Fix this by returning a dummy FD created from pipe() instead of an
invalid one. The dummy FD is not any more useful, but it can be
duplicated safely.

BUG=b:148105252
TEST=video_decode_accelerator_tests passing on nyan_big.

Change-Id: Ifda5f98d8383f4883494d13708a45783149810f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016817Reviewed-by: Miguel Casas <mcasas@chromium.org>
Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735334}

Bug: 1011392
Change-Id: Ibca97cfb784e396ef56b796d401ee23704996da2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2021785Reviewed-by: Adam Rice <ricea@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735333}

Behaviors have been unclear, but if requests are made from a custom
scheme, the Origin header in outgoing requests should be set to
"<scheme>://" without containing the host:port part those are
officially required to be a proper origin for such special cases
in WebView.
Servers can use "Access-Control-Allow-Origin: *" or
"Access-Control-Allow-Origin: <scheme>://" to permit such accesses.

This patch adds tests to verify these behaviors to keep compatible
behaviors.

Bug: 1035366
Change-Id: Ia08e7b4ed764225566c3b09edef2980cfa1b1b70
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010591Reviewed-by: Richard Coles <torne@chromium.org>
Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735332}

This CL removes support for sharing URLs through NFC aka Android Beam as
it is being deprecating.

https://android-review.googlesource.com/q/topic:%22Deprecate-android-beam%22)

Change-Id: Idb8445e962cdb8d52d870c2f919b67e1b302520a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989754
Commit-Queue: François Beaufort <beaufort.francois@gmail.com>
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Reviewed-by: Boris Sazonov <bsazonov@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735331}

This patch fixes |NGInlineCursor::InternalMoveTo|:
1. When |FirstInlineFragmentItemIndex| is not available and
   |this| is not at the beginning, it sets |item_iter_| but
   forgot to set |item_|.
2. When |this| did not have a root, it adds item index to
   span. It should be span index instead.

Bug: 982194
Change-Id: If14c1fe0a99c816789ee85a7695bb4ffceaeceed
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2022443
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735330}

https://skia.googlesource.com/skia.git/+log/f93a8436cea5..0fb0a21bd999

git log f93a8436cea5..0fb0a21bd999 --date=short --first-parent --format='%ad %ae %s'
2020-01-27 skia-autoroll@skia-public.iam.gserviceaccount.com Roll ../src 2ae61982..82459860 (508 commits)
2020-01-27 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/angle2 f3b4e6c3030f..fcef6dcb6ab2 (15 commits)
2020-01-27 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader 5ef91b82cbed..748ad200897b (6 commits)

Created with:
  gclient setdep -r src/third_party/skia@0fb0a21bd999

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/skia-autoroll
Please CC reed@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Bug: None
Tbr: reed@google.com
Change-Id: Ie231f3934adc9f600dc81f84deda7bcabc8b1ecb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2020580Reviewed-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@{#735329}

Include changes to always prefer AAT over GSUB in horizontal runs, but
prefer GSUB over AAT in vertical for reasons of better control over
glyph rotation in OpenType `vert` feature.

Fallback positioning whitespace size difference in baselines explained
in issue chromium:1040017.

https://chromium.googlesource.com/external/github.com/harfbuzz/harfbuzz.git/+log/82545c5e2ba2..544031392417

$ git log 82545c5e2..544031392 --date=short --no-merges --format='%ad %ae %s'
2020-01-26 ebrahim Update COPYING
2020-01-25 ebrahim minor
2020-01-24 ebrahim Run morx if run is horizontal or GSUB doesn't exist
2020-01-25 ebrahim [test] Increase subset timeout
2020-01-25 ebrahim [tests] Apply expected results of Mplus1p-Regular subset
2020-01-24 ebrahim [sbix] minor style fixes
2020-01-21 qxliu [subset] Add "--name-languages" and "--name-legacy" options Make name table subsetting consistent with fontTools
2020-01-24 ebrahim Disable hb_ot_glyph_decompose in HB_TINY
2020-01-24 59700018+ckitagawa-work [subset] sbix fix missed offset is_null() check
2020-01-23 ebrahim [ot-glyph] Add a test for #2053
2020-01-24 ebrahim [cmake] Don't build src/main
2020-01-24 ebrahim [ci] Increase msan and fedora-O0 bots subset fuzzer timeout
2020-01-24 ebrahim [src/main] separate the places use private API, minor
2020-01-24 ebrahim Fold src/test-ot-glyph and src/test-ot-color into src/main
2020-01-23 ebrahim [test] Adopt test-ot-color with ot-glyph and remove freetype/cairo dependecy
2020-01-24 ebrahim Revert "[subset] Add "--name-languages" and "--name-legacy" options"
2020-01-24 drott Only prefer AAT morx for horizontal layout
2020-01-21 qxliu [subset] Add "--name-languages" and "--name-legacy" options Make name table subsetting consistent with fontTools
2020-01-22 qxliu [subset] Cmap table: remove encodingRecord entry for empty cmap4 subtable
2020-01-23 ckitagawa Move push call to caller
2020-01-23 ckitagawa [subset] Fix UBSAN issue in sbix
2020-01-22 ariza add api test
2020-01-22 ariza refix PR #2087 subset PairPos1
2020-01-23 ebrahim [ot-glyph] remove open callback
2020-01-23 ebrahim [ot-glyph] noop->nil, fix close path
2020-01-22 ckitagawa Address garretrieger@'s comments
2020-01-21 ckitagawa Add second fixed test
2020-01-21 ckitagawa Fix style issue
2020-01-21 ckitagawa [subset] Fix sbix fuzz problem
2020-01-18 ariza remove empty lookup subtables
2020-01-17 qxliu [subset] Add more tests for GPOS1 subsetting These tests were left out because of issue: https://github.com/fonttools/fonttools/issues/1709 Now re-adding these tests since the issue is resolved.
2020-01-16 ariza minor: un-include glyf.hh in gvar.hh
2020-01-15 ariza [subset] fixed GPOS device table sanitize & serialize (#2087)
2019-11-01 qxliu [subset] subset lookup/feature/script lists for GSUB/GPOS
2020-01-15 ckitagawa Add unittests
2020-01-14 ckitagawa Simplify copy and add fuzzing coverage
2020-01-14 ckitagawa Address initial comments
2020-01-09 ckitagawa [subset] Support sbix subsetting
2020-01-14 ebrahim [ot-glyph] Add open/close callbacks
2020-01-13 ebrahim [ot-glyph] make hb_ot_glyph_decompose_funcs_t struct opaque
2019-10-31 qxliu [subset] layout closure_features and store them in subset-plan
2020-01-13 drott Fix duplicate check in hb_ot_rotate chars
2020-01-13 ebrahim [ot-glyph] minor on tests
2020-01-12 ebrahim Fix collect lookups logic of FeatureTableSubstitution (#2097)
2020-01-11 ebrahim Fix collect lookups logic of FeatureVariationRecord
2020-01-11 ebrahim Use REPLACEME tag
2019-10-22 qxliu [subset] closure lookups for GSUB/GPOS
2020-01-11 ebrahim [ot-glyph] Add tests for hb_ot_glyph_decompose
2020-01-10 ebrahim [ot-glyphs] fix the tests
2020-01-10 ebrahim [ot-glyphs] Move CFF glyph decompose logic to their tables
(...)
2019-03-20 ariza added TT VF full font test & fixed bugs
2019-03-19 ariza update CFF2 test results
2019-03-19 ariza add api test cases for HVAR with index map (and fix)
2019-03-19 ariza add gvar & HVAR retain-gids test cases
2019-03-19 ariza fix test build
2019-03-19 ariza add api tests for subset gvar & HVAR; bug fixes
2019-03-18 ariza replaced tt var api test with a composite glyph
2019-03-18 ariza move rounding advance width to glyf
2019-03-18 ariza fix empty glyf's advance width
2019-03-18 ariza add api test for tt var advance widths
2019-03-18 ariza fix build
2019-03-17 ariza fix composite glyf extents
2019-03-17 ariza fix unpack_points
2019-03-17 ariza fix infer_delta
2019-03-17 ariza added explicit casts to metrics
2019-03-17 ariza moved most of var code from gvar to glyf
2019-03-16 ariza add components transformation
2019-03-16 ariza fix tt var extents & add test
2019-03-12 ariza add gvar::get_extents
2019-03-01 ariza fix build
2019-03-01 ariza minor edits
2019-03-01 ariza build fix attempt
2019-03-01 ariza more build fixes
2019-03-01 ariza fix build attempt
2019-03-01 ariza calculate VF advance widths from gvar & glyf
2019-02-26 ariza gvar::subset()
2019-02-26 ariza Added hb-ot-var-gvar-table.hh
2019-02-25 ariza renamed hb_map2_t to hb_bimap_h in its own .hh
2019-02-22 ariza subset VVAR & outer indices
2019-02-22 ariza unuse set in hb_map2_t impl
2019-02-21 ariza fixed compiler gripes
2019-02-21 ariza fix CFF2 local subr subsetting
2019-02-21 ariza fix HVAR & VarStore subsetting
2019-02-20 ariza subset HVAR
2019-03-12 ariza add gvar::get_extents
2019-03-01 ariza fix build
2019-03-01 ariza minor edits
2019-03-01 ariza build fix attempt
2019-03-01 ariza more build fixes
2019-03-01 ariza fix build attempt
2019-03-01 ariza calculate VF advance widths from gvar & glyf
2019-02-26 ariza gvar::subset()
2019-02-26 ariza Added hb-ot-var-gvar-table.hh
2019-02-25 ariza renamed hb_map2_t to hb_bimap_h in its own .hh
2019-02-22 ariza subset VVAR & outer indices
2019-02-22 ariza unuse set in hb_map2_t impl
2019-02-21 ariza fixed compiler gripes
2019-02-21 ariza fix CFF2 local subr subsetting
2019-02-21 ariza fix HVAR & VarStore subsetting
2019-02-20 ariza subset HVAR

Created with:
  roll-dep src/third_party/harfbuzz-ng/src
R=bashi@chromium.org,behdad@chromium.org,bungeman@chromium.org,drott@chromium.org,eae@chromium.org,jshin@chromium.org

Bug: 1040017
Change-Id: I5980699aa76e2c588bff78f8db0baa9353b6a24e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2020963
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735328}

Bug: 839389
Change-Id: Ic95b6207bfaccbe91c2165d09614138bed00ba68
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016776
Commit-Queue: Hitoshi Yoshida <peria@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735327}

We generate code of IDL dictionaries under
{core,modules}/xxx/yyy/foo.{cc,h}, and their bindings code under
bindings/{core,modules}/v8/v8_foo.{cc,h}.

If we need the implementation of a dictionary, we included the former
style header files, but bindings team decided to use the latter files as
main include target.

This CL updates the includes and some forward declarations for the
change.


Tbr: kinuko
Bug: 839389, 1034398
Change-Id: I5371bac9dbd4c16d1db0c7fe4091100155ece4ca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016991
Commit-Queue: Hitoshi Yoshida <peria@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735326}

Bug: 839389
Change-Id: Ie5c9bfb9daa3fbd2d8a2f6bdfca69ad7d52a8001
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2022122Reviewed-by: Hitoshi Yoshida <peria@chromium.org>
Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735325}

TBR=haraken@chromium.org

Bug: 839389
Change-Id: I96cf78520e05e7234a176174fbbac17ac6c149c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2014622
Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Hitoshi Yoshida <peria@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735324}

Bug: 1023250
Change-Id: I1a45f712fca7ce79c47f6dd11c858156f7afc8b6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016785
Commit-Queue: Hiroshi Ichikawa <ichikawa@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735323}

The response URL is now used without breaking the DCHECK. This function
uses |url_list_| and |response| to populate response_data->SetURLList(),
with the service worker response url as necessary, but |url_list_|
doesn't have the service worker response url.

Bug: 553535
Change-Id: Id42bdb3b62d52be6b043ef16ff4a6347d8df1fb9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016807Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735322}

This patch changes |MoveTo(const LayoutObject&)| to eliminate
unnecessary code paths due to the changes to culled inline
boxes in r729656 <crrev.com/c/1774425>.

More specifically, this patch changes the function not to
return descendants when |NGFragmentItem| is enabled.

This fix is needed for <crrev.com/c/2016822>.

Bug: 982194
Change-Id: Ia9c6a86359543532aa70032c2752100a5878031b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016771Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735321}

When ServiceWorkerStorage is moved to the Storage Service it
wouldn't be able to access live ServiceWorkerVersions directly.
This CL moves live version lookup to ServiceWorkerRegistry as a
preparation for moving ServiceWorkerStorage to the Storage Service.

Bug: 1039200
Change-Id: Ib5458c558d719a004da11159083fc510d19c6bae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015864Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Kenichi Ishibashi <bashi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735320}

r729656 <crrev.com/c/1774425> sets |NGInlineItem| for inline
boxes without |NGPhysicalBoxFragment|, but failed to do so
when bidi reordering moved placeholder.

This patch fixes to set |NGInlineItem| even for that case.

crrev.com/c/2016771 fails without this fix.

Bug: 982194
Change-Id: I755b359cc2a177e667ff3f655ac147472707d081
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2021565Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735319}

Instead, add a callback and only call exit in the CLI version

Bug: 1044513
Change-Id: Ic0fafb21fea42bf48434c38243f9ba27935eb526
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2019789
Commit-Queue: Victor Vasiliev <vasilvv@chromium.org>
Reviewed-by: Ryan Hamilton <rch@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735318}

This CL lets WaylandBufferManagerGpu allocate buffer ids for
GbmPixmapWayland and WaylandCanvasSurface to make sure they are unique.

Bug: 1039806
Bug: 1039429
Test: no collision between buffer ids
Change-Id: I9c66c1fe234fac45e20dd8792353c93fa4a1cb86
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2006907Reviewed-by: Maksim Sisov <msisov@igalia.com>
Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Commit-Queue: Eliot Courtney <edcourtney@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735317}

It looks only third_party/blink/web_tests/platform/mac-mac10.10/
media/video-layer-crash-expected.png has a different image.
Maybe the expected image is mistaken.

TBR=michaelludwig@google.com

Bug: 1045050
Change-Id: I2d93f6bc49bb8947b33b639077624f6a23992b39
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2022044Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735316}

R8 has now added support (b/122902374) for this, fixing a few
outstanding bugs related to class merging. This also makes build rules
a bit simpler.

Still need to switch Trichrome synchronized proguard over to using
R8 for dexsplitting, then we can remove dexsplitter support entirely.

This CL updates R8 with another patch, but does not change the R8
base version used.

Binary-Size: R8 patch now keeping extra methods.
Bug: 1032609
Change-Id: I79f88736c20d96b718eb129cdbd093fe1cd297b9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2014309
Commit-Queue: Eric Stevenson <estevenson@chromium.org>
Reviewed-by: Sam Maier <smaier@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735315}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/f93a317ccef9..05d914745a97


Created with:
  gclient setdep -r src-internal@05d914745a97

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll
Please CC jbudorick@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome
Bug: None
Tbr: jbudorick@google.com
Change-Id: I0ecb745f7ac01044a5de84c422b13fc861bebb1b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2020576Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#735314}

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

Change-Id: I968c0df974c71c9d85ad457882459e8665e95cbd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2022247Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#735313}

We will make UserLevelMemoryPressureSignal feature available on chrome desktop, because MemoryUsageMonitor is available on Linux, Windows and MacOS X now.
The feature is disabled-by-default and is enabled only on Android by using GCL. So this change doesn't enable the feature on chrome desktop.

Bug: 920922
Change-Id: Idbcdef6693ea3956a3f010065f5d21c5fb4594cc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015474Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Erik Chen <erikchen@chromium.org>
Commit-Queue: Takashi Sakamoto <tasak@google.com>
Cr-Commit-Position: refs/heads/master@{#735312}

This CL adds WPT for a worker loaded from a data URL.
This test is basically same to dedicated-worker-import-data-url.any.js

Bug: 824646
Change-Id: I43faf747c9877c431157e2a3b71d3a2bbad05130
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016784
Commit-Queue: Eriko Kurimoto <elkurin@google.com>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735311}

This reverts commit 9204d725.

Reason for revert: This patch is suspicious to have made LocalNTPCustomBackgroundsThemeTest and LocalNTPBackgroundsAndDarkModeTest flaky.

Original change's description:
> Remove BrowserNonClientView::GetThemeProviderForProfile and just use GetThemeProvider.
> 
> Change-Id: I9c458a7fe05c2ed60c1f9498dd0cea3cc3237455
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2019923
> Commit-Queue: Peter Kasting <pkasting@chromium.org>
> Reviewed-by: Peter Kasting <pkasting@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#735051}

TBR=pkasting@chromium.org,kylixrd@chromium.org
Bug: 1045829

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

Change-Id: I014ef51f6c76a4b461313e969224489f37f340f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2022442Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735310}

This CL adds WPT for SharedWorker.
It checks the behavior when NaN or Infinity is set to ScriptURL and WorkerOptions.

Bug: 10399674
Change-Id: I12d9560ca77e3ed0258ec7ba92af08266ca3bde6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015869
Commit-Queue: Eriko Kurimoto <elkurin@google.com>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735309}

Prior to this CL an 2px outline-offset was used by default for links.
Because we have seen many cases where the focus ring is seen chopped, this
CL changes the offset back to 0px.

Bug: 1044899
Change-Id: I1aa2246a0d4df63a3ad112293c9f8ddca26be29b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2020562
Commit-Queue: Ionel Popescu <iopopesc@microsoft.com>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735308}

Bug: 1014839
Change-Id: I040a679baa9785fd975fabc2253a5d7e9c560608
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1999973Reviewed-by: Jenny Zhang <jennyz@chromium.org>
Reviewed-by: Tony Yeoman <tby@chromium.org>
Commit-Queue: Rachel Wong <wrong@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735307}

This CL finalizes the URL for announcment notification.

TBR=dtrainor@chromium.org

Bug: 1042124
Change-Id: I713a7657c525038b5d4685373fc8155a9ae9c09f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2022342Reviewed-by: Xing Liu <xingliu@chromium.org>
Commit-Queue: Xing Liu <xingliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735306}

Following bot results are included.
1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132
1133 1134 1135 1136 1137 1138 1139

32 lines were removed and 20 lines were deflaked by consecutive
results since 1124.

TBR=yosin@chromium.org
NOTRY=true

Bug: 982194
Change-Id: I30e9c7cc425f22e5d841e888dda6083fa64faea8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2019626Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735305}

https://skia.googlesource.com/skia.git/+log/d92e4e9de7f1..f93a8436cea5

git log d92e4e9de7f1..f93a8436cea5 --date=short --first-parent --format='%ad %ae %s'
2020-01-26 mtklein@google.com support dither in skvm

Created with:
  gclient setdep -r src/third_party/skia@f93a8436cea5

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/skia-autoroll
Please CC reed@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Bug: None
Tbr: reed@google.com
Change-Id: I471269a051a1c8496a0fa126e754f09fc0826728
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2020572Reviewed-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@{#735304}

The CL fixes a bug where the scrollbar thumb and arrows were not being
invalidated when users clicked on them. The root cause here was, the
MouseEvent(s) were not being passed on deep enough into the main thread
scrollbar code (where the logic to invalidate exists).

Bug: 1040258
Change-Id: I3a1b413aea06b437f07e37822e16fcfcab11aef5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008132
Commit-Queue: Rahul Arakeri <arakeri@microsoft.com>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735303}

Because ExpandablePaymentHandlerBrowserTest.CancelPayment is flaky,
disable the test before we find the cause.

Bug: 1045274

Change-Id: Iaa253bccc7edc8141061dd8df5aa921ca1bc89bb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2020570Reviewed-by: Liquan (Max) Gu <maxlg@chromium.org>
Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735302}

https://skia.googlesource.com/skia.git/+log/d3963a330245..d92e4e9de7f1

git log d3963a330245..d92e4e9de7f1 --date=short --first-parent --format='%ad %ae %s'
2020-01-26 mtklein@google.com cache only when SkVM has a JIT

Created with:
  gclient setdep -r src/third_party/skia@d92e4e9de7f1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/skia-autoroll
Please CC reed@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Bug: None
Tbr: reed@google.com
Change-Id: I5f60a3506d97f7adde9c1d94062a0653857aa251
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2021610Reviewed-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@{#735301}

https://skia.googlesource.com/skia.git/+log/f85fe1366887..d3963a330245

git log f85fe1366887..d3963a330245 --date=short --first-parent --format='%ad %ae %s'
2020-01-26 reed@google.com offer raw-array variant of remaining 44 methods

Created with:
  gclient setdep -r src/third_party/skia@d3963a330245

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/skia-autoroll
Please CC reed@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Bug: None
Tbr: reed@google.com
Change-Id: Iab6f42609b5514873817dce4c5df1b20e8bacf6a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2021609Reviewed-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@{#735300}