GitLab

This CL renames LocalMouseInputMonitor to LocalPointerInputMonitor,
plumbs the event type (ET_MOUSE_MOVED or ET_TOUCH_MOVED) through to
the RemoteInputFilter, and adds touch input detection to ChromeOS.

Change-Id: I1adb94df5d56ec3194e7ccd81b870d2c8e73efa6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1590449
Commit-Queue: Joe Downing <joedow@chromium.org>
Reviewed-by: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656282}

- Adds new max width constant for cr-searchable-down to shared_vars_css.
- Update SmbShare page to use this new max width constant.
- This constant will be used in other dialogs in future CL's.

Bug: 955173
Test: End to End manual
Change-Id: Icc68ca995c1bf0d8df81f16c954e2ae5a202a5b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584845
Commit-Queue: jimmy gong <jimmyxgong@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Bailey Berro <baileyberro@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656281}

Use pageVisibility to hide:
* internet
* bluetooth
* device

Bug: 950007
Change-Id: I5fdfb525a33b19176d99bc6528bd060758fb2171
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1590604
Auto-Submit: James Cook <jamescook@chromium.org>
Commit-Queue: Dan Beam <dbeam@chromium.org>
Reviewed-by: Dan Beam <dbeam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656280}

Change-Id: I20db073d1b987abf5e4e4c43267f2cbae9e7a70a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1592619
Commit-Queue: Joe Downing <joedow@chromium.org>
Reviewed-by: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656279}

Ensures that the wrapper script for the XR browser tests properly exits
with the browser tests' return code. Previously, it was doing nothing
with the returncode, causing the tests to appear to always exit with 0.

Bug: 954581
Change-Id: Iede65178478980a7e1770df9c4b20a38f2efa3b0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1592616
Auto-Submit: Brian Sheedy <bsheedy@chromium.org>
Commit-Queue: Klaus Weidner <klausw@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656278}

ImmersiveContext remains as an interface in //ash/public.

Bug: 958248
Change-Id: Ie32c248e2683cf6957448b33436808394b551176
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1593836Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656277}

Bug: 841899
Tbr: thestig@chromium.org
Change-Id: I972785b8f6c189039c56049a8c132b7bf4c69876
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584531
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656276}

https://skia.googlesource.com/skia.git/+log/7fde8e172810..666a9f9f8bb9


git log 7fde8e172810..666a9f9f8bb9 --date=short --no-merges --format='%ad %ae %s'
2019-05-02 bungeman@google.com Update includes for Wuffs.
2019-05-02 bungeman@google.com IWYU for SkTLogic.h
2019-05-02 ethannicholas@google.com Child fragment processors are now written as separate functions
2019-05-02 skia-autoroll@skia-public.iam.gserviceaccount.com Roll skia/third_party/skcms 668026c511f3..853f66269c16 (2 commits)
2019-05-02 halcanary@google.com GMs: re-sort gni, script to regenerate gni, file name convention
2019-05-02 halcanary@google.com SkPaint:  new constructor
2019-05-02 herb@google.com SkShaper JSON output with cluster visualization


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

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

Change-Id: I420e09c36a614796d854398a1c7b319ad5194215
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1593596Reviewed-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@{#656275}

The part of the AshWindowManager mojom which was being used to preview
and perform snaps (click on restore button and drag to left or right)
is moved to a pure virtual interface in //ash/public/cpp, and
implemented in //ash/frame.

Bug: 958154
Change-Id: I1cb107784dfffe2209e27860d6735342913cc5d5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1592871
Auto-Submit: Evan Stade <estade@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656274}

This is mostly a revert of ddb9a768 and
08ebee42. It also deletes the tap visualizer
app.

You can test with --ash-touch-hud and ctrl-alt-i, or --show-taps.

Bug: 958074
Change-Id: I7282603e02588ad4d92fb51181565e203ee12f06
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1589830Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Auto-Submit: Evan Stade <estade@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656273}

All GPU test suites have been moved onto the new expectations
format. This CL also removes the generate_test_expectations.py
script which was used to generate test expectations file for a
test suite using the old test expectation python scripts. This CL
also removes the --also-run-disabled-tests command line argument.
This argument depended on the old format of expectations. The
--all command line argument can be used instead to run disabled
tests. It either by ignores the Skip expectation in the new format
or the --skip command line globs.

Bug: chromium:698902
Bug: chromium:937516
Change-Id: I5d866f0e2f21f2ada0ac94db45bf656ec11a9029
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1594057
Commit-Queue: Rakib Hasan <rmhasan@google.com>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656272}

Bug: 954797
Change-Id: Ibc4db91c4ea76b109a6361aa6c269e99cce8480d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1577674
Commit-Queue: John Williams <jrw@chromium.org>
Reviewed-by: Takumi Fujimoto <takumif@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656271}

Since we allow duration to be infinite, a seek to 2**64
(kInfiniteDuration) and a subsequent currentTime retrieval
will yield kInfiniteDuration.

BUG=958324

Change-Id: Ia7e2beead415cb3cfca91672f9399d6fd09a0d89
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1592614Reviewed-by: Dan Sanders <sandersd@chromium.org>
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656270}

Inline containing block dimensions were computed incorrectly if:
- inline OOF container was split
- OOF Element was inside non-root continuation

This happened because container dimensions were computed by
finding all fragments whose layout object root matched inline_container.
If inline container was not a root, no fragments were found.

Actual fix is simple: ensure that NGOutOfFlowPositionedDescendant
always points to the root.

While fixing this, I also did a little bit of cleanup. Main change was

- change NGOutOfFlowPositionedDescendant.inline_container to LayoutInline*
from LayoutObject*

Bug: 931867
Change-Id: Ibd3c0e9fdeffaf2c63d3f59386bc2ea223ec726b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1592528
Commit-Queue: Aleks Totic <atotic@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656269}

This was removed in the spec in 2016 (commit 16cd4c74, "Spec update"), and
there is no reason to keep it around at this point.

Bug: 257511, 957953
Change-Id: I3d0d6400ec529891266633fba0f86d7df67a32c9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1588637Reviewed-by: Robert Ma <robertma@chromium.org>
Reviewed-by: Colin Blundell <blundell@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Cr-Commit-Position: refs/heads/master@{#656268}

The fallback fonts logic in VR was used to detect that every glyphs
will exists when rendering.

see:
  https://bugs.chromium.org/p/chromium/issues/detail?id=722861

This is roughly a revert of:
  https://chromium-review.googlesource.com/c/chromium/src/+/1345419

The Android fallback fonts is implemented here:
  https://chromium-review.googlesource.com/c/chromium/src/+/1589274

R=billorr@chromium.org

BUG: 952963, 770893, 944227
Change-Id: Ia370f666369127f19bd7c950cbd32529e8927411
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1573652Reviewed-by: Etienne Bergeron <etienneb@chromium.org>
Reviewed-by: Bill Orr <billorr@chromium.org>
Commit-Queue: Etienne Bergeron <etienneb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656267}

Bug: 958769
Change-Id: I6001ac7307215bd947c21022d3cabc9bfbf37667
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1594082Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Pedro Amaral <amaralp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656266}

The tests started failing a while back; trying them locally they pass 100% of
the time. Re-enabling the tests and monitoring dashboard.

TBR=wjmaclean@chromium.org

Bug: 949683
Change-Id: Ib96a0562492372e2bc66e52fb2c65465beec84ef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1593641Reviewed-by: Ehsan Karamad <ekaramad@chromium.org>
Commit-Queue: Ehsan Karamad <ekaramad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656265}

When PlatformEventController is initialized, it takes a handle to the
current Document. In some navigation scenarios, the Document used to
initialize the PlatformEventController is short-lived and may be shut
down by the time the page has fully loaded. Attempting to use the
shut down Document can lead to errors.

NavigatorGamepad is a subclass of PlatformEventController. When
NavigatorGamepad is constructed with a short-lived Document, it fails
to properly initialize the PlatformEventDispatcher (GamepadDispatcher)
if it passes the (null) LocalFrame associated with the shut down
document.

This CL modifies PlatformEventController::AddController to take a
LocalFrame parameter to use instead of the frame associated with the
possibly-stale Document. NavigatorGamepad is modified to pass the
LocalFrame associated with the DOMWindow, which is not stale.

BUG=949320

Change-Id: Ied380362eb26add5ef0c23195a9ba93bebb5f348
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1552410
Commit-Queue: Matt Reynolds <mattreynolds@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656264}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/e2f2fee059f6..e207b5651204


git log e2f2fee059f6..e207b5651204 --date=short --no-merges --format='%ad %ae %s'
2019-05-02 manojgupta@google.com cros_fuzz: Update tool to handle msan.


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

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.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel
TBR=chrome-os-gardeners@chromium.org

Change-Id: I2e344312c761b14c411dedc119f76433986663a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1594092Reviewed-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@{#656263}

History navigations might have
|CommonNavigationParams::initiator_origin| that doesn't match spec
expectations (i.e. they might use an opaque origin, rather than the
original initiator origin).  This issue causes https://crbug.com/946503
and now apparently also causes https://crbug.com/958421.

This CL makes the following changes:

- It adds a regression test for the CORB issue caused by
  |request_initiator_site_lock| calculated based on the incorrect
  |CommonNavigationParams::initiator_origin|

- It fixes the CORB issue by reverting r635124, so that
  |request_initiator_site_lock| is based on the site URL (rather than on
  |CommonNavigationParams::initiator_origin|) for about:blank frames.

Bug: 958421, 918967, 888079
Change-Id: Ibec66ac8cf6d4fddf2ebe0e911e3b5922131a90b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1593793Reviewed-by: Charlie Reis <creis@chromium.org>
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Auto-Submit: Łukasz Anforowicz <lukasza@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656262}

In the current ScopesLockManager design, locks that were granted by
the release of other locks (the async use-case) were temporarily owned
by the task queue. This meant that even if you destructed all objects
that held locks, the lock system could still have locks being held by
SequencedTaskManager queue.

This change splits up the lock granting into two pieces, a lock
receiver and a closure which is called on lock granting. This allows
the lock to always be held by the client, and makes the interaction
between the lock system and system shutdowns / object destructions much
more predictable.

Doc:
https://docs.google.com/document/d/1jX6OOQJ0aLrWAeqYLtARXPFawUlJPbHNIKAK-0vmFHU/edit?pli=1#heading=h.upsvliozchjx

Bug: 862456
Change-Id: I0953c5f2025a3851750f7cdae621c4bf9326e645
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1590595
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656261}

new_tab.js was calling EncodeURIComponent on a full URL, only to have
CoreAppLauncherHandler call UnescapeURLComponent() on the URL, to get
the original result back. This is unnecessary, and not really correct,
since UnescapeURLComponent() leaves certain unsafe characters escaped.

This CL is part of an issue to clean up uses of UnescapeURLComponent(),
as it's been used for wildly disparate uses, and much of its logic is
only suitable for cases where we want to format a URL for safe display
to the user. We also want to make it leave more weird characters
escaped, but need to eliminate usage of it in other contexts before we
can do that.

Bug: 849998
Change-Id: I9c1aadecff32b1f5a592a6deb1ae73997a523b5f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1593453Reviewed-by: Dan Beam <dbeam@chromium.org>
Commit-Queue: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656260}

This removes the client of the mojom::AXHost interface. Future CLs
will remove the implementation.

This must land after the shortcut viewer moves back in-process,
otherwise it will break accessibility for that dialog.

Bug: 958187
Change-Id: Ib993fd7eb76e33fa4b93657e0ae280c123282eb2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1589669
Auto-Submit: James Cook <jamescook@chromium.org>
Reviewed-by: David Tseng <dtseng@chromium.org>
Reviewed-by: Toni Baržić <tbarzic@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656259}

Change-Id: Ic32a954422a0825392f76fa039dcff3e2c41890b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1594063
Commit-Queue: Ryan Hamilton <rch@chromium.org>
Commit-Queue: Zhongyi Shi <zhongyi@chromium.org>
Auto-Submit: Ryan Hamilton <rch@chromium.org>
Reviewed-by: Zhongyi Shi <zhongyi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656258}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/71ee4b946e64..719163224a6f


Created with:
  gclient setdep -r src-internal@719163224a6f

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.

CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome

BUG=chromium:920315
TBR=gogerald@chromium.org,caseq@chromium.org,ksakamoto@chromium.org,drott@chromium.org

Change-Id: Ib0a674f8fc964ae7e73dff09d305ba25776a4943
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1594094Reviewed-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@{#656257}

Use enum class instead of enum for ImageViewBase::Alignment
enum class is more type safety.

Bug: 940736
Change-Id: Ia5f7b5e8cb0d49ae070c85a861b878ce82e84c0f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1587578Reviewed-by: Peter Kasting <pkasting@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Hwanseung Lee <hs1217.lee@samsung.com>
Cr-Commit-Position: refs/heads/master@{#656256}

https://quiche.googlesource.com/quiche.git/+log/7bf7c3c358eb..97b690b069ce

$ git log 7bf7c3c35..97b690b06 --date=short --no-merges --format='%ad %ae %s'
2019-05-02 ianswett gfe-relnote: Close the connection if a STOP_WAITING frame is received in v44 or above.  Protected by gfe2_reloadable_flag_quic_do_not_accept_stop_waiting.
2019-05-02 fayang Remove the call to write padding when send probing data.

Created with:
  roll-dep src/net/third_party/quiche/src src/third_party/quic_trace/src

Change-Id: I6187b8ef0a5685858c019cf91691e089e4bd1ffc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1594087Reviewed-by: Ryan Hamilton <rch@chromium.org>
Commit-Queue: Bence Béky <bnc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656255}

Add missing 'const'. Also add a usage.

Change-Id: I26cb1cfb06d61d3ce272e3b661fddf0e556db9e0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1590878Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656254}

Changelog: https://github.com/googlechrome/lighthouse/compare/v4.3.0...v4.3.1

Bug: 772558, 958952
Change-Id: If37fc2b10b1100b35ae236f719e20255efad50c9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1593542Reviewed-by: Erik Luo <luoe@chromium.org>
Reviewed-by: Paul Irish <paulirish@chromium.org>
Commit-Queue: Connor Clark <cjamcl@google.com>
Cr-Commit-Position: refs/heads/master@{#656253}

This function is outdated after MediaDrmStorageImpl change [1]. It's not
breaking bots because USE_CHROMECAST_CDMS is true by default on Android,
which could be a bug on its own.

[1] https://chromium-review.googlesource.com/c/chromium/src/+/1416398

Bug: 917527
Change-Id: I7effd079c9a1ff33ee0cc91a2130a1361cb99c3c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1592229Reviewed-by: John Rummell <jrummell@chromium.org>
Reviewed-by: Yuchen Liu <yucliu@chromium.org>
Commit-Queue: Xiaohan Wang <xhwang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656252}

This changes contains three functional differences:

1) Overscroll by 24dp when a new element is focused. This is done by
overriding requestChildRectangleOnScreen in our custom LayoutManager
and adding 24dp to the bounds of the focus rect.

2) Added 24dp of whitespace after the More articles button to match
mocks. This allows the overscroll to take effect instead of running out
of space to scroll.

3) Focusing any element in the above the fold view now scrolls all the
way to the top of the above the fold section.

Bug: 952344
Change-Id: I15fc0d58dbb7bbe45c77fdf213d07979afac1214
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1594152Reviewed-by: Brandon Wylie <wylieb@chromium.org>
Commit-Queue: Sky Malice <skym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656251}

This adds chart GEM objects number and size to memory diagram.

TEST=Locally + limited unit tests
BUG=b:122555793

Change-Id: I902c65a016f89041e69ab202f6344eff9838a9dd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1592709Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Yury Khmel <khmel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656250}

There are still two cases that check NavigationDisablerForBeforeUnload,
add LocalFrame::IsNavigationAllowed() there as needed.

Change-Id: I34b6456818a3a440c9b63432b6491278ac4581e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1588520
Commit-Queue: Nate Chapin <japhet@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656249}

In preparation for adding PartitionAlloc support to GWP-ASan, rename the
current sampling "allocator shims" to more specifically be the malloc
shims.

Bug: 956824
Change-Id: I05ab7a556063d1cd0966ab40474720299caf0f76
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1593838Reviewed-by: Vitaly Buka <vitalybuka@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Robert Sesek <rsesek@chromium.org>
Auto-Submit: Vlad Tsyrklevich <vtsyrklevich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656248}

Causes BuildConfig.java to be generated with a flag
"ENABLE_OFFLINE_PAGES" when build variable "enable_offline_pages" is
set to true. This is in preparation for disabling Offline Pages on
touchless mobile devices.

Bug: 955642
Change-Id: Ifef81f750e7f09e8d3f9a942476c6bf47f8a5d3b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1591477Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Ian Wells <iwells@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656247}

Currently FCP++ explicitly ignores the cases where opacity:0, but this is not
neccesary. This is because the paint pipeline has already ignore the case
where opacity == 0. If an element has opacity:0, the FCP++ wouldn't even be
notified of this element. As it's unnecessary, FCP++ should remove the opacity
check.

In additon to this fix. we also add test cases for visiblity:hidden,
display:none and opacity:0.01. There are to make sure they are automatically
excluded from feeding the FCP++ paint hooks.

Bug: 957674
Change-Id: If9e87f0f1544732cf7ac16b5c9dd497da19ea8a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1594053Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656246}

This CL is part of an issue to clean up uses of UnescapeURLComponent(),
as it's been used for wildly disparate uses, and much of its logic is
only suitable for cases where we want to format a URL for safe display
to the user. We also want to make it leave more weird characters
escaped, but need to eliminate usage of it in other contexts before we
can do that.

Bug: 849998
Change-Id: I72cfeab6a5ad734d41549b288ef37e0814369961
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1592704Reviewed-by: Sorin Jianu <sorin@chromium.org>
Commit-Queue: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656245}

https://swiftshader.googlesource.com/SwiftShader.git/+log/1c462b340845..c57ec6f0af33


git log 1c462b340845..c57ec6f0af33 --date=short --no-merges --format='%ad %ae %s'
2019-05-02 chrisforbes@google.com Add support for sampling VK_FORMAT_B10G11R11_UFLOAT_PACK32
2019-05-02 chrisforbes@google.com Add support for sampling VK_FORMAT_D32_SFLOAT (without depth compare)


Created with:
  gclient setdep -r src/third_party/swiftshader@c57ec6f0af33

The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-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: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

BUG=chromium:b/131246807,chromium:b/131246807
TBR=swiftshader-team+autoroll@chromium.org

Change-Id: Ib6759852cddcb21f18dc9abcda2fee6bab72787f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1593594Reviewed-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@{#656244}

before the recycler view was attached to the screen.

Bug: 958924
Change-Id: Iee206f691ab307a04ddac6896ba2f4f37dcbb00b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1593834
Auto-Submit: Cathy Li <chili@chromium.org>
Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Commit-Queue: Sky Malice <skym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656243}