GitLab

Use WaitForMultiprocessTestChildExit() instead of
base::Process::WaitForExitWithTimeout() to wait for multiprocess test
child processes to complete. It's identical to WaitForExitWithTimeout()
on macOS/Windows/Linux but also works on Android. (Android tests don't
fork so they use a special process monitoring mechanism.)

Bug: 973167
Change-Id: I3c3f10a155d4ea9058404ae7474cfacdcf2ed402
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1668335
Auto-Submit: Vlad Tsyrklevich <vtsyrklevich@chromium.org>
Commit-Queue: Vitaly Buka <vitalybuka@chromium.org>
Reviewed-by: Vitaly Buka <vitalybuka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671908}

This CL:
 - removes perfetto_unittests entirely, because it isn't running on any
   other android bot
 - adds android+asan-specific filters for content_browsertests and
   unit_tests

Bug: 790202
Change-Id: I361069217c4c52a49e48a8e53c23bb238f495879
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1674592
Commit-Queue: John Budorick <jbudorick@chromium.org>
Commit-Queue: Stephen Martinis <martiniss@chromium.org>
Auto-Submit: John Budorick <jbudorick@chromium.org>
Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671907}

InstallWebAppWithOptions shouldn't dcheck
AreWebAppsUserInstallable.

Remove DCHECKs from WebAppInstallManager:
Let WebAppInstallTask only DCHECKs it (WebAppInstallTask is a leaf node
and it is used by WebAppInstallManager anyway).

In general, this is go/chromium-profile-types again.

Bug: 977823
Change-Id: I1c5f0cfcef363cad9cfdd92e69decd64022f707e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1672091Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Commit-Queue: Alexey Baskakov <loyso@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671906}

This reverts commit 3bceb8a7.

Reason for revert:

Seems to have broken
IndexedDBBrowserTest.NegativeDBDataVersion
IndexedDBBrowserTest.NegativeDBSchemaVersion

On various bots:
https://ci.chromium.org/p/chromium/builders/ci/KitKat%20Phone%20Tester%20%28dbg%29/14978
https://ci.chromium.org/p/chromium/builders/ci/Mac%20ASan%2064%20Tests%20%281%29/54305

Original change's description:
> [IndexedDB] Open sequence cleaned up with better failure handling.
> 
> The previous open sequence was really hard to understand and only
> sometimes recovered the database. This change cleans this up. See the
> document here for more info:
> https://docs.google.com/document/d/1jX6OOQJ0aLrWAeqYLtARXPFawUlJPbHNIKAK-0vmFHU/edit#heading=h.5qhp88d21pi0
> 
> Bug: 862456
> Change-Id: Ib8fa4e48c0154451e8ab787bc0086a57759f05d0
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1665433
> Commit-Queue: Daniel Murphy <dmurph@chromium.org>
> Reviewed-by: Victor Costan <pwnall@chromium.org>
> Reviewed-by: Chase Phillips <cmp@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#671765}

TBR=cmp@chromium.org,dmurph@chromium.org,pwnall@chromium.org

Change-Id: I9e851fce26bd9feb351c76bec8e418cbd09799a0
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 862456
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1674623Reviewed-by: Dan Beam <dbeam@chromium.org>
Commit-Queue: Dan Beam <dbeam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671905}

In content::NavigationControllerImpl::NavigateFromFrameProxy we pull
RenderFrameHost::FrameTreeNode out into a separate variable but rarely
use it. This CL uses the variable in locations were we previously
computed its value.

Bug: N/A
Change-Id: Ic5ef6e209b2c5146d7d62a8b884d61c150c1100a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1673172Reviewed-by: Nasko Oskov <nasko@chromium.org>
Commit-Queue: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671904}

Added flag for new Switch Access text input improvements that will
be made.

Bug:978232

Change-Id: I97c2349fb28f3651f74bf9eaa3646d3c168bfa34
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1674471
Commit-Queue: Rose Garcia <rosalindag@google.com>
Reviewed-by: Katie Dektar <katie@chromium.org>
Reviewed-by: Anastasia Helfinstein <anastasi@google.com>
Cr-Commit-Position: refs/heads/master@{#671903}

Cursor should be set to 'default' instead of 'none'.

Bug: 977948
Change-Id: I2d4619f26bd33524718c1d3993fc6162fa2a3485
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1674410
Commit-Queue: Kyle Milka <kmilka@chromium.org>
Commit-Queue: Kristi Park <kristipark@chromium.org>
Auto-Submit: Kyle Milka <kmilka@chromium.org>
Reviewed-by: Kristi Park <kristipark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671902}

Replace with an observer interface on FullscreenController.

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

No change to logic, only docs.

This adds an explainer for class verification (focusing on ART), and
tips for debugging class verification errors, including
list_class_verification_failures.py.

Bug: 918221, 855796
Test: tools/md_browser/md_browser.py
Test: Upload to gerrit > open file > click "gitiles"
Change-Id: I28c0e5fb337fe0f126106b6e5bc6a5001ce24167
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1663589Reviewed-by: Changwan Ryu <changwan@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671900}

Changes the detection mechanism for the ToolbarIconContainerView
highlight border so that it is active when either:

* The container is mouse hovered but the main view is not.
* Any child view has focus.
* Any child view is in the pressed state.

Bug: chromium:932818, chromium:943702
Change-Id: I388a4b78a43ddd05b3dd2623321f92938110ba0f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1674629Reviewed-by: Siyu An <siyua@chromium.org>
Commit-Queue: Peter Boström <pbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671899}

Verifies the following behavior for WebXR Gamepads:
1) Changes to the button and input axis values for the mock gamepad
   object make their way through all the plumbing and on to the session's
   input source's Gamepad.
2) Changing button and input axis values cause the Gamepad to be updated
   in-place. XRInputSource and Gamepad objects should not be re-created
   in this case and an inputsourceschange event should not be fired.

Bug: 976978
Change-Id: I6de7a45e357e6900eccca103741dddc33fc9d495
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1673083Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Commit-Queue: Jacob DeWitt <jacde@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671898}

https://skia.googlesource.com/skia.git/+log/91032f8cd7ea..e2439cc929f9


git log 91032f8cd7ea..e2439cc929f9 --date=short --no-merges --format='%ad %ae %s'
2019-06-24 rmistry@google.com Add to lottieweb blacklist
2019-06-24 rmistry@google.com Do not retry G3 tryjobs
2019-06-24 nigeltao@google.com Pause Wuffs' getFrameCount in incremental decode
2019-06-24 jvanverth@google.com Reland "Prefer using GrOvalOpFactory over GrFillRRect for circles and axis-aligned circular roundrects."
2019-06-24 bsalomon@google.com Fix GrColorType name for half float RG.
2019-06-24 egdaniel@google.com Add defaults for GrProtected on createBackendTexture.
2019-06-24 csmartdalton@google.com Rename "preferredInternalSampleCount" to "internalMultisampleCount"
2019-06-24 herb@google.com Remove getGlyphIDMatrics type calls.
2019-06-24 rmistry@google.com [lottie-web-perf] Make similar to skottie-wasm-perf
2019-06-24 rmistry@google.com [skottie-wasm-perf] Make sure we are drawing to 1000x1000
2019-06-24 bsalomon@google.com Fix EGLImageTest asserts on Android
2019-06-24 robertphillips@google.com Reduce GrCaps' reliance on GrPixelConfig
2019-06-24 brianosman@google.com Install runtime check error handler in RTC builds
2019-06-24 bsalomon@google.com GrColorSpaceInfo stores SkAlphaType.
2019-06-24 halcanary@google.com experimental/editor: progress on newlines
2019-06-24 benjaminwagner@google.com Shuffle jobs to the NVIDIA_Shield (2 of 2)
2019-06-24 mtklein@google.com fix Dockerfile?
2019-06-24 mtklein@google.com add bit_clear
2019-06-24 fmalita@chromium.org [skottie] Run resources "GMs" on Lottie bots
2019-06-24 emircan@google.com Enable creating protected vulkan backend
2019-06-24 mtklein@google.com split out Analysis struct from Instruction
2019-06-24 mtklein@google.com embed val_to_reg in Builder::Instruction
2019-06-24 mtklein@google.com refactor to remove the need for death schedule
2019-06-24 mtklein@google.com split ID -> Reg,Val
2019-06-24 mtklein@google.com simplify instructions back to one immediate
2019-06-24 benjaminwagner@google.com Shuffle jobs to the NVIDIA_Shield (1 of 2)
2019-06-24 brianosman@google.com Particles: SkScalar -> float


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

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

BUG=chromium:971936
TBR=djsollen@google.com

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

Bug: none
Change-Id: I3636b34d6f87f9db732f1263cc3f2eddeb39335f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1670527Reviewed-by: Dan Sanders <sandersd@chromium.org>
Reviewed-by: Chrome Cunningham <chcunningham@chromium.org>
Commit-Queue: Chrome Cunningham <chcunningham@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671896}

We weren't freeing some objects that wayland allocates (and expects us
to free for ourselves).

Bug: 977600
Change-Id: I6e5441e92ec5e951d3e3ad3b9c431a7b3690d60c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1672078Reviewed-by: Joel Hockey <joelhockey@chromium.org>
Commit-Queue: Nic Hollingum <hollingum@google.com>
Cr-Commit-Position: refs/heads/master@{#671895}

Previously, we had two copies of each Record, Train, and Rank method for
the ranker and each predictor: one that took a query and one that didn't.
The idea was that predictors (and therefore the ranker) was set up to
either work in a zero-state or condition-based environment, and clients
should only call the appropriate methods.

This has limitations, in particular, zero-state predictors can't be used
in an ensemble model along with condition-based ones. This CL removes
the distinction between these methods.

Specific changes are as follows:

1. Predictors now only have Train(target, condition) and
   Rank(condition) methods. The non-condition versions have been
   deleted.

2. The Ranker's zero-state Train and Rank methods are now just
   shortcuts for having an empty-string condition.

3. All predictors labelled ZeroStateX have been renamed to just X. It
   seems most of our predictors won't use the condition and, in order
   to incorporate a condition, will be wrapped in some kind of
   ConditionalPredictor. So it makes sense for the default naming to not
   specify zero-state-ness, as the current names are very verbose.

Bug: 921444
Change-Id: I5273715501319cda951b717d755e1abb559d4dd6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1670668
Commit-Queue: Tony Yeoman <tby@chromium.org>
Reviewed-by: Charles . <charleszhao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671894}

Now system logs from the target system (running under qemu) are stored in a separate
file in the output directory. A separate CL will remove these logs from tests stdout.

Bug: 869753
Change-Id: Ife0993605add5f0eb2e1422879e7df0fedabb31b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1674667
Auto-Submit: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671893}

Making sure there are at least 2 owners after I leave.
This CL was uploaded by git cl split.

R=dnicoara@chromium.org

Change-Id: Ib08fe6f8c354dbd7f9dc6c3c91caa693a493579a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1674611
Auto-Submit: Antoine Labour <piman@chromium.org>
Commit-Queue: Daniele Castagna <dcastagna@chromium.org>
Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671892}

There are paths in the layout code where layout of the children of
an element is done even when NormalChildNeedsLayout/PosChildNeedsLayout
aren't dirty, and display locked elements fail in those cases because
we remove the self-dirty layout bits with the assumption that the
child dirty bits will be there and will be restored in future
updates/unlocks.

This CL adds notifications of blocked child layouts, so the next time
the subtree is allowed to be updated we can make sure those blocked
child traversals will happen, even if NeedsLayout() is false on the
locked element.

Bug: 966458
Change-Id: I12f2f82af475243ca2dcf91df643294332e20e2f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1652892Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: vmpstr <vmpstr@chromium.org>
Commit-Queue: Rakina Zata Amni <rakina@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671891}

This changes traversal to use a 'selection' similar to omnibox
that is wholly managed by a single object.
This change is currently behind a flag, and will be default-on
in a follow up CL by June 25th

Bug: 931909
Change-Id: I828605ca77a87829eded327ab8a6198097450ecf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1607502
Commit-Queue: Kevin Strohbehn <ginko@google.com>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671890}

https://chromium.googlesource.com/external/github.com/material-components/material-components-ios/+log/e90aa11c4be3..dc0267693ad4


git log e90aa11c4be3..dc0267693ad4 --date=short --no-merges --format='%ad %ae %s'
2019-06-24 codyleeweaver@gmail.com Merge branch 'release-candidate' into stable


Created with:
  gclient setdep -r src/ios/third_party/material_components_ios/src@dc0267693ad4

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

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:ios-internal-mdc
TBR=bling-p10-rolls@google.com

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

This CL is a part of moving access token management to
OAuth2AccessTokenManager.

It moves RequestParameters to OAuth2AccessTokenManager and
TokenCache type definition which uses RequestParameters
also is moved.

Bug: 967598
Change-Id: I62d268f634c91caf61d792110206f5a01751f006
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1670132
Commit-Queue: Julie Jeongeun Kim <jkim@igalia.com>
Reviewed-by: Colin Blundell <blundell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671888}

This reverts commit b916e68c.

Bug: 977019

Original change's description:
> Enable feedback from power button menu in KioskNext sessions
>
>  Bug: 967931
>
> Change-Id: I302a4eb12ff69c117c0254fdc86d1a2323231180
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1647454
> Reviewed-by: James Cook <jamescook@chromium.org>
> Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
> Commit-Queue: Yilkal Abe <yilkal@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#667308}

TBR=jamescook@chromium.org,michaelpg@chromium.org,yilkal@chromium.org

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

Bug: 967931
Change-Id: I279992966d55b8ba140f488bbac798efb515f11f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1674189Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Yilkal Abe <yilkal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671887}

Bug: 956419
Change-Id: I6f769800f1deb20461d4148b28d4b03d23310de2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1657355
Commit-Queue: Peter Kasting <pkasting@chromium.org>
Reviewed-by: Mohamed Amir Yosef <mamir@chromium.org>
Reviewed-by: Trent Apted <tapted@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Christian Dullweber <dullweber@chromium.org>
Reviewed-by: Olivier Robin <olivierrobin@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Reviewed-by: Peter Lee <pkl@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Reviewed-by: Eric Noyau <noyau@chromium.org>
Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671886}

Because Linux/CrOS do not respect hit test transparency, the top shadow
of bubbles fights for mouse events with the window underneath. This
causes unacceptable flicker with tab hover cards on Linux and ChromeOS.

As a temporary fix until the real culprit can be addressed (a much
larger effort; see crbug/978134), on the affected platforms we move
hover cards down slightly and slightly raise the bottom of the hit test
area for tabs up slightly to compensate. This is not ideal from a UX
standpoint but it is the only solution available at the current time for
an issue that is otherwise a release blocker.

Bug: 972582
Change-Id: I91f0583f8c6c4dfb912c4ea75e07a437fc770f02
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1674290
Commit-Queue: Dana Fried <dfried@chromium.org>
Reviewed-by: Caroline Rising <corising@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671885}

The function "AddItem" add invisible empty menu for extension overflow menu.
It might be workaround to resolve appkit menus bug. But, it might be resolve.
The empty menu added before extension overflow menu is invisible, but
it has margins. So, the exetension overflow menu view in AppMenu looks
different in Windows and Mac.

Bug: NONE
Change-Id: Iba0b944f688b42a42d2e83716209770acae689e8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1669136Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Sangseok Jang <sangseok.jang@navercorp.com>
Cr-Commit-Position: refs/heads/master@{#671884}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/e3905cd79dbe..754e19056745


Created with:
  gclient setdep -r src-internal@754e19056745

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
TBR=tzik@google.com,dbeam@google.com,huanzhong@google.com

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

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

This reverts commit e2af10b0.

Reason for revert: Seems to be causing crashes in https://crbug.com/977956.

Original change's description:
> Fix Android NTP kills by disallowing NTP process reuse before processing the NTP commit.
> 
> SiteInstance supports a class of "siteless" URLs that represent blank
> or placeholder documents, which normally do not "use up" their process
> (by leaving their site URL unassigned) and allow subsequent
> navigations to stay within the same process.  Currently, these URLs
> include "about:blank" as well as chrome-native://newtab on Android
> (used as a placeholder when loading the native NTP to warm up the
> process for a subsequent navigation).
> 
> Unfortunately, with Android NTP, a race is possible where the NTP
> placeholder process is told to commit chrome-native://newtab, but
> before we hear back the DidCommitProvisionalLoad IPC for
> chrome-native://newtab, a subsequent navigation to foo.com starts,
> reaches the ReadyToCommit stage, and locks the NTP process to foo.com.
> When the chrome-native://newtab commit is processed, we kill the
> renderer, since the foo.com process lock is not compatible with
> chrome-native://newtab.
> 
> To fix this, this CL disallows reusing a process during the narrow
> window of time when it has a pending commit to a siteless URL like
> chrome-native://newtab (i.e., after CommitNavigation is sent, but
> before DidCommitProvisionalLoad is received).  It's still fine to
> reuse the NTP process post-commit, which is expected to be the common
> case that requires the process reuse optimization.
> 
> Bug: 970046
> Change-Id: I82c4fa964e3b0cc5ed400b7da9981573f7873d86
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1661271
> Reviewed-by: Steven Holte <holte@chromium.org>
> Reviewed-by: Charlie Reis <creis@chromium.org>
> Commit-Queue: Alex Moshchuk <alexmos@chromium.org>
> Auto-Submit: Alex Moshchuk <alexmos@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#670618}

TBR=creis@chromium.org,alexmos@chromium.org,holte@chromium.org

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

Bug: 970046
Change-Id: I957374edd66badbc0f1c4f33514e26d78713efbe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1674620Reviewed-by: Charlie Reis <creis@chromium.org>
Commit-Queue: Charlie Reis <creis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671881}

Because border thickness changes the default result of calling

contents of a view that has had its border changed must be re-laid-out.

View: :GetInsets() and by extension View::GetContentsBounds(), the
Change-Id: I42b9c95b72162d8bc4ca26d283062d6f154c021e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1669655
Commit-Queue: Dana Fried <dfried@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671880}

The overview selector is newer, so the window cycle selector should be
updated to match it. Instead of using LayerFillBackgroundPainter, we'll
opt to use setters for the layers more directly like with overview.

R=afakhry@chromium.org, sammiequon@chromium.org

Bug: 974050
Test: manual

Change-Id: I86721cdb8a75daaabac2337a5b27ebc6b53102c0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1670288Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Sammie Quon <sammiequon@chromium.org>
Commit-Queue: Danton Vu <dantonvu@google.com>
Cr-Commit-Position: refs/heads/master@{#671879}

Adds Allowed/Committed PreviewsState -> PreviewType support in
PreviewsContentUtil for DeferAllScript preview. It is prioritized
at this level above ResourceLoadingHints and NoScript since they are
supported on older clients and also assuming it is a better option
if supported by the client. The optimization guide logic may affect
priority separately as well.

Bug: 965277
Change-Id: I27b24ad4076f9b424cc9c5041e2d7a36027b12f9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1669983
Commit-Queue: Doug Arnett <dougarnett@chromium.org>
Reviewed-by: Robert Ogden <robertogden@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671878}

BUG=965657

Change-Id: Ie596ccf2b97c071b4039b643393c0391bf322c6c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1673757
Auto-Submit: May Lippert <maybelle@chromium.org>
Reviewed-by: Zachary Kuznia <zork@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Commit-Queue: May Lippert <maybelle@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671877}

https://chromium.googlesource.com/chromiumos/platform2/system_api.git/+log/ed5a30c1446a..33a144a0bdb9

$ git log ed5a30c14..33a144a0b --date=short --no-merges --format='%ad %ae %s'
2019-05-02 apotapchuk cryptohome: Adding calls for obtaining RSUDeviceID
2019-06-14 ljusten kerberos: Implement option to use login password
2019-06-06 ljusten Kerberos: Handle bad configuration
2019-05-20 khegde diagnostics: Add some telemetry battery metrics

Created with:
  roll-dep src/third_party/cros_system_api

BUG=chromium:952240
TEST=None

Change-Id: I5a26fba9aea6096ff6e7794140d1b7a8104df12d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1674547Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Commit-Queue: Lutz Justen <ljusten@chromium.org>
Auto-Submit: Lutz Justen <ljusten@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671876}

Bug: 976402
Change-Id: Icef1bce64612e489c575d4ede2d892d76383b529
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1669990
Commit-Queue: Shakti Sahu <shaktisahu@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671875}

This reverts commit 9a315e8e.

Reason for revert: https://crbug.com/978199: hook would appear to break the tab capture tests.

Original change's description:
> Hook up the delay load failure function in the renderer processes (Take 2)
> 
> (reland of
> https://chromium-review.googlesource.com/c/chromium/src/+/1655909 with
> the code living in a different compiland).
> 
> The problem with the previous CL was that renderer_main_platform_delegate_win.cc
> is linked into browser_tests.exe, which caused the hook to be used by the browser
> code.
> 
> I've verified this change by checking out the 3814, applying the fix to it and
> navigating to  https://opensource.salesforce.com/ to confirm that this was
> generating a crash report.
> 
> -------- Original CL description -------------
> 
> This allows getting a crash report when failing to delay load a DLL.
> 
> Example of the stack trace that this will provide:
> chrome_child!base::debug::BreakDebugger+0xc [C:\src\chrome\src\base\debug\debugger_win.cc @ 28]
> chrome_child!logging::LogMessage::~LogMessage+0x3f5 [C:\src\chrome\src\base\logging.cc @ 939]
> chrome_child!DllLoadHook+0x75 [C:\src\chrome\src\chrome\child\delay_load_failure_hook.cc @ 24]
> chrome_child!__delayLoadHelper2+0x13f [d:\agent\_work\3\s\src\vctools\delayimp\delayhlp.cpp @ 305]
> chrome_child!RtlUnwind+0x470
> chrome_child!SkFontMgr::legacyMakeTypeface+0x13 [C:\src\chrome\src\third_party\skia\src\core\SkFontMgr.cpp @ 164]
> chrome_child!blink::DWriteVersionSupportsVariations+0x7f
> chrome_child!blink::WebFontTypefaceFactory::FontManagerForVariations+0xc
> 
> 
> Bug: 970893, 976241
> Change-Id: Ifeb5e79ee141c5eb121e379ff928a9c3d941e71c
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1665913
> Reviewed-by: Will Harris <wfh@chromium.org>
> Reviewed-by: Scott Violet <sky@chromium.org>
> Auto-Submit: Sébastien Marchand <sebmarchand@chromium.org>
> Commit-Queue: Scott Violet <sky@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#670968}

TBR=sky@chromium.org,wfh@chromium.org,sebmarchand@chromium.org

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

Bug: 970893, 976241
Change-Id: I08cf199c5ad21966530f0a325c2f5097786d5882
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1674610Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Reviewed-by: Will Harris <wfh@chromium.org>
Commit-Queue: Robert Kroeger <rjkroege@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671874}

They are unused after GpuVideoDecoder removal.

Bug: 882542
Change-Id: Ic5e64f2b30b8a32be7a4f9209d5aebe007f439f1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1674474
Auto-Submit: Antoine Labour <piman@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Commit-Queue: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671873}

Bug: 977520
Test: http/tests/navigation/xmhtml-location-change-crash.xhtml
Change-Id: Idbb8718db7de77ddf41dbc62bd102e884d0bfa12
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1674364
Commit-Queue: Nate Chapin <japhet@chromium.org>
Auto-Submit: Nate Chapin <japhet@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671872}

Migrat the Site Settings preference fragment from the deprecated
framework preferences to the support library preferences.

Bug: 968592
Change-Id: I127b24977adf8f4091769131f6f554484b149317
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1668628
Commit-Queue: Natalie Chouinard <chouinard@chromium.org>
Reviewed-by: Finnur Thorarinsson <finnur@chromium.org>
Reviewed-by: Becky Zhou <huayinz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671871}

This CL adds another test which has flaked to the filter.

Bug: 977669
Change-Id: I740871a457227a21a75834d02fe1da7afd527096
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1674632
Commit-Queue: Jonathan Ross <jonross@chromium.org>
Reviewed-by: Jonathan Ross <jonross@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671870}

This change updates the SMS formatting to use "To:" instead of
"From:"[1]. This seems more appropriate because there isn't any
guarantee that it is actually going to be coming from
what the address states. The intent is to direct a message
"to" an origin, independently of "where/from" it is coming from.

[1] https://github.com/samuelgoto/sms-receiver#formatting

Bug: 976346
Change-Id: Iaf1358661b45a5a2066f4d8c3eac2bc294c10511
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1669985Reviewed-by: Jun Cai <juncai@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Ayu Ishii <ayui@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671869}