GitLab

This has thread safety issues, reverting to reland a fixed version.

This reverts commit 0f70801a.

Reason for revert: <INSERT REASONING HERE>

Original change's description:
> [Cros SR] Reflect user history deletion actions in the model.
> 
> We have an on-device model ranking commonly used URLs in the CrOS
> launcher, which stores these URLs in the model itself. This CL
> observes the history service and deletes URLs from the model that
> are removed by the user.
> 
> Bug: 931149
> Change-Id: If9e9654a00ae804807319a3dc5dc91b599698c7c
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1725032
> Commit-Queue: Tony Yeoman <tby@chromium.org>
> Reviewed-by: Jia Meng <jiameng@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#683049}

TBR=jiameng@chromium.org,tby@chromium.org

Change-Id: Iadd8433895f16fb3c9e3a4d5f9b2a53869612ab3
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 931149
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731990Reviewed-by: Tony Yeoman <tby@chromium.org>
Commit-Queue: Tony Yeoman <tby@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683398}

Gesture navigation on rendered pages opened via 'open in a new tab'
was not working due to a bug in the logic determining the activation
of its UI. This CL fixes the bug by having it use the same logic
used by native pages.

Bug: 989729

Change-Id: Ifdf6df5fa4ec5a7ce592167d16c5c63434c27b94
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1728535Reviewed-by: Theresa  <twellington@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683397}

CollectedCookiesViews::CreateAndShowForWebContents may be called
while an existing dialog (widget) is in the process of closing. In
this case, exit gracefully instead of crashing.

The only way I can think of that might be possible to repro this
IRL (i.e. aside from clusterfuzz) would be to:
a) open page info bubble
b) click "cookies"
c) open page info bubble again
d) click "cookies", then focus cookies dialog, press escape,
   all in rapid succession
e) cookies dialog starts closing
f) click on "cookies" is a posted task, and is handled after
   cookies dialog starts closing, but before finishing closing

This is probably exceedingly rare, enough so that it's not worth
being concerned with re-opening the cookies dialog. (And arguably,
it shouldn't re-open anyway, since the last command the user issued
was "escape" (close).)

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

Bug: 978109
Change-Id: Ie59d4d378da2476d9e78fc20f5a6a8e5929e55f2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731763
Commit-Queue: Charlene Yan <cyan@chromium.org>
Commit-Queue: Bret Sepulveda <bsep@chromium.org>
Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683395}

Context: These features hard-code in Chrome that Elo and JCB cards are
unsupported for upload save to Google Payments. In M75, the
AutofillDoNotUploadSaveUnsupportedCards study (Project Passport Control)
does the same thing but dynamically via a Payments RPC and for more card
types. Thus, these features can finally go away (M69-M74).

Note that this CL is essentially a reversal of the original one:
https://chromium-review.googlesource.com/c/chromium/src/+/1153301

Bug: 868552, 902366
Change-Id: I820a110afb83002151e726ae539097104e6ae45f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717490Reviewed-by: Maxim Kolosovskiy <kolos@chromium.org>
Reviewed-by: Brian White <bcwhite@chromium.org>
Commit-Queue: Jared Saul <jsaul@google.com>
Cr-Commit-Position: refs/heads/master@{#683394}

`delivery_value` can be None.

Generated files will be updated after some more changes, not now.

Bug: 906850
Change-Id: Ia40b1cb4a75d14384092fb1fb84c51df8411ef15
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1723012
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683393}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/447b45d42307..24146be8336f

git log 447b45d42307..24146be8336f --date=short --no-merges --format='%ad %ae %s'
2019-08-01 ehmaldonado@chromium.org depot_tools: Simplify CheckCallAndFilter[AndHeader]

Created with:
  gclient setdep -r src/third_party/depot_tools@24146be8336f

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

Bug: chromium:984182
Change-Id: If6530ac3c6647eb6e452bc719e787eb6bc7cf246
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731760Reviewed-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@{#683392}

This CL moves the inline script CSP check from
PendingScript::ExecuteScriptBlock() (#execute-the-script-block)
to ScriptLoader::PrepareScript() (#prepare-a-script)
as spec'ed.

This CL removes Script::InlineSourceTextForCSP()
which is no longer used.

Behavior changes (the new behavior is spec-conformant and thus
this CL adds WPT tests):

- Previously <script>'s error events were fired
  when inline script CSP check fails,
  while after this CL the events are no longer fired.
  Test: scripthash-basic-blocked-error-event.html
  (Moved from layout test with expectation changes)

  This CL makes Chromium's behavior align with Firefox and Safari.

- If the nonce attribute is changed or the CSP list is updated
  after prepare-a-script before evaluation,
  previously the new nonce/CSP were used for CSP,
  while after this CL the old nonce/CSP
  (at the time of prepare-a-script) is used.
  Test: scriptnonce-changed-*.html

  This CL makes Chromium's behavior align with Firefox.
  (Safari's behavior is different from any other browsers)

This CL also adds scripthash-changed-*.html (just for symmetry
with scriptnonce-changed.html), which pass only on Chromium.

Bug: 964537
Change-Id: I8673956101d9d13708c452db23258f125cb3d256
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1618262
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683391}

This removes ChildProcessLauncher's nominal dependency on BrowserThread
initialization by capturing the client's current SequencedTaskRunner
rather than the current thread's BrowserThread::ID, which may not be
initialized yet.

Bug: 989769
Change-Id: Ia4b9cb0781540f6737be761c201b6440f7713ac6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731473Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Clark DuVall <cduvall@chromium.org>
Commit-Queue: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#683390}

Bug: 984550
Change-Id: I8d94c4267bb1730765e247d4841cad3ac7622a2f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1728268
Commit-Queue: Lucas Gadani <lfg@chromium.org>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683389}

It's WebAPK-specific logic, so it seems like it belongs there.

I also made a utility getWebApkInfo() function. IMHO, it makes
conceptual sense that WebApkActivity only deals with WebApkInfo (it
mostly shouldn't need to know that WebappInfo even exists).

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

In single-view, pages are horizontally centered within the document.
This centering is being done in PDFiumEngine, making it difficult to
test.

This CL moves the centering logic for single-view to
draw_utils::CenterRectHorizontally(). This allows us to test the logic.

Bug: 51472
Change-Id: Idd67cde3c57d4155c9e02ca82a36ad19a6205f08
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730524
Commit-Queue: Jeremy Chinsen <chinsenj@google.com>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683387}

It is safe not to if ~RunLoop happens-after Quit() (or if the loop never
ran). Off-thread destruction happens sometimes in RefCountedThreadSafe
objects after the loop was quit (see failures on patch set 1).

Bug: 715235
Change-Id: If3d6e3661d9bc00547ac5606075b3fe066ff3e7e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1671868
Commit-Queue: Gabriel Charette <gab@chromium.org>
Reviewed-by: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683386}

https://android.googlesource.com/platform/external/perfetto.git/+log/bf0e385cd6fb..f50c2ff2f70c

git log bf0e385cd6fb..f50c2ff2f70c --date=short --no-merges --format='%ad %ae %s'
2019-08-01 treehugger-gerrit@google.com Merge "client api: Ignore multiple registrations of the same data source"

Created with:
  gclient setdep -r src/third_party/perfetto@f50c2ff2f70c

The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-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=perfetto-bugs@google.com

Bug: None
Change-Id: I7e05c82a7434f63450e9e2e09d72d4ccb3e4a46c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730497
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#683385}

ActivationDelegate is the primary interface from cellular_setup.mojom to
be implemented in JavaScript. This class deals with sending and
receiving status update messages to the service.

This CL implements this delegate and deals with routing between the
first page (SIM detect) and either the second page (provisioning) or the
third page (final) depending on the response received.

Note that the second page (provisioning) still isn't implemented as part
of this CL; this functionality is part of a follow-up CL.

Bug: 968858
Change-Id: I67d86647237dc47a1c4660bf7160e5e993f45f13
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1721042
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Ryan Hansberry <hansberry@chromium.org>
Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Auto-Submit: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683384}

As BrowserActionsContainer disappears with the introduction of
ExtensionsToolbarContainer this CL adds CHECKs to make sure that that
experiment is not enabled whenever GetBrowserActionsContainer gets
called.

This change adds |GetToolbarActionViewForId| and
|GetDefaultExtensionDialogAnchorView| to the ToolbarButtonProvider
interface so requests for those do not need to go through
BrowserActionsContainer.

As a a side effect ExtensionUninstallDialogView can now anchor to
pinned extensions when this experiment is enabled (as they are visible),
but like the extension-installed dialog they cannot pop out the
extension to display the dialog anchor yet.

Bug: chromium:985834
Change-Id: I0bbc8da1d501846e72fc06987343dd758e83f922
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731301Reviewed-by: Caroline Rising <corising@chromium.org>
Commit-Queue: Peter Boström <pbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683383}

The main changes are making these run on the UI thread instead of IO.
Also removes some references to net:: objects that aren't needed
anymore.

Bug: 824856
Change-Id: I99262c4dd1d364c7b5a03627121023bea5d671ca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731298
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683382}

We start them as shown if the WebContents is shown, then immediately
send a Hide() unconditionally - in different places for child and main
frames. Instead just always start them hidden and remove all the
plumbing.

This is toward https://chromium-review.googlesource.com/c/chromium/src/+/1693812
wherein I'd like to DCHECK we don't call OnHidden IPC for a provisional
RenderWidget, which we currently do. Right now we DCHECK that we don't
call it for a frozen widget, which includes provisional main frame
widgets, but not the first one. And it's the first one we create shown
and then hide.

Renderer-created widgets (eg window.open()) go through
WebContentsImpl::CreateNewWidget() and should Show() immediately if the
renderer has initialized the page as shown, since there may be no navigation
afterward to show the widget in that case.

R=avi@chromium.org

Bug: 419087, 745091
Change-Id: Id7cc1981ae9fbf6a71c51a4b54fc488ba47f1753
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717702Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683381}

This requires notifying layout_helper_ when a tab is being destroyed,
and TabStripLayoutHelper to step carefully around closing tabs in a few
places, but saves more complexity by not duplicating state between
TabStrip and TabStripLayoutHelper.

Bug: 958173
Change-Id: Iaeafc2391ecac0397947ccc34ddaecf853feb787
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1725271
Commit-Queue: Taylor Bergquist <tbergquist@chromium.org>
Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683380}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/7e33a7e91b89..5833269d4277


Created with:
  gclient setdep -r src-internal@5833269d4277

The AutoRoll server is located here: https://skia-autoroll.corp.goog/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=jbudorick@google.com

Bug: chromium:None,chromium:None,chromium:None
Change-Id: Ia7bb304416e85f3286e941b00efa999309fe0850
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731781Reviewed-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@{#683379}

Using wpt-import in Chromium 46c53596.
With Chromium commits locally applied on WPT:
250461b3 "Worker: Register a service worker just once for worker subresource interception tests"
bf4ad57e "Experimental CookieStore API: some additional browser-side validation"


Note to sheriffs: This CL imports external tests and adds
expectations for those tests; if this CL is large and causes
a few new failures, please fix the failures by adding new
lines to TestExpectations rather than reverting. See:
https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md

Directory owners for changes in this CL:
foolip@chromium.org, lpz@chromium.org, robertma@chromium.org:
  external/wpt/tools

NOAUTOREVERT=true
TBR=lpz

No-Export: true
Change-Id: I9d473295c249178d077aad3e0d789a13249a1fc0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731869Reviewed-by: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#683378}

Mojo JS Lite Bindings were recently renamed to align with the new C++
names. This CL changes usage of the old names with the new ones. See
bug for more details.

Bug: 968369
Change-Id: If7ea7b08af65702c7c972f2e10bd1fa290587306
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1705890
Commit-Queue: Michael Giuffrida <michaelpg@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683377}

An <input type='tel'> should have LocalizedControlType of "telephone"
per https://w3c.github.io/html-aam/#el-input-tel

Currently its LocalizedControlType is "edit".  This change updates it
to "telephone" by adding an entry to
BrowserAccessibility::GetLocalizedStringForRoleDescription().

Bug: 988138
Change-Id: I880df88fe45208e2a0bb296a1541599228ff73cc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1721033Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Kevin Babbitt <kbabbitt@microsoft.com>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Commit-Queue: Dan Clark <daniec@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#683376}

https://chromium.googlesource.com/external/github.com/google/shaderc/+log/3101bd58464a..d289a55e46ff

git log 3101bd58464a..d289a55e46ff --date=short --no-merges --format='%ad %ae %s'
2019-08-01 zoddicus@users.noreply.github.com Only use -fPIC on compilers that support it (#772)

Created with:
  gclient setdep -r src/third_party/shaderc/src@d289a55e46ff

The AutoRoll server is located here: https://autoroll.skia.org/r/shaderc-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=radial-bots+chrome-roll@google.com

Bug: None
Change-Id: I699f58472bb7349d308620a8a84d7eb33f83b65e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730586Reviewed-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@{#683375}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/69c9ca09..b0db4f56

Please follow these instructions for assigning/CC'ing issues:
https://v8.dev/docs/triage-issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: Ia96f03cf868819ab97413e8b5337f2ddc784fcc2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731709Reviewed-by: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#683374}

Since Linux FYI Release (NVIDIA) now runs the same OS and driver.

Move gpu_skia_renderer_vulkan_telemetry_tests and gpu_blink_web_tests_vulkan
testing to "Linux FYI SkiaRenderer Vulkan (NVIDIA)", where they belong.

TBR=kbr

Bug: 978103, 908932
Change-Id: Ibc48e7925c71de048e08b411cba9b6e131ed32cf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730600Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Reviewed-by: Jonathan Ross <jonross@chromium.org>
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683373}

https://skia.googlesource.com/skia.git/+log/80e7bd03d473..c711a8649301

git log 80e7bd03d473..c711a8649301 --date=short --no-merges --format='%ad %ae %s'
2019-08-01 michaelludwig@google.com Combine erode and dilate implementations

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

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=benjaminwagner@google.com

Bug: None
Change-Id: Iff533e7316d9d671bf93e249c376e8c6419aeebb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730587Reviewed-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@{#683372}

To enable to reference `sourceContextList` when checking results.

Bug: 906850
Change-Id: I6d27ac081cef1f2cfa3d387a2a448833aa424694
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1725258
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683371}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/5dd6b1e0a5ef..d014b3d5541d

git log 5dd6b1e0a5ef..d014b3d5541d --date=short --no-merges --format='%ad %ae %s'
2019-08-01 eashanbhatt@google.com cros_chrome_sdk: Delete --require-exact-version
2019-08-01 bmgordon@chromium.org cros lint: Remove deprecated shflags arg

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

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@google.com

Bug: None
Change-Id: Idd91a34376401a3af5e4639e5a696b82b52a8362
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730584Reviewed-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@{#683370}

No change to behavior, because the legacy net path is no longer
supported.

This trims out usage of URLRequestContext/URLRequestContextGetter in the
Safe Browsing component. This is only used in the legacy net path, so
it's safe to remove entirely. This updates chrome/ and AW/ to no longer
pass values for URLRequestContextGetter.

Bug: 989709
Test: autoninja monochrome_apk (both chrome & webview compile)
Test: Manual - start up chrome for desktop, verify SB on http://testsafebrowsing.appspot.com
Test: Manual - start up webview demo app, verify SB works
Change-Id: I84a39cdee3b0703ebf401f565a73ef590d82ef74
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730252Reviewed-by: Varun Khaneja <vakh@chromium.org>
Reviewed-by: Richard Coles <torne@chromium.org>
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683369}

Introduce an intermediate layer between the PinDialogManager and the
RequestPinView, so that the Chrome OS PIN dialogs manager class is
abstracted away from the Pin Dialog UI implementation.

This change allows adding in follow-up CLs the support of different
PIN Dialog UI implementations - for the Chrome OS Login/Lock screens.

Bug: 964069
Change-Id: Ia7130ce76fb007b61daa51e513d62bfa4e6ba590
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1710556
Commit-Queue: Maksim Ivanov <emaxx@chromium.org>
Reviewed-by: Igor <igorcov@chromium.org>
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683368}

https://pdfium.googlesource.com/pdfium.git/+log/6d82d95f2dd0..077eb792907f

git log 6d82d95f2dd0..077eb792907f --date=short --no-merges --format='%ad %ae %s'
2019-08-01 tsepez@chromium.org Break dependence of cjs_document.cpp on fpdfapi/font.
2019-08-01 tsepez@chromium.org Rename CPDF_Font::GetBaseFont() to GetBaseFontName().
2019-08-01 tsepez@chromium.org Break dependence of fpdfapi/page on fxcrt/fdrm.

Created with:
  gclient setdep -r src/third_party/pdfium@077eb792907f

The AutoRoll server is located here: https://autoroll.skia.org/r/pdfium-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=pdfium-deps-rolls@chromium.org

Bug: None
Change-Id: Ic8b4dbc8889530f92c6d475967a2248c327931a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730583Reviewed-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@{#683367}

Temporarily filter some tests which fail due to broken getsockname()
semantics on connect()ed UDP sockets.

Bug: 989223
Change-Id: I5ddd5783d33ce84999cced12f273d3680f56fae1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730653
Auto-Submit: Wez <wez@chromium.org>
Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
Reviewed-by: Kevin Marshall <kmarshall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683366}

Bug: 989821
Change-Id: Iaf03ae1d1dbf8fb7a97dba470e4001b3af7f3906
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730511
Commit-Queue: Shakti Sahu <shaktisahu@chromium.org>
Reviewed-by: Min Qin <qinmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683365}

Add the `AddCredential` command to ChromeDriver.

A draft of the proposed addition to the specification is available at
https://github.com/w3c/webauthn/pull/1256

This is one in a series of patches intended to create a Testing API for
WebAuthn, for use in Web Platform Tests and by external webauthn tests.

For an overview of overall design, please see
https://docs.google.com/document/d/1bp2cMgjm2HSpvL9-WsJoIQMsBi1oKGQY6CvWD-9WmIQ/edit?usp=sharing

Bug: 922572
Change-Id: Id9b9fb75ab6682126d5d1275b12785640b7f0053
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729963
Commit-Queue: Nina Satragno <nsatragno@chromium.org>
Auto-Submit: Nina Satragno <nsatragno@chromium.org>
Reviewed-by: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683364}

This adds skia_renderer_isolated_scripts to chromium_linux_rel_isolated_scripts.

This will add the tests to Linux Tests on CI, and linux-rel on CQ.

TEST=skia_renderer_swiftshader_blink_web_tests
     vulkan_swiftshader_blink_web_tests

Bug: 984120
Change-Id: I3c92d414a0c0aba97e93fc2ad299fd5fee8ecb24
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731015Reviewed-by: Aaron Gable <agable@chromium.org>
Commit-Queue: Jonathan Ross <jonross@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683363}

This CL fixes a typo in the hardcoded path for OEM third-party
libraries.

Bug: internal b/138659261

Change-Id: Ia3d6aeab4e9bc116ac21aeedf47672d14d89acff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731545Reviewed-by: Kenneth MacKay <kmackay@chromium.org>
Commit-Queue: Steven Zhu <jz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683362}

Bug: 989868,924416
Change-Id: I7b19d9e9332df1472e0511a9a410d4e3331e9f6e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730832Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683361}

To support multiple profiles we need to ensure the 1:1 relationship between counterparts.
Native object creates its Java counterpart.

Move AwTracingController from AwBrowsingContext to AwInit because
TracingController should be per-app and not per-profile.

Bug: 963875
Change-Id: I7e6523bbd83b460a94bed65022b3064c554088e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1708930Reviewed-by: Richard Coles <torne@chromium.org>
Commit-Queue: Anna Malova <amalova@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683360}

MaxTextOffset was computing the total text string for a given node in
UTF-16 just to obtain its length. Taking the length of std::string is
a constant-time operation, so eliminating this effort reduces the scale
factor from number of characters to number of nodes. On a simple test
page this led to a 24% speedup in MaxTextOffset which is used by a
variety of TextPattern methods.

Bug: 970297
Change-Id: Ie40e8032b72a45510a2a9ee6bc0e4c4cf5564627
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730094
Commit-Queue: Kevin Babbitt <kbabbitt@microsoft.com>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Reviewed-by: Kurt Catti-Schmidt <kschmi@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#683359}