GitLab

This is to allow us to use the flag within ui/accessibility, as
ui/accessibility cannot depend on chromeos/ or chrome/

BUG=889370
R=dmazzoni,aboxhall

Change-Id: I90c51f123c347975d1bc4ede3ea3900dac04625c
Reviewed-on: https://chromium-review.googlesource.com/c/1314072Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Chris Hall <chrishall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605618}

Bug: 902201
Change-Id: Ib9fd5a5f0e9cc49cf653b6af768d00912c008deb
Reviewed-on: https://chromium-review.googlesource.com/c/1319392
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605617}

https://skia.googlesource.com/skia.git/+log/aa27a834ba5d..2dfab27d6957


git log aa27a834ba5d..2dfab27d6957 --date=short --no-merges --format='%ad %ae %s'
2018-11-06 brianosman@google.com Revert "Fix div-by-zero loophole in gradient factory func"
2018-11-05 brianosman@google.com Revert "Revert "Use float colors for blend constant""
2018-11-05 recipe-roller@chromium.org Roll recipe dependencies (trivial).
2018-11-05 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader 20622c0194bd..4169b31090db (1 commits)
2018-11-05 recipe-roller@chromium.org Roll recipe dependencies (trivial).
2018-11-05 reed@google.com add alternative setters for hinting
2018-11-05 brianosman@google.com Revert "Use float colors for blend constant"
2018-11-05 jvanverth@google.com Fix persp_images with DDL correctly
2018-11-05 michaelludwig@google.com Fix div-by-zero loophole in gradient factory func
2018-11-05 brianosman@google.com Use float colors for blend constant
2018-11-05 brianosman@google.com Use SkPMColor4f throughout clear APIs
2018-11-05 jvanverth@google.com Temporarily disable support of mipmapped flattened YUVA image
2018-11-05 herb@google.com Move Painter implementations into Painter
2018-11-05 mtklein@chromium.org lookup sent types using factory pointer
2018-11-05 csmartdalton@google.com Revert "ccpr: Unblacklist Sandy Bridge/Bay Trail on Mesa"
2018-11-05 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/angle2 37297a4f1440..3d86e89bce7a (1 commits)
2018-11-05 herb@google.com Reorganize to extract GPU main drawing code


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

The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll

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-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;master.tryserver.blink:linux_trusty_blink_rel
TBR=allanmac@chromium.org

Change-Id: I2f2e00a3eace7048c0a2ef603ecbe5a13da700be
Reviewed-on: https://chromium-review.googlesource.com/c/1318159Reviewed-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@{#605616}

Change-Id: I18b6fb62596e00cb8315c5eabd0360cdbe48f59a
Reviewed-on: https://chromium-review.googlesource.com/c/1318803
Commit-Queue: Wez <wez@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605615}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/459aaba03456..6d6e0a8009f2


git log 459aaba03456..6d6e0a8009f2 --date=short --no-merges --format='%ad %ae %s'
2018-11-05 recipe-roller@chromium.org Roll recipe dependencies (trivial).
2018-11-05 recipe-roller@chromium.org Roll recipe dependencies (trivial).


Created with:
  gclient setdep -r src/third_party/depot_tools@6d6e0a8009f2

The AutoRoll server is located here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll

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

Change-Id: Ib11bd44effbf0e8478e60ee2a9c2b545533a151f
Reviewed-on: https://chromium-review.googlesource.com/c/1318160Reviewed-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@{#605614}

This CL removes a now-erroneous overwrite of a valid SSLStatus when
a user performs a same-document navigation that does not result in a
network request.

Bug: 877618
Change-Id: I495b9e43fe11d2dc6650e7f2a4d776d5cf804c5d
Reviewed-on: https://chromium-review.googlesource.com/c/1311126
Commit-Queue: Joe DeBlasio <jdeblasio@chromium.org>
Reviewed-by: Christopher Thompson <cthomp@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Carlos IL <carlosil@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605613}

Since ui/base/touch/touch_device.h and it's implementations
(touch_device*.cc) now cover more than just touch inputs, the CL rename
these files to pointer_device.*.

Bug: 438794
Change-Id: Iea744612f1e4bf7d3e4c6b9e875c9385508f6d10
Reviewed-on: https://chromium-review.googlesource.com/c/1303324Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Zhuoyu Qian <zhuoyu.qian@samsung.com>
Cr-Commit-Position: refs/heads/master@{#605612}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/2f08425d51e7..228942c6f98d


Created with:
  gclient setdep -r src-internal@228942c6f98d

The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll

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.



BUG=chromium:856278
TBR=mmoss@chromium.org

Change-Id: Id8db7f14667919fb18b5b74a0e595e4ef48c22bd
Reviewed-on: https://chromium-review.googlesource.com/c/1319370Reviewed-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@{#605611}

https://google.github.io/styleguide/cppguide.html#Namespace_Names
> Namespace names are all lower-case.

This CL has no behavior changes.

Bug: 889726
Change-Id: Id1a9e25e4c241587268fd9c891a65d3ead832929
Reviewed-on: https://chromium-review.googlesource.com/c/1319389Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Zhuoyu Qian <zhuoyu.qian@samsung.com>
Cr-Commit-Position: refs/heads/master@{#605610}

It has two changes:

https://chromium.googlesource.com/chromium/deps/icu.git/+log/42d5027..834113

One is to cherry-pick an integer overflow fix. The other is to fix
ISO-2022-JP encoding.

Now that 373 code points are encoded as expected. Rebaseline the test results
(delete them because all the code points in those files pass).

Bug: 901255, 900059
Test: See bug 900059
Test: LayoutTests: external/wpt/encoding/legacy-mb-japanese/iso-2022-jp
Test: https://www.w3.org/International/tests/repo/run?base=encoding&batch=encoding-dbl-byte&test=legacy-mb-japanese/iso-2022-jp/iso2022jp-encode-form.html
Change-Id: I474ac74c270b77c46f786b28d04494fadb753694
Reviewed-on: https://chromium-review.googlesource.com/c/1317129Reviewed-by: Joshua Bell <jsbell@chromium.org>
Commit-Queue: Jungshik Shin <jshin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605609}

Enables HeapCompaction for kIncrementalIdleGC and kIncrementalV8FollowupGC.

Bug: 864425

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
Commit-Queue: Keishi Hattori <keishi@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#603477}
Change-Id: I506868b5ea224714491fb4dfd9403e5311550255
Reviewed-on: https://chromium-review.googlesource.com/c/1316954Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605608}

Bug: 898795
Change-Id: I143b0705647563e732e662701f3878126139cb1a
Reviewed-on: https://chromium-review.googlesource.com/c/1318419
Commit-Queue: Charlie Harrison <csharrison@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605607}

Bug: 896861
Change-Id: Ida470c2da886409de0864da4f3a4dfdca117e03e
Reviewed-on: https://chromium-review.googlesource.com/c/1289575Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Alan Cutter <alancutter@chromium.org>
Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Commit-Queue: Azeem Arshad <azeemarshad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605606}

In order to match with test_driver Actions API, we need to change the
button type from string to int in the pointerActionSequence API and the
related web platform tests and layout tests.

Bug: 893480
Change-Id: I151849d31038cf40a2a603196e0f616e15d89072
Reviewed-on: https://chromium-review.googlesource.com/c/1297637
Commit-Queue: Lan Wei <lanwei@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605605}

https://webrtc.googlesource.com/src.git/+log/a9bbd8684936..d7db17b992e4


git log a9bbd8684936..d7db17b992e4 --date=short --no-merges --format='%ad %ae %s'
2018-11-05 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision bf7ad46d..11d7305a (605401:605505)


Created with:
  gclient setdep -r src/third_party/webrtc@d7db17b992e4

The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-chromium-autoroll

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:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng

BUG=chromium:None
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: I582f1055289c2c0315749b93949f0ebb28444850
Reviewed-on: https://chromium-review.googlesource.com/c/1318161Reviewed-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@{#605604}

This CL removes the typemapping of
(blink.mojom.Referrer, content::Referrer) and leaves a TODO: replace
content::Referrer with blink::mojom::Referrer everywhere in the future.

Next step we can move blink/public/platform/referrer.mojom into
blink/public/mojom/.

BUG=789854

Change-Id: I70b52fe762a858d6425177604749ce4e85a7fc9c
Reviewed-on: https://chromium-review.googlesource.com/c/1317348Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Leon Han <leon.han@intel.com>
Cr-Commit-Position: refs/heads/master@{#605603}

Bug: 326740
Change-Id: Iea381d99984249796fb0e11279174a553ea9ce8a
Reviewed-on: https://chromium-review.googlesource.com/c/1313328Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Emircan Uysaler <emircan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605602}

Initializing a struct member with the value of an enum would previously
fail to compile; implement this. This is slightly awkward because the
front end does not scope the enum value to the enum like the C++ (and
JS) bindings but rather only to the library. So the compiler needs to
know the type to which it's being assigned and use that to determine how
the enum's value is intended to be qualified.

Bug: 883496
Change-Id: Id8a9f75d07bb0acb11963ecbd37d4915b36c28e0
Reviewed-on: https://chromium-review.googlesource.com/c/1313286
Commit-Queue: Scott Graham <scottmg@chromium.org>
Reviewed-by: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605601}

This CL simplifies lengthy function calls via Platform::Current() that
obtain the current thread and the main thread by using Thread::Current()
and Thread::MainThread().

Also now-redundant null checks for those functions are removed.

Bug: 826203
Change-Id: Iedfd7f09b5334dc84fa921cdca84ca39ad9b3af9
Reviewed-on: https://chromium-review.googlesource.com/c/1318773Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Yuta Kitamura <yutak@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605600}

Change-Id: I759a8630ea1ae636bfc3954006a2fa5fd6b5299d
Reviewed-on: https://chromium-review.googlesource.com/c/1318732
Commit-Queue: Eric Foo <efoo@chromium.org>
Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605599}

This adds video frame flags, --frame_validator=,
check : compares md5 values computed from video frame with the expected md5
        values. Test fails if there is an unexpected video frame.
dump  : outputs video frames to files

BUG=chromium:856562
TEST=VDA unittest with --test_import
TEST=VDA unittest with --test_import --frame_validator=check
TEST=VDA unittest with --frame_validator=check
TEST=VDA unittest with --frame_validator=check,dump
TEST=VDA unittest with --frame_validator=dump
TEST=VDA unittest with --gtest_filter=VideoDecodeAcceleratorTest.DISABLED_GenMD5 --gtest_also_run_disabled_tests

Change-Id: I1511ef07a2bd01231e9daf1038776324c22e3da5
Reviewed-on: https://chromium-review.googlesource.com/c/1309390Reviewed-by: Alexandre Courbot <acourbot@chromium.org>
Commit-Queue: Hirokazu Honda <hiroh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605598}

R=cmasso@chromium.org

Change-Id: Id3b9912d9b06e0baae9e98e4e51d9da53ec64e6b
Reviewed-on: https://chromium-review.googlesource.com/c/1319331Reviewed-by: Krishna Govind <govind@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605597}

Change-Id: I80a812501aeb3c4d894d687326dac3777b2f54c5
Reviewed-on: https://chromium-review.googlesource.com/c/1318587Reviewed-by: Ryan Tseng <hinoka@chromium.org>
Commit-Queue: Eric Foo <efoo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605596}

This CL simplifies lengthy function calls via Platform::Current() that
obtain the current thread and the main thread by using Thread::Current()
and Thread::MainThread().

Bug: 826203
Change-Id: I18a106751518e361aecfb6e82152359c1b00f3d1
Reviewed-on: https://chromium-review.googlesource.com/c/1319129Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Yuta Kitamura <yutak@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605595}

Bug: 889567
Change-Id: I790222c0e74692214bc10daff7a6aa00478a4b88
Reviewed-on: https://chromium-review.googlesource.com/c/1319109
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605594}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/3d2886849216..c238958c1ca3


git log 3d2886849216..c238958c1ca3 --date=short --no-merges --format='%ad %ae %s'
2018-11-06 chrome-bot@chromium.org Update config settings by config-updater.


Created with:
  gclient setdep -r src/third_party/chromite@c238958c1ca3

The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-chromium-autoroll

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: I07cd28e68dc926a69573e8627859e0e287e92467
Reviewed-on: https://chromium-review.googlesource.com/c/1318164Reviewed-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@{#605593}

This patch changes |NGInlineNode::AssociateItemsWithInlines()| to associate
|NGInlineItem| to |LayoutText| correctly by skipping |NGInlineItem| without
layout object.

Before this patch, |LayoutText| is assocaited |NGIninlineItem| objects
after the |NGIninlineItem.layout_object == nullptr|.

This patch is a preparation of the patch[1].

[1] http://crrev.com/c/1309562 Make Element#innterText to utilize NGInlineItem
instead of NGPaintFragment

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: I41f16ea13ca1e0641cb2a42331d64fa2cd6387ac
Reviewed-on: https://chromium-review.googlesource.com/c/1317217
Commit-Queue: Yoshifumi Inoue <yosin@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605592}

This reverts commit 2bdc43ad.

Reason for revert: crbug.com/900373

Original change's description:
> viz: Turn off or crop primary plane when possible
>
> For many fullscreen cases, the rest of the renderpass quads are solid
> black quads. In that case, we can turn off the primary plane, and not
> having to scan out an full screen of black pixels saves a good deal of
> power. In other cases, we can crop down the primary plane down to the
> content rectangle (youtube channel logo, for example) and save power.
>
> Averaging battery draw measurement over about a minute of play back
> for a fullscreen youtube video, power savings for soraka is around
> 500mW (6.5W to 6.0W) and 300mW for kevin (4.4W to 4.1W), when we
> turn off the primary plane.
>
> Change-Id: I7946d7acab334bffdf2bb49a1d9c424cf46fc610
> Reviewed-on: https://chromium-review.googlesource.com/c/1045256
> Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
> Reviewed-by: Dongseong Hwang <dongseong.hwang@intel.com>
> Commit-Queue: Kristian H. Kristensen <hoegsberg@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#600415}

TBR=dongseong.hwang@intel.com,dcastagna@chromium.org,hoegsberg@chromium.org

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

Bug: 900373
Change-Id: I37857bca0cda656c2e2a83dc04312b9c599976e7
Reviewed-on: https://chromium-review.googlesource.com/c/1318547
Commit-Queue: Wenzhao (Colin) Zang <wzang@chromium.org>
Reviewed-by: Wenzhao (Colin) Zang <wzang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605591}

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

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

This CL makes a few improvements in searching for the Crostini Terminal:
- Allow partial matches (bug 840699). Instead of requiring the entire
word 'terminal', allowa match from just 'ter' (but still require a few
characters to avoid over-triggering).
- Add additional keywords 'linux', 'crostini' (bug 858822).
- Add unlocalized (English) keywords. Users may still search for these
as localizations of Linux/Crostini tend to be tranliterations.

Bug: 840699, 858822
Change-Id: Iabff74d9d8a61c2c2abcc50f9683b381c5dce126
Reviewed-on: https://chromium-review.googlesource.com/c/1280092
Commit-Queue: Timothy Loh <timloh@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605589}

API doesn't ask user to call SetPhotoOptions before TakePhoto.
Therefore TakePhoto should enable blob streams as well if
SetPhotoOptions is not called.

BUG=b:114676133, chromium:900900
TEST=./capture_unittest --gtest_filter="*VideoCaptureDeviceTests/*"
     and take photo in CCA

Change-Id: I72d4f1394fe95aaca768cb366a341796f55fe336
Reviewed-on: https://chromium-review.googlesource.com/c/1314074Reviewed-by: Miguel Casas <mcasas@chromium.org>
Commit-Queue: Heng-ruey Hsu <henryhsu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605588}

When an Element is made the global rootScroller, it can hide the URL bar
like Document scrolling does normally. However, the Element's LayoutBox,
like the LayoutView, is not resized in this case. This means there's a
newly exposed region at the bottom of the screen that's visible beyond
the Element's overflow rect.

LayoutView already has an exception in the PaintLayerClipper for this
case. This CL extends the exception to the root scroller. This fixes hit
testing that descends into child PaintLayers of the root scroller's
layer.

In addition, it also caches an "IsGlobalRootScroller" bit in
LayoutObject for performance, just like the effective bit added in
https://crrev.com/2685a6b3e82be7711c6d3b02f225b1b90bb9bf46

Also added tests to ensure this works in an iframe.

Bug: 798719
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Iaf87db5569ebbe1aa82f20d3cf19868a12ed9539
Reviewed-on: https://chromium-review.googlesource.com/c/1287176
Commit-Queue: David Bokan <bokan@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605587}

This reverts commit ba0225d1.

Reason for revert: breaks internal compilation; see e.g. http://shortn/_9928H1Hk0R

Original change's description:
> Reland "Android: turning on bytecode checker"
> 
> This is a reland of 0301a791
> 
> I don't think this would have caused a runtime chromeos error, since it's
> a build time android change. If it pops up again that I broke the test,
> I will investigate further.
> 
> TBR=retry
> 
> Original change's description:
> > Android: turning on bytecode checker
> >
> > This arg was defaulting to false when it should have defaulted to true.
> >
> > TBR=turning off bytecode checks for certain dirs
> >
> > Bug: 874854
> > Change-Id: I248ccab0ed52079106b07e43a302927bfa4414c8
> > Reviewed-on: https://chromium-review.googlesource.com/c/1309973
> > Commit-Queue: Sam Maier <smaier@chromium.org>
> > Reviewed-by: agrieve <agrieve@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#605068}
> 
> Bug: 874854
> Change-Id: Idc95750d4465ca53b72db26a98ce74724fe21968
> Reviewed-on: https://chromium-review.googlesource.com/c/1318071
> Reviewed-by: Sam Maier <smaier@chromium.org>
> Commit-Queue: Sam Maier <smaier@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#605347}

TBR=agrieve@chromium.org,smaier@chromium.org

Change-Id: I4bb41ab999431fd2df511838d10db598cd5c0a87
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 874854
Reviewed-on: https://chromium-review.googlesource.com/c/1319333Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605586}

This patch also fixes the bug whereby Jaws wasn't announcing the visited state on a link.
We need to update the accessibility tree if there are any changes to the way a layout object is painted.
To be safe, we update the whole subtree.
The update needs to happen after the style change, not before, so as to catch any changes to the visited link state, color and font.
R=dmazzoni@chromium.org, aleventhal@chromium.org

Change-Id: I03f512a95f8101c603a712fb3d62e7b31a59da5e
Bug: 898706
Reviewed-on: https://chromium-review.googlesource.com/c/1298173
Commit-Queue: Nektarios Paisios <nektar@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605585}

Stop notifying events via old api and replace old API with new API.
This CL is a refactor and has no intended behavior change.

Bug: 842194
Change-Id: I5e11e7323940acbbdc31bd73d599480c7312e8b9
Reviewed-on: https://chromium-review.googlesource.com/c/1314508
Commit-Queue: Sang Woo Ko <sangwoo108@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605584}

The previous title has translation issue.

Bug: 897998
Change-Id: I59471c13de7c099bd8b7755d09c67d83e517f6b4
Reviewed-on: https://chromium-review.googlesource.com/c/1316835Reviewed-by: Evan Stade <estade@chromium.org>
Commit-Queue: Siyu An <siyua@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605583}

The fields ps, sid in chrome-proxy header are deprecated. So removing them.
https://g3doc.corp.google.com/wireless/speed/flywheel/g3doc/protocol/syntax_proxy.md#requests

Bug: 893728
Change-Id: I752938b6defd6e55405bd40151341ab50486c014
Reviewed-on: https://chromium-review.googlesource.com/c/1316677
Commit-Queue: rajendrant <rajendrant@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605582}

With this change, client initiated stream ID is 0, 2, 4..., and server initiated stream ID is 1, 3, 5... If client starts with v99, and server does not support v99, the version negotiation is not supported.

Merge internal change: 218572979

R=rch@chromium.org

Change-Id: I922820118ce229e1ae188a3c2d1a16cf3b34c2a6
Reviewed-on: https://chromium-review.googlesource.com/c/1318355
Commit-Queue: Fan Yang <fayang@chromium.org>
Reviewed-by: Ryan Hamilton <rch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605581}

- Merge TargetRegistry into DevToolsSession.
- Allow flatten children on any targets.

Bug: 775132
Change-Id: Idaafb019f9881a937f3e4b2d1abab7a3e89af06e
Reviewed-on: https://chromium-review.googlesource.com/c/1316748
Commit-Queue: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605580}

This reverts commit dc7a451a.

Reason for revert: Broke tests on Mac (at least): https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac10.12%20Tests/16499

Broken test output: https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8930653299367123984/+/steps/network_service_browser_tests_on_Intel_GPU_on_Mac_on_Mac-10.12.6/0/logs/SaveCardBubbleViewsFullFormBrowserTest.StrikeDatabase_Upload_AddStrikeIfSaveFails/0


Original change's description:
> Add StrikeDatabase browsertests
> 
> The tests in this CL have been landed and reverted a couple of times;
> they work, but end up being a little flaky on Win7. We've had a hard
> time getting a reproducible setup, and the Chrome testing team have
> verified our feature works as intended, so for the time being we're
> marking the tests as flaky on Windows and will follow up.
> 
> (Sheriffs: If somehow the landing of this CL causes additional
> flakes, feel free to revert. Flake analysis hasn't shown anything
> outside of Win7.)
> 
> Bug: 884817
> Change-Id: Iec545cb861bfc1aa3d50746c3a413257c9a9ec82
> Reviewed-on: https://chromium-review.googlesource.com/c/1316666
> Commit-Queue: Jared Saul <jsaul@google.com>
> Reviewed-by: Evan Stade <estade@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#605507}

TBR=estade@chromium.org,jsaul@google.com

Change-Id: I1e408b6395c80c425d982544bfdd88e01231db7b
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 884817
Reviewed-on: https://chromium-review.googlesource.com/c/1319190Reviewed-by: Dmitry Titov <dimich@chromium.org>
Commit-Queue: Dmitry Titov <dimich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605579}