GitLab

This test will report the size-on-disk of various system partitions,
including the one that hosts the chrome installation.

Bug: 537081
Change-Id: Ibaa14023c45bf890d1bd5d93a5213eb9263fa439
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994044Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732609}

Add a PIECEWISE_HDR transfer function that is sRGB scaled to hit 1 at
the the specified "SDR joint" in the domain, and then grows linearly
to the specified "HDR level" at 1.

Add the math for this transfer function. Add tests to hit all segments
of the function, for a handful of parameter values.

Add GLSL for this transfer function. Add it transfer function as the
source and target for GL pixel tests.

Bug: 958166
Change-Id: If53dc04777dbf105c465f121bcbcc1dabc1c1ee9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003811
Commit-Queue: ccameron <ccameron@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732608}

The function checks a deleted element. I switched to checking enrollment
step.

Bug: 1042594
Test: manual call of the function in devtools
Change-Id: I3f0cdc0336bc6be431e68a798aee95d8447052a3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002513Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Commit-Queue: Roman Sorokin [CET] <rsorokin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732607}

This removes the MediaController knob panel below the video
player, and replaces it with controls that are overlaid on
top of the video (and fade away after a small amount of time).

Also introduces a Mute button.

Bug: 895776, 656015
Change-Id: If89fa712c70b62eeda550be87478562c1a118914
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992436Reviewed-by: Theresa  <twellington@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: Finnur Thorarinsson <finnur@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732606}

A minor cleanup to reduce diff noise on more substantive CLs.

Updates //fuchsia GN files to incorporate recent updates
in how "gn format"'s formats lists with single items.

All changes in this CL were produced by running "git cl format".

Change-Id: I5229dfe9c6989a3ec8b258a9abc06c33c68e5c29
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2006108
Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
Commit-Queue: Fabrice de Gans-Riberi <fdegans@chromium.org>
Reviewed-by: Fabrice de Gans-Riberi <fdegans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732605}

Bug: 1012776, 1012819
Change-Id: Iecf5ce14ec8150e69ac852a818263e5598049817
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003193
Commit-Queue: Haiyang Pan <hypan@google.com>
Reviewed-by: Peter Wen <wnwen@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732604}

The resident size recorded from the metrics show it is never 0. The
devcies in the lab might get a 0 value if some code tries to override
mallinfo. So, remove this unnecessary check. If the metrics go wrong in
future, we can detect that from the UMA.

BUG=843843

Change-Id: Ie9a2e9f5e3f18b1572e45ef8db291f155dbe7c7a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2004903
Auto-Submit: ssid <ssid@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Reviewed-by: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732603}

Following from https://chromium-review.googlesource.com/1984792, this CL
removes a further redundant call to WebLaunchFilesHelper::SetLaunchPaths,
this time in OpenApplicationWindow.

Bug: 1007621
Change-Id: I79732f93499b209fce42db9a758969bc8b8d8c7c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003159Reviewed-by: Michael Wasserman <msw@chromium.org>
Commit-Queue: Robert Woods <robertwoods@google.com>
Cr-Commit-Position: refs/heads/master@{#732602}

Currently the BinaryUploadService tracks authorization by checking the DM
token with the server. For Advanced Protection users, we will not have a
DM token, so we need to authorize the upload another way. This CL adds a check
for whether the user is truly enrolled in APP as the authorization.

Bug: 1020418
Change-Id: Ie9d61906aeed1fbb68fb68d455a5c24c9d5d31fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001107
Commit-Queue: Daniel Rubery <drubery@chromium.org>
Reviewed-by: Bettina Dea <bdea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732601}

This CL checks the existing setting for predictive operations to ensure
users are comfortable with predictively connecting to the search engine
without them explicitly searching.

This also cleans up the code a little bit to move the call to loading
predictor.

Bug: 1036489
Change-Id: Ibe4672cf2f7a2fcc5c678a09833a2ee4df300f21
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992589
Commit-Queue: Ryan Sturm <ryansturm@chromium.org>
Reviewed-by: Alex Ilin <alexilin@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732600}

Change-Id: I6b866e83eba6beb749d9cae58323a6b3988771f9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1982920
Commit-Queue: Nasko Oskov <nasko@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732599}

This interaction handler implements logic shared amongst all infobar
modal implementations.  This class encompasses the model-layer updates
possible from the InfobarModalDelegate protocol.  These handlers will
be subclassed to handle interaction events for other protocols that
conform to InfobarModalDelegate.

InfobarModalOverlayRequestCallbackInstaller installs callbacks that
execute the main action for an infobar modal for dispatched
InfobarModalMainActionResponses.  As with the interaction handlers,
subclasses will be created to handle responses corresponding with
InfobarModalDelegate protocols.

Bug: 1030357
Change-Id: I896299166f982bf842e938e325b4318786f759e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1999453
Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org>
Reviewed-by: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732598}

Idrefs encountered in <svg:use/> instance trees now referenced the
originating scope as per the spec (and firefox). Introduces a new
node::GetSourceTreeScope() method to facilitate this which can also be
used for bringing style resolution up to the current spec.
(see https://svgwg.org/svg2-draft/struct.html#UseStyleInheritance)

Stop flattening shadow trees of nested <svg:use/> elements as this
is not to spec and was a workaround for the fact that use elements
couldn't resolve their targets from inside a use shadow tree.

Fix instance leak when removing use elements
(removal now tears down instance references).

Fix interaction between SVG relative lengths and shadow dom.

This does not change any webexposed behavior (svg:use has closed shadow dom).
DevTools APIs (invalidation, etc.) and the `internals` testing hook are affected
(hence the rebaselined tests).

Bug: 785246
Change-Id: Ie2429c0cf9ab6aa6bc7851269cf286d3ecb200ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986325Reviewed-by: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: George Steel <gtsteel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732597}

This reverts commit 4af59255.

Reason for revert: broken linux-archive-rel build

Build error is 

Build failure is: ENOENT: no such file or directory, open '/b/s/w/ir/cache/builder/src/out/Release/gen/ui/webui/resources/cr_elements/cr_splitter/cr_splitter.m.js'

Build is here:
https://ci.chromium.org/p/chromium/builders/ci/linux-archive-rel/19235

Original change's description:
> WebUI: Stop auto-generating Polymer 3 version of cr-splitter.
> 
> The Polymer 2 version is not used anymore, therefore no auto-generation
> is necessary and the v3 version can be directly checked in.
> 
> Fixed: 1042545
> Change-Id: I5054477c0b7427f4ec6b760e5da3eac904af2320
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003114
> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
> Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org>
> Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#732590}

TBR=dpapad@chromium.org,rbpotter@chromium.org

Change-Id: I363a778967e7be5fafc11fb1a72cebdd5c8dac16
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2006214Reviewed-by: Aleks Totic <atotic@chromium.org>
Commit-Queue: Aleks Totic <atotic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732596}

With OOP-D on all platforms, HostFrameSinkManager will never be in the
same process as FrameSinkManagerImpl, so HostFrameSinkManagerLocalTest
no longer makes much sense. Merge it with HostFrameSinkManagerRemoteTest
into HostFrameSinkManagerTest, and refactor the tests to work on remote.

CommunicateFrameToken and HitTestAggregatorQuery require access to
CompositorFrameSinkSupport, but they test things out of scope of this
class, so they can be removed.

Bug: 1033683
Change-Id: I32e1150d7f7858c24f7733b8ad5e62ac242a6fac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1972895Reviewed-by: kylechar <kylechar@chromium.org>
Commit-Queue: Sean Gilhuly <sgilhuly@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732595}

1. Add Begin and End functions to the GL command buffer for
accessing a batch of shared images instead of a single shared
image.

2. Add a new class SharedImageBatchAccessManager to manage the
batch access to the shared images.

3. Add a ScopedBatchReadAccess class in DisplayResourceProvider
to do begin/end read access to a batch of shared images.

4. Update DisplayResourceProvider to do batch read access.

5. Update SharedImageBackingEGL and SharedImageManager to support
batch read access.

Change-Id: I4089ab2e81dc61e5a3c78b860fe96e477dea754a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1999066Reviewed-by: Eric Karl <ericrk@chromium.org>
Commit-Queue: vikas soni <vikassoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732594}

Change-Id: Iff07fe6dc3ba057c38364ea0eba8ae7741083b96
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003641
Commit-Queue: vikas soni <vikassoni@chromium.org>
Reviewed-by: Frank Liberato <liberato@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732593}

Enables scroll to text by default for M81. Note we plan to launch via
Finch for M80.

Intent to ship with LGTMs:
https://groups.google.com/a/chromium.org/d/msg/blink-dev/zlLSxQ9BA8Y/t-_3pAiSAwAJ

This patch also updates web platform test expectations:
- scroll-to-text-fragment.html now passes; it just needed an extra rAF
  for the fallback to element anchor behavior.
- scroll-to-text-fragment-security.html has two expected failures, as
  they need to be updated to test cross-origin navigations. I'll make
  this change in a follow-up patch to close bug 1042311.

Bug: 919204
Change-Id: Ic2d563934cd9406fb335904a94c390bba789e0b4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1838701Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Nick Burris <nburris@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732592}

This is a revert of
https://chromium-review.googlesource.com/c/chromium/src/+/1986342
now that the root cause was fixed by
https://chromium-review.googlesource.com/c/chromium/src/+/1987297


Bug: 1039019
Change-Id: I865d0e256e00d1cf615b6d2fe7c006f303aee0ea
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002944
Commit-Queue: Caleb Rouleau <crouleau@chromium.org>
Auto-Submit: Caleb Rouleau <crouleau@chromium.org>
Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732591}

The Polymer 2 version is not used anymore, therefore no auto-generation
is necessary and the v3 version can be directly checked in.

Fixed: 1042545
Change-Id: I5054477c0b7427f4ec6b760e5da3eac904af2320
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003114
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732590}

This CL adds more tests for Timing-Allow-Origin checks in ElementTiming
and LargestContentfulPaint with multiple redirects. Before, we had tests
for:
* Single cross-origin response with a TAO header (image-TAO.sub.html).
* Multiple redirects, with '*' TAO header (multi-redirect-image.html).

This CL renames the latter to be more descriptive and adds:
* Same-origin redirect tests (should pass without TAO headers).
* Multi-cross-origin redirect tests with various TAO header values.

Bug: 1003943
Change-Id: Id44f0f18f143c8ca4ee3ca40c2383fa2ae22590c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001070
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732589}

This seems to be a majority of the failures for invalid deserialization
errors with PaintOpBuffers and its unclear whether this is just fallout
from failure to deserialize an inlined SkTextBlob or a caching error.

Skip performing a crash dump for the cache error cases to make this
clearer.

R=ericrk@chromium.org

Bug: 1019634
Change-Id: Ia882b918dc0630a89c7507fb0154f6fb08ee0087
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001584
Auto-Submit: Khushal <khushalsagar@chromium.org>
Reviewed-by: Eric Karl <ericrk@chromium.org>
Commit-Queue: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732588}

There is a data race in
LayerTreeHostScrollbarsPixelTest.HugeTransformScale caused by
TestGpuServiceHolder being initialized before the command line options
for Vulkan are set in LayerTreeTest::RunTest(). The test was not running
using Vulkan, and was passing as a false positive.

Set |renderer_type_| in the constructor of LayerTreeTest and move the
command line initialization there to make sure that these options are
set before any of the test body code is run. To clean up, remove
RendererType from the LayerTreePixelTest::RunTest() variants, and
replace some direct checks to |renderer_type_|.

Bug: 1040259
Change-Id: If47923b5ba21190733d584b0a709276c46710527
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003171Reviewed-by: kylechar <kylechar@chromium.org>
Commit-Queue: Sean Gilhuly <sgilhuly@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732587}

Change-Id: Id3998f7ae6dd0de5449a184481afd392e549b889
Bug: 1042531
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003070
Commit-Queue: Cathy Li <chili@chromium.org>
Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732586}

Previously this caused SharedImageStub::
MakeContextCurrentAndCreateFactory() to get a kSuccess and use nullptr
as |context_state_|.

Bug: 1027768
Change-Id: Icc8c7c2e5efa3e8a5aa24d1c340b4f355a6a5ed5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1997638
Commit-Queue: Kramer Ge <fangzhoug@chromium.org>
Reviewed-by: Eric Karl <ericrk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732585}

When the feature is enabled shelf navigation controls (home and back
button) and overview button will be hidden from shelf (in favor of
gesture navigation). The feature is disabled by default.

BUG=1012814

Change-Id: I372a11efec9e9ed5b0e92c0a73b9b4a9c739c493
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995776
Commit-Queue: Toni Baržić <tbarzic@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Manu Cornet <manucornet@chromium.org>
Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732584}

Manual tests run:
- Tab traverse forwards
- Tab traverse backwards
- ChromeVox traverse forwards
- ChromeVox traverse backwards
- Click inside non-navigable card
- Tap inside non-navigable card
- Click inside navigable card
- Tap inside navigable card
- Tab traverse multiple cards

Bug: b:146351046
Change-Id: I72bb661765792ec0d222c39dd82df3f0795d6d81
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003219Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Commit-Queue: David Black <dmblack@google.com>
Cr-Commit-Position: refs/heads/master@{#732583}

* Adjust the width of the '+' button in new tab variation from 48dp to
56dp.
* Properly tint the '+' button for light/dark mode.

Bug: 1042606, 1042015
Change-Id: I47a29b9d29ab7a5d719ec183c4c88de240eb399e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2005549
Auto-Submit: Yue Zhang <yuezhanggg@chromium.org>
Reviewed-by: Theresa  <twellington@chromium.org>
Commit-Queue: Yue Zhang <yuezhanggg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732582}

The group name has been changed to Enabled_20191111 some time back

Change-Id: Ifb62c159f9ac02d21bece604e17ccb22e3464b91
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002744Reviewed-by: Jesse Doherty <jwd@chromium.org>
Commit-Queue: Min Qin <qinmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732581}

Currently, when a group is moved, there is a tab-moved event that is
fired for every single tab in the group. This leads to issues when
trying to preserve the parent-child relationship of the TabGroup
and the TabElement when certain tab-moved events have fired before
others and leads to temporary re-ordering of tabs within the group.

This CL coalesces multiple tab-moved events to a synthetic group-moved
event only after every tab-moved event is fired, so that the TabGroup
element is only moved once.

Bug: 1027373
Change-Id: I70ccddd4cb674642a219cab6f7cecc9166bf6f12
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001744
Commit-Queue: John Lee <johntlee@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732580}

This includes switching into a grouped tab and tab creation.

Bug: 1040657
Change-Id: I48aa185a8be5a383bb4253061b5860d1cd73b022
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995955Reviewed-by: Peter Boström <pbos@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Connie Wan <connily@chromium.org>
Commit-Queue: Charlene Yan <cyan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732579}

The identity pill has been launched and was enabled by default. It can
now be enabled permanently.

Change-Id: I01d1fe957d81c5729dc10e3f40a81864773c1240
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2000117Reviewed-by: Jan Krcal <jkrcal@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Auto-Submit: David Roger <droger@chromium.org>
Commit-Queue: Jesse Doherty <jwd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732578}

This is still useful, increase the milestone.

Bug: 1037425
Change-Id: I667130d5594f76fce5413b13a01a0c8087c12484
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1997553Reviewed-by: Jesse Doherty <jwd@chromium.org>
Commit-Queue: Jesse Doherty <jwd@chromium.org>
Auto-Submit: Alex Newcomer <newcomer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732577}

Removing the histogram because we have historically not looked at it
and we now have UKM which will give us more accurate data

BUG=1042133

Change-Id: Ib8d05040b017586bd7ef653d505d9d6e0a8e4dd1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001853
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Reviewed-by: Glenn Hartmann <hartmanng@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732576}

When merging 2 pending layers, merge rect_known_to_be_opaque if
possible instead of just use that of the home pending layer.

This also fixed a bug that the home layer's rect_known_to_be_opaque
should be updated when the merged state is different from its
previous state.

Thanks pdr@ for contributing the UniteRectsKnownToBeOpaque()
algorithm.

Bug: 701991, 1029620
Change-Id: Id8d5d1b35c12959069176d7de18e59c636ac122c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001235Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732575}

TBR=fserb@chromium.org

Change-Id: I05a35c241e4f9793675c6a56e38362928ce831b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001292Reviewed-by: Khushal <khushalsagar@chromium.org>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Commit-Queue: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732574}

- Remove an extra heading under "Rebaselining using try jobs" >
  "Options".
- Add doc for '--patchset=n'.
- Add link to local manual rebaselining.

TBR=robertma@chromium.org

Change-Id: I54d1daf6754707009c08cbc53791a70262bca206
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2005408
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732573}

The issue happened when an SVG background image was painted with a very
small background size rounded to zero, causing infinite tile scale and
DCHECK failure in ClipRectOp.

Bug: 1039762
Change-Id: Ia94ce2fd350b28696ef8068bd0e756bfc6d87a72
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002839
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Reviewed-by: Kevin Marshall <kmarshall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732572}

This reverts commit 3c4c13ac.

Reason for revert: Made ChromeVoxBackgroundTest.SelectSingleBasic flaky

Original change's description:
> Move LayoutMenuList::DidUpdateActiveOption() to HTMLSelectElement
> 
> Also,
>  - Remove LayoutMenuList::DidSelectOption().
>  - Add HTMLFormControlElement::UpdateFromElement() to add
>   DidUpdateMenuListActiveOption() to each of
>   LayoutMenuList::UpdateFromElement() calls.
> 
> This CL is a preparation to build a LayoutNG counterpart of LayoutMenuList.
> This CL has no behavior changes.
> 
> Bug: 1040828
> Change-Id: If7917af101119a830e899a50711a6c1491e22eb3
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003164
> Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
> Commit-Queue: Kent Tamura <tkent@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#732313}

TBR=yosin@chromium.org,tkent@chromium.org,kojii@chromium.org

Change-Id: I4f571b72f01f0494fc855c1ceb3841e7ff02a963
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1040828
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2006268Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732571}

Current implementation of FilterOperation::MapRectReverse() for a blur
filter actually does a forward (outset) map of the rect. This patch
fixes the erroneous behavior by supporting MapRectReverse() to map
backward for a blur filter.

Bug: 916583
Change-Id: I43bf4498b89e18ba9c2d1eb341e977944e2226c4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986646Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Md. Hasanur Rashid <hasanur.r@samsung.com>
Cr-Commit-Position: refs/heads/master@{#732570}