GitLab

Merge all resource dependency manifests using the manifest merger from the
Android SDK, providing the functionality described in
https://developer.android.com/studio/build/manifest-merge.html.

Removing the nontrivial manifest guard in the android_aar_prebuilt() template
will be done in a follow-up change, as well as removing pre-merged manifest
tags, such as "com.google.android.gms.version" meta-data.

Bug: 643967
Change-Id: Ifdf9f3f76f5c80f1a2326dcd47045d032556936f
Reviewed-on: https://chromium-review.googlesource.com/558296Reviewed-by: Bo Liu <boliu@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Ingemar Ådahl <ingemara@opera.com>
Cr-Commit-Position: refs/heads/master@{#485303}

This CL adds TextBadgeView to iOS Showcase. This involves adding a
text_badge_view folder to showcase, creating a glue view controller,
and modifying the Showcase configuration file and BUILD.gn files as
necessary.

Since TextBadgeView is currently a stub implementation, Showcase
displays a blank white screen.

BUG=740133.

Review-Url: https://codereview.chromium.org/2967113003
Cr-Commit-Position: refs/heads/master@{#485302}

BUG=704216

Review-Url: https://codereview.chromium.org/2936673003
Cr-Commit-Position: refs/heads/master@{#485301}

Bug: 739816
Change-Id: I73ac3e7b68f5918a3f4749896d0ed7cf26d739df
Reviewed-on: https://chromium-review.googlesource.com/562856
Commit-Queue: Lucas Gadani <lfg@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: James MacLean <wjmaclean@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485300}

After discovering that the unused |SetDefaultResourceForSite| breaks the
current Beta build, this CL redoes https://crrev.com/2959193002/ and
disables the baked-in popular sites for iOS.

Bug: 737607
Change-Id: I6ba17e95a2a81d9ec9e06580ab1248b2fc24faac
Reviewed-on: https://chromium-review.googlesource.com/564614Reviewed-by: Chris Pickel <sfiera@chromium.org>
Commit-Queue: Friedrich Horschig <fhorschig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485299}

https://pdfium.googlesource.com/pdfium.git/+log/4183f201c515..217644c0d65a

$ git log 4183f201c..217644c0d --date=short --no-merges --format='%ad %ae %s'
2017-07-06 npm Force unicodes into valid ranges

Created with:
  roll-dep src/third_party/pdfium


Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls


TBR=dsinclair@chromium.org

Change-Id: Ifbb39630f7ef720133eae54ca9336b680bdbd900
Reviewed-on: https://chromium-review.googlesource.com/565044
Reviewed-by: <pdfium-deps-roller@chromium.org>
Commit-Queue: <pdfium-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485298}

Use templates to determine the size of each element and the elements per
unit allowing ComputeDataSize to only use a single inlined CheckedNumeric
multiply with a compile-time constant.

The data size validation of glUniform calls was up to 12% of the GPU
process' CPU time on some WebGL applications, this lowers it to be less
than 0.1%.

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: Ic6e5f975087308da9473918a9ef081c0b591fbb4
Reviewed-on: https://chromium-review.googlesource.com/559104Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485297}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/74cef601..2588b89c

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

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

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org

Change-Id: I5a3aa9aefd1bfe7a3c3ca5afd882376123bef2fa
Reviewed-on: https://chromium-review.googlesource.com/565459Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485296}

When an intent is received in Custom Tabs, extract a redirect endpoint
from an extra. If it exists, the URL to load is first party with respect
to the calling app, preconnect to the redirect endpoint.

This is part of Leapfrog, see the bug.

Also, only disables preconnection with the data reduction proxy for HTTP
URLs, as HTTPS URLs don't go through the proxy.

BUG=739165

Review-Url: https://codereview.chromium.org/2970003003
Cr-Commit-Position: refs/heads/master@{#485295}

crrev.com/2858693002 introduced a wait on an egl fence before pageflipping
buffers.

After that CL we noticed big performance regressions on Intel:
crbug.com/721463

Removing the coarse egl lock that seemed to be the issue  helped but
didn't solve the performance regression completely:
https://crrev.com/f3d9d4d0c7a4520e2e0117222ff6e8d4a4ce595f

This CL adds a workaround for Intel to restore the previous behavior where
synchronization relies completely on the Intel drivers.

Bug: 721463
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: Ice34e03edb3f4cd81152ae917ceb08a23626b2d0
Reviewed-on: https://chromium-review.googlesource.com/562178Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Daniele Castagna <dcastagna@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485294}

When the bottom sheet is closed, set its adapter to null, which clears the view
(and recycles all the view holders inside it), to reduce the memory overhead of
the views (which potentially hold large bitmaps) while the sheet is closed.
The adapter itself is still around and holds on to the model, so it can be
reattached when the sheet is opened again. The model caches bitmaps only via
discardable references, which it will drop under memory pressure.

Bug: 718925
Change-Id: I58510bc831a35f15d831915ba9fc47f929253978
Reviewed-on: https://chromium-review.googlesource.com/562136
Commit-Queue: Bernhard Bauer <bauerb@chromium.org>
Reviewed-by: Nicolas Dossou-Gbété <dgn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485293}

This flag takes precedence over --site-per-process and other
site isolation modes.

BUG=688617
TEST=Cross-site subframes work with --single-process --site-per-process
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation

Review-Url: https://codereview.chromium.org/2964033002
Cr-Commit-Position: refs/heads/master@{#485292}

Filter out build/secondary/third_party dependencies to work around
__main__.LicenseError: missing README.chromium or licenses.py SPECIAL_CASES entry in build/secondary/third_party/android_tools

BUG=606859
BUG=710801
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_cronet_tester

Review-Url: https://codereview.chromium.org/2959303002
Cr-Commit-Position: refs/heads/master@{#485291}

https://chromium.googlesource.com/angle/angle.git/+log/27a6063..70c95fa

BUG=chromium:739448,chromium:731324,:angleproject:1644,chromium:682815

TBR=jmadill@chromium.org

TEST=bots

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

Change-Id: I9ed559801bfbb7cada2fef863096047f33437703
Reviewed-on: https://chromium-review.googlesource.com/565051Reviewed-by: Geoff Lang <geofflang@chromium.org>
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485290}

BUG=619868

Review-Url: https://codereview.chromium.org/2966383004
Cr-Commit-Position: refs/heads/master@{#485289}

CL 563307 didn't add taget/action for the share button on the tools
menu, which meant that the share button (and thus: printing and reading
list) didn't work.

This CL fixes that, by adding the two add/remove target/action calls
that should have been there in the first place.

Bug: 73881
Change-Id: Ia3c90b8c6175cb3038f321636ef467efecc3cbfb
Reviewed-on: https://chromium-review.googlesource.com/565498
Commit-Queue: Mark Cogan <marq@chromium.org>
Reviewed-by: Jean-François Geyelin <jif@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485288}

Remove a block of code that used to detect a incorrect PageTransition
and to replace it by its correct value.
Apparently, this block is no more reached. This CL removes it.
Furthermore, a test is added. It replays the steps one had to do to
reach this block of code.

BUG=736772,740461
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation

Review-Url: https://codereview.chromium.org/2961903003
Cr-Commit-Position: refs/heads/master@{#485287}

https://swiftshader.googlesource.com/SwiftShader.git/+log/83a6bb9..a781af7

BUG=737875

TEST=bots

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel,linux_chromium_cfi_rel_ng;master.tryserver.chromium.android:android_optional_gpu_tests_rel

Change-Id: Ib4a779492cd09ba17bd6dda86cb1b0ef9685a756
Reviewed-on: https://chromium-review.googlesource.com/564665Reviewed-by: Alexis Hétu <sugoi@chromium.org>
Commit-Queue: Nicolas Capens <nicolascapens@google.com>
Cr-Commit-Position: refs/heads/master@{#485286}

Intent to implement and ship:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/Wa5sdcDrJnA

BUG=730030

Review-Url: https://codereview.chromium.org/2936263003
Cr-Commit-Position: refs/heads/master@{#485285}

GrBackendTextureDesc is being phased out.

Change-Id: I6e4bb519ad31cfb4796c127d2d4daecd98598c79
Reviewed-on: https://chromium-review.googlesource.com/562807
Commit-Queue: Brian Salomon <bsalomon@chromium.org>
Reviewed-by: David Reveman <reveman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485284}

Since there is now a class SingleDebugDaemonLogSource, the old
name "SingleLogSource" is ambiguous. Rename it to indicate that the
logs come from a log file.

Also refactored the use of SingleLogSource in feedbackPrivate API:
- Use the base interface class SystemLogsSource instead, in
  LogSourceAccessManager.
- Convert from feedback_private::LogSource directly to a
  SystemLogSource in SingleLogSourceFactory. Conversion of enums is
  internal to SingleLogSourceFactory.

BUG=733846

Review-Url: https://codereview.chromium.org/2956513004
Cr-Commit-Position: refs/heads/master@{#485283}

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/9f7e1bcf98c3..72646aa580ee

$ git log 9f7e1bcf9..72646aa58 --date=short --no-merges --format='%ad %ae %s'
2017-07-10 charliea Upload the battor agent binary to the latest version

Created with:
  roll-dep src/third_party/catapult
BUG=728496


Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls


CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=sullivan@chromium.org

Change-Id: Id17109882ae7c93dc517fda12a3c1bdbe9d7ceab
Reviewed-on: https://chromium-review.googlesource.com/565001
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485282}

This CL introduces the interfaces TouchSelectionControllerClient and
TouchSelectionMenuClient, and the basic logic to support (initially)
copy on touch-selected content. It is not functional until the
required plumbing to export selection updates from PDFium lands in a
separate CL.

Bug: 737585
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_site_isolation
Change-Id: Iaa5ed68a0590d3e2e27e5d2ae3d7b86ab5342e92
Reviewed-on: https://chromium-review.googlesource.com/558771Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: Dan Sinclair <dsinclair@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485281}

BUG=739386

Change-Id: I81d4802615ef8b02aaa48db99bddbdd8ce8f8868
Reviewed-on: https://chromium-review.googlesource.com/559536Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485280}

TBR=perezju@chromium.org, ulan@chromium.org

Bug: 728152
Change-Id: I5b71e3b844c11a51dedc6be291885762ad373a0a
Reviewed-on: https://chromium-review.googlesource.com/565184Reviewed-by: Ned Nguyen <nednguyen@google.com>
Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
Commit-Queue: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#485279}

Cleaning up a TODO from a recent CL.

Change-Id: I7a9f470c3681d8cfd12f9202879f24e2074cda72
Reviewed-on: https://chromium-review.googlesource.com/562043Reviewed-by: Varun Khaneja <vakh@chromium.org>
Reviewed-by: Jialiu Lin <jialiul@chromium.org>
Reviewed-by: Ben Wells <benwells@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Commit-Queue: Luke Z <lpz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485278}

global using namespace statements cause issues with jumbo builds so this
patch moves and removes two such occurances in modules/sensor.

An alternative is to import explicit symbols rather than the full
namespaces.

R=mikhail.pozdnyakov@intel.com

Bug: 
Change-Id: Iafc85a856b02b381dae6244b2fc3acedc37e30db
Reviewed-on: https://chromium-review.googlesource.com/565296Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: bratell at Opera <bratell@opera.com>
Cr-Commit-Position: refs/heads/master@{#485277}

The current behavior of DrmDevice when drm atomic is requested but not
supported is to fall back to legacy page flip.

This caused more issues than benefits, since it's not clear if
we're running with atomic or with legacy pageflip when atomic is
requested.

This CL makes Chrome fail to startup when drm atomic is requested but
not available.

Bug: 
Change-Id: Ic6824a2b346d51cebbde1f26b7f05507aed64a25
Reviewed-on: https://chromium-review.googlesource.com/563998Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Commit-Queue: Daniele Castagna <dcastagna@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485276}

TBR=yzshen@chromium.org
NOTRY=true

Change-Id: I34adc34f77fc0ab45ecde9d939f39f2350396f83
Reviewed-on: https://chromium-review.googlesource.com/565187Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485275}

This fixes a weird interaction between to tasks involving settings reset:
 - Post-cleanup settings reset, which can happen at start up after the
   Chrome Cleanup Tool successfully completed (for example, it may have
   required a reboot);
 - Settings reset prompt, which will check if user settings have been
   hijacked and offer the user to reset it to its default values.

In case both features are enabled, we should only check the latter after
completing the former, so that we will not prompt users to reset their
settings if they have already agreed on resetting them post-cleanup.

BUG=690020

Review-Url: https://codereview.chromium.org/2971183002
Cr-Commit-Position: refs/heads/master@{#485274}

There is a Function<> template in WTF/Functional.h which is shadowed
or collides with any local definitions of Function. This is not always
a problem, but it caused problems in Jumbo builds so let us rename
it to something harmless.

Change-Id: Ib594b2673a1dce6b4647445d3377b1e1099849da
Reviewed-on: https://chromium-review.googlesource.com/563667
Commit-Queue: bratell at Opera <bratell@opera.com>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485273}

A couple of files in core/css were missing include guards which broke
jumbo builds.

R=fs@opera.com

Change-Id: I1d50e8b62f4926c054d51b48ab4f4edf5df5b76d
Reviewed-on: https://chromium-review.googlesource.com/565291Reviewed-by: Fredrik Söderquist <fs@opera.com>
Commit-Queue: bratell at Opera <bratell@opera.com>
Cr-Commit-Position: refs/heads/master@{#485272}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/99a6c585..74cef601

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

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

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org

Change-Id: I1479913544163c02fa9e0e82003a4bd77211bd25
Reviewed-on: https://chromium-review.googlesource.com/565458Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485271}

Change-Id: I86c0fbc4fe353dd8ab00cb10b24f0c3b3a905561
Reviewed-on: https://chromium-review.googlesource.com/565284Reviewed-by: Anthony Berent <aberent@chromium.org>
Commit-Queue: Michael van Ouwerkerk <mvanouwerkerk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485270}

https://pdfium.googlesource.com/pdfium.git/+log/b46ce4172ee8..4183f201c515

$ git log b46ce4172..4183f201c --date=short --no-merges --format='%ad %ae %s'
2017-07-07 thestig Change parameter type to IPWL_FocusHandler::OnSetFocus().

Created with:
  roll-dep src/third_party/pdfium


Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls


TBR=dsinclair@chromium.org

Change-Id: I5fe1bf6508a7720d7fba2daef8689a4453f6e317
Reviewed-on: https://chromium-review.googlesource.com/565182
Reviewed-by: <pdfium-deps-roller@chromium.org>
Commit-Queue: <pdfium-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485269}

This reverts commit 7e6f3031.

Reason for revert: The crash is fixed by https://chromium.googlesource.com/chromium/src/+/b5ac971cfbf3afa2230534369912bffccefb0fc1.

Original change's description:
> Mark serviceworker-proxied/thorough/cors-preflight2-other-https.html crash on MSAN
> 
> TBR=imcheng@chromium.org
> NOTRY=true
> 
> Bug: 736802
> Change-Id: I9938a569ad9fe8001fe0b3385c519ca95ad9a70b
> Reviewed-on: https://chromium-review.googlesource.com/548836
> Reviewed-by: Xida Chen <xidachen@chromium.org>
> Commit-Queue: Xida Chen <xidachen@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#482304}

TBR=imcheng@chromium.org,xidachen@chromium.org

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

Bug: 736802
Change-Id: If05af3b9aa3df36c160b756cebf8ee1a3a38df76
Reviewed-on: https://chromium-review.googlesource.com/564878Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485268}

The target that compiles generated files does not use the same
template as other code in blink core so it didn't automatically become
jumbo enabled. Since it's a non-negliable part of the build time (~1%)
this patch enables jumbo for this target as well.

R=fs@opera.com
BUG=713137

Review-Url: https://codereview.chromium.org/2973603003
Cr-Commit-Position: refs/heads/master@{#485267}

Bug: 734584
Change-Id: If013a3e5031314abbb72be4d94a949e0eb1c3527
Reviewed-on: https://chromium-review.googlesource.com/565280
Commit-Queue: vitaliii <vitaliii@chromium.org>
Reviewed-by: Jan Krcal <jkrcal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485266}

DevTools relies on a NetLogObserver (which needs a NetLog) to return the
raw response headers, e.g. Set-Cookie headers.

Bug: 692090
Change-Id: I9faae71198b7c45d1dc05175b606452012d7ec83
Reviewed-on: https://chromium-review.googlesource.com/565139
Commit-Queue: Alex Clarke <alexclarke@chromium.org>
Reviewed-by: Eric Seckler <eseckler@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485265}

This allows a track to be added to a peerconnection with 0 or 1
associated streams. The multiple stream case is not yet supported.
This allows tracks and streams to be attached to a peerconnection
independently of add/removeStream and is a major milestone of the
RTP Media API.

The ontrack and onended events will be added/fire on the remote end in
follow-up CLs.

Spec:
https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-addtrack
https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-removetrack

BUG=700916, 705901

Review-Url: https://codereview.chromium.org/2951713002
Cr-Commit-Position: refs/heads/master@{#485264}