GitLab

This is a reland of 15fef9cc

Original change's description:
> RC: Set Frame->Process association at RenderFrameHost creation.
>
> At present this is only done at navigation time, which can leave frames
> disconnected from their hosting process.
>
> Bug: 901828
> Change-Id: I611eafebe5e7e54c046def38bbaf5b348dedfcb9
> Reviewed-on: https://chromium-review.googlesource.com/c/1318405
> Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org>
> Reviewed-by: Will Harris <wfh@chromium.org>
> Reviewed-by: François Doray <fdoray@chromium.org>
> Reviewed-by: Jochen Eisinger <jochen@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#608994}

TBR=wfh@chromium.org,jochen@chromium.org

Bug: 901828
Change-Id: I7809f666e7cccba865d2220f9409936b727d1556
Reviewed-on: https://chromium-review.googlesource.com/c/1342699
Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org>
Reviewed-by: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609727}

TBR=oysteine@chromium.org

Bug: 899897
Change-Id: Iaa1a9fbb2ae0d5122bfacb82a21f47e194221197
Reviewed-on: https://chromium-review.googlesource.com/c/1343177
Commit-Queue: Gabriel Charette <gab@chromium.org>
Reviewed-by: Etienne Bergeron <etienneb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609726}

BTW This bug could be caught much earlier. We should consider enabling
static code analysis, see https://checkerframework.org/.

Test: passes static code analysis in Android Studio.
Bug: internal b/119660059.
Change-Id: Ia6d9a4fa5118e417fa01c667b8b0ebca2e2cbc38
Reviewed-on: https://chromium-review.googlesource.com/c/1343112Reviewed-by: Simeon Anfinrud <sanfin@chromium.org>
Commit-Queue: Jan Lamecki <jachor@google.com>
Cr-Commit-Position: refs/heads/master@{#609725}

We stopped using this experiment some time ago.

Bug: 900255
Change-Id: I95bf3e3b065ed7113d9cc172680a5095520f288f
Reviewed-on: https://chromium-review.googlesource.com/c/1343279Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Tommy Li <tommycli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609724}

Before this patch, the spacing between the details and the payment
request UI were too large.

This patch shows/hides the caroussel when the payment request is shown.
It's an intermediate quick fix before we have the new UI architecture
and works since the payment request is shown during a script execution,
which in turn again means that the caroussel is empty. Showing the
carousel reduces the margins of the details view.

R=jdemeulenaere@chromium.org, szermatt@google.com

Bug: 806868
Change-Id: I17d5d3bf138c8a2f68b24753fde55cada50984fa
Reviewed-on: https://chromium-review.googlesource.com/c/1341542
Commit-Queue: Mathias Carlen <mcarlen@chromium.org>
Reviewed-by: Stephane Zermatten <szermatt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609723}

All sync configuration code is removed from UnifiedConsentService.
This means that the UnifiedConsentService does *not* modify the
sync state/settings anymore.

Bug: 906031
Change-Id: I98fbc466feafc3dfb8474fcacdfdc506acd2ccaf
Reviewed-on: https://chromium-review.googlesource.com/c/1340816Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Christian Dullweber <dullweber@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Reviewed-by: David Roger <droger@chromium.org>
Commit-Queue: Thomas Tangl <tangltom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609722}

This CL introduces AccountsMutator, which will support the mutation of
refresh tokens and seeding of account info for the user's Gaia accounts
in the IdentityManager world.

Its design is conceptually similar to that of PrimaryAccountMutator,
although unlike that class it is supported on all platforms. The full
design doc is here:
https://docs.google.com/document/d/1kLjnxPnBAX0G6W-3u6OF_VguuJc0pXdgCRVR0z3yn-g/edit#

This CL does the following:
- Introduces the class
- Implements an initial API and its unittest
- Adds the ability to get the mutator from IdentityManager

Followup CLs will complete the API surface.

Bug: 887870
Change-Id: Iafc0d365766118ad07eef5038d2257f1630c254e
Reviewed-on: https://chromium-review.googlesource.com/c/1333775Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Commit-Queue: Colin Blundell <blundell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609721}

This reverts commit a6e3f5c9.

Reason for revert: This change is on the blame list for a webgl conformance test failure in WebglConformance_conformance_uniforms_no_over_optimization_on_uniform_array_09 on Windows FYI. Reverting to see if this is so.

Original change's description:
> Implement WEBGL_video_texture
> 
> This patch implement a WebGL draft extension: WEBGL_video_texture. This extension will bring a new type of texture for WebGL and can
> share the video frame to WebGL texture directly. This should reduce on blit operation and should have performance improvement for
> uploading video to texture.
> 
> Bug: 776222
> 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
> Change-Id: Id052010bb726c328b0362c28d2486ce1986cc6e2
> Reviewed-on: https://chromium-review.googlesource.com/c/1235335
> Commit-Queue: Shaobo Yan <shaobo.yan@intel.com>
> Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
> Reviewed-by: Kentaro Hara <haraken@chromium.org>
> Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
> Reviewed-by: Dan Sanders <sandersd@chromium.org>
> Reviewed-by: Kenneth Russell <kbr@chromium.org>
> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#609604}

TBR=kbr@chromium.org,haraken@chromium.org,mlamouri@chromium.org,sandersd@chromium.org,shaobo.yan@intel.com,foolip@chromium.org,kainino@chromium.org

Change-Id: Ia843571180c67a343d6db2c89eac484faf306fb5
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 776222
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
Reviewed-on: https://chromium-review.googlesource.com/c/1344251Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Commit-Queue: Robert Kroeger <rjkroege@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609720}

In blink::LayoutThemeMac, various system color properties are retrieved
from NSColor. These system colors are part of the "dynamic system color
store", and trying to access them may cause issues with the sandbox.

This augments the blink::WebSandboxSuport interface on Mac to look up
system colors via a shared memory segment that is populated by the
browser. In addition, this centralizes the various Mac implementations
of that interface into a single one.

      System Prefs>General and change the Highlight Color. Upon going
      back to Chrome, the new highlight color should be visible.

Bug: 641509, 36032
Test: Highlight some text on a web page. Then go to
Change-Id: I3bc05c08ecab62b1fc68442d3edd93ec7edb8590
Reviewed-on: https://chromium-review.googlesource.com/c/1331133Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609719}

Records user actions when one of the shortcuts is pressed.
Records time the user spent with the popup open.

Bug: none
Change-Id: Icbc76437d0a6cc12ee040c393fa1b1ad61c86e9b
Reviewed-on: https://chromium-review.googlesource.com/c/1337345
Commit-Queue: Stepan Khapugin <stkhapugin@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609718}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/655a9bc2..8f1238bc

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=luci.chromium.try:linux-blink-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;luci.chromium.try:android_optional_gpu_tests_rel

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

Change-Id: Id43771a1fb6e4b1370f3252fa58be8d894f8cc2f
Reviewed-on: https://chromium-review.googlesource.com/c/1343573
Commit-Queue: Sergiy Byelozyorov <sergiyb@chromium.org>
Reviewed-by: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#609717}

This will make it consistent with the Upstream prompt.

Bug: 906560
Change-Id: I86a1753fc0ac8e4dfb6ef2a4d6c5efd282d5dd16
Reviewed-on: https://chromium-review.googlesource.com/c/1343070Reviewed-by: Moe Ahmadi <mahmadi@chromium.org>
Commit-Queue: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609716}

The legacy (pre-USS) implementation of session sync was the only
remaining user of this field and has been deleted recently, so let's
just remove the now unused API.

This is convenient for pseudo-USS (SyncableServiceBasedBridge) because
there is no need for additional plumbing to propagate this information
through (it wasn't actually properly populated prior to this patch).

Bug: 895455
Change-Id: I02a577978b5fd7a84ced4775cd200d0210928985
Reviewed-on: https://chromium-review.googlesource.com/c/1343003
Commit-Queue: Mikel Astiz <mastiz@chromium.org>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Reviewed-by: Jan Krcal <jkrcal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609715}

Guard for https://skia-review.googlesource.com/c/skia/+/171908

TBR=fmalita@chromium.org

Change-Id: I368fa8f6539b9072a0ae2b75e72040c5d2f68130
Reviewed-on: https://chromium-review.googlesource.com/c/1343009Reviewed-by: Mike Klein <mtklein@chromium.org>
Reviewed-by: Florin Malita <fmalita@chromium.org>
Commit-Queue: Mike Klein <mtklein@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609714}

ANGLE now exposes this extension under the same conditions as Chrome: on top
of a native ES driver.

BUG=angleproject:1552

Change-Id: I6552e51bccd5ece43b7405b26d63127283a90c46
Reviewed-on: https://chromium-review.googlesource.com/c/1342497Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Reviewed-by: Kai Ninomiya <kainino@chromium.org>
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609713}

Bug: 806868
Change-Id: Ia2d3ab25ab95645db5215a2c6d8c4b0f1d9d3a1c
Reviewed-on: https://chromium-review.googlesource.com/c/1343561Reviewed-by: Mathias Carlen <mcarlen@chromium.org>
Commit-Queue: Ganggui Tang <gogerald@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609712}

This is mostly to get the bugfix from [1], which will
allow the removal of 2 workarounds in our build system.
See [2]

[1] https://github.com/google/bundletool/issues/32
[2] https://chrome-internal-review.googlesource.com/c/clank/internal/apps/+/719231

BUG=891931
R=agrieve@chromium.org, ntfschr@chromium.org

Change-Id: Ibc6f406ce3b2d920b19435e392b51181308e24a2
Reviewed-on: https://chromium-review.googlesource.com/c/1343107Reviewed-by: agrieve <agrieve@chromium.org>
Commit-Queue: David Turner <digit@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609711}

The test was meant to check what happens if a password field has a
CVC-like name. Instead, it tested what happens if a text field has
this name.

This CL fixes that mistake. The test thankfully still passes.

This is a yak-shaving for adding the fallback pass, hence the below
bug association.

Bug: 906584
Change-Id: I9228c0252c97397fb5486e8a62c4cfb6a3f14cf6
Reviewed-on: https://chromium-review.googlesource.com/c/1343269Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Commit-Queue: Vaclav Brozek <vabr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609710}

This patch fixes NGLineBreaker not to freeze when all of the
following conditions met:
* 'word-wrap: break-word' is set.
* 'whitespace: pre-wrap' is set.
* Two or more adjacent preserved spaces are split to two or
  more elements, and is the last space to fit in the line.

e.g.,
<div style="whitespace: pre-wrap; word-break: break-word">
  <span>xxx <span> yyyy
</div>
and "yyyy" does not fit.

We need to handle trailing spaces not only when spaces follow
a break opportunity but also spaces are after spaces.

Bug: 903909
Change-Id: Ie4346a670ec22d35cca3a290b9a423161537e4e8
Reviewed-on: https://chromium-review.googlesource.com/c/1343466Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609709}

Pass the hosted e-mail domain to the gaia sign in page through GCPW.

Bug: 887444
Change-Id: Ie77034dadc3873de35bbf32a30d20364877ec328
Reviewed-on: https://chromium-review.googlesource.com/c/1333869Reviewed-by: Greg Thompson <grt@chromium.org>
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Reviewed-by: Roger Tawa <rogerta@chromium.org>
Reviewed-by: Tommy Martino <tmartino@chromium.org>
Commit-Queue: Tien Mai <tienmai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609708}

BUG=None

Change-Id: If9ca23541732251aa800c0335c8b094235e631a7
Reviewed-on: https://chromium-review.googlesource.com/c/1343458
Commit-Queue: Abhishek Arya <inferno@chromium.org>
Reviewed-by: Abhishek Arya <inferno@chromium.org>
Reviewed-by: Jungshik Shin <jshin@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609707}

base::AssertBlockingAllowedDeprecated is deprecated in favor of
ScopedBlockingCall, which serves as a precise annotation of
the scope that may/will block.

Please make sure of the following:
  - ScopedBlockingCall is instantiated in a scope with minimal CPU usage.
    If this is not the case, ScopedBlockingCall should be instantiated
    closer to the blocking call. See scoped_blocking_call.h for more
    info. Please let me know when/where the blocking call happens if this needs
    to be changed.
  - Parameter |blocking_type| matches expectation:
      MAY_BLOCK: The call might block (e.g. file I/O that might hit in memory cache).
      WILL_BLOCK: The call will definitely block (e.g. cache already checked and now pinging
        server synchronously).
    See BlockingType for more info. While I assumed MAY_BLOCK by default, that might
    not be the best fit if we know that this callsite is guaranteed to block.
  - The ScopedBlockingCall's scope covers the entirety of the blocking operation
    previously asserted against by the AssertBlockingAllowed().
  - Calls to blocking //base APIs don't need to be annotated
    with ScopedBlockingCall. All blocking //base APIs (e.g. base::ReadFileToString, base::File::Read,
    base::SysInfo::AmountOfFreeDiskSpace, base::WaitableEvent::Wait, etc.) have their
    own internal annotations.

Refer to the top-level CL if necessary :
https://chromium-review.googlesource.com/c/chromium/src/+/1338391

Please CQ if LGTY!

This CL was uploaded by git cl split.

R=csharp@chromium.org

Bug: 903957
Change-Id: I5ff84cb3c4169e19e04d59e682916eb6632a848a
Reviewed-on: https://chromium-review.googlesource.com/c/1338127Reviewed-by: proberge <proberge@chromium.org>
Commit-Queue: proberge <proberge@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609706}

- Adds kWasmCodeCache to blink::features.
- Checks if enabled before creating the cache in the browser.
- Checks if enabled before fetching from cache in renderer.

This is patterned after the Javascript IsolatedCodeCache feature.

Bug: chromium:719172
Change-Id: I1ffea5d8029b2b550c45e3ba25821889c7c2183c
Reviewed-on: https://chromium-review.googlesource.com/c/1341071
Commit-Queue: Bill Budge <bbudge@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Mythri Alle <mythria@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609705}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/316e4119ed88..afe4ec5b3170


Created with:
  gclient setdep -r src-internal@afe4ec5b3170

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.


TBR=mmoss@chromium.org

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

1) Favor --renderer-cmd-prefix more heavil when generating flags files
for ClusterFuzz.
2) Remove the --gpu-launcher option as it no longer works. Looking at
existing issues I'm not sure that this is too important for our
coverage, so it seems easier to remove it than to try to continue
maintaining it.

R=inferno@chromium.org

Bug: 904773
Change-Id: I3f0f468337540dfc5af73289ad0a46e41dcdb5ae
Reviewed-on: https://chromium-review.googlesource.com/c/1340978Reviewed-by: Abhishek Arya <inferno@chromium.org>
Commit-Queue: Abhishek Arya <inferno@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609703}

zip_mini_installer_tests runs this script as part of the build, and the build
is supposed to be silent except for errors.

Bug: none
Change-Id: I97b25cabf36fe4f2df577877c46159fad389f3dc
Reviewed-on: https://chromium-review.googlesource.com/c/1342597Reviewed-by: Greg Thompson <grt@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609702}

Using wpt-import in Chromium 756bea38.
With Chromium commits locally applied on WPT:
5ee777f6 "Fix test exclusion logic of wpt/referrer-policy test generator
warning: inexact rename detection was skipped due to too many files.
warning: you may want to set your diff.renameLimit variable to at least 1920 and retry the command."
ec589a5c "Add referrer-policy module worker tests"


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

NOAUTOREVERT=true
TBR=raphael.kubo.da.costa@intel.com

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

This patch adds style recalc and one of the stages that the display
lock prevents. Note that in order to reach the element during commit,
this also adds a "style needs recalc" to the element.

I'll replace these with smaller hammers after updating the layout tests,
and fixing any bugs that popup there.

R=chrishtr@chromium.org

Bug: 882663
Change-Id: Icf8ac9c285b5e340c38addca7483b419f34ebadc
Reviewed-on: https://chromium-review.googlesource.com/c/1340570Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609700}

These are the only two stories still often failing on
android-pixel2-perf bot.

NOTRY=true
TBR=nednguyen@google.com

Bug: 865400
Change-Id: I3439893506c11b92d0d18a337ec7eef43c55080b
Reviewed-on: https://chromium-review.googlesource.com/c/1344133Reviewed-by: Juan Antonio Navarro Pérez <perezju@chromium.org>
Commit-Queue: Juan Antonio Navarro Pérez <perezju@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609699}

ChromeTableViewController.

This CL migrates the PrivacyCollectionViewController from
CollectionViewController, which is based on MDCCollectionViewController,
to ChromeTableViewController, which is based on UITableViewController.

Bug: 894791
Change-Id: Ia35b023b4fc1231d6ef35c93fb1ab8961d56ea40
Reviewed-on: https://chromium-review.googlesource.com/c/1340330
Commit-Queue: Yi Su <mrsuyi@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Reviewed-by: edchin <edchin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609698}

Luckily, nacl compiler has fdebug-compilation-dir and it makes nacl compiled result deterministic.
https://chromium.googlesource.com/native_client/pnacl-clang/+/cfbfff6970d1fc876a6ed3f04289e3086c9a9129/include/clang/Driver/CC1Options.td#135

Bug: 906741
Change-Id: I4b8ea54d20ba4cc58c07cc941a14584df33426c8
Reviewed-on: https://chromium-review.googlesource.com/c/1343472
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609697}

The issue is very similar to https://crbug.com/905648.

TBR=dcastanga@chromium.org

Bug: 906292
Change-Id: Ia4283dff5acc39b6146518a1dd7c2ebffe35d8e4
Reviewed-on: https://chromium-review.googlesource.com/c/1342404
Commit-Queue: Abhishek Arya <inferno@chromium.org>
Reviewed-by: Max Moroz <mmoroz@chromium.org>
Reviewed-by: Abhishek Arya <inferno@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609696}

Bug: 899437
Change-Id: I25ab289eaf053f09974413431e70ec648def95f5
Reviewed-on: https://chromium-review.googlesource.com/c/1309114Reviewed-by: Dan Erat <derat@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609695}

r608360 enabled fragment caching when BFC block offset
changes, but r609030 disabled it when RareData exists,
probably due to merge failure.

This patch re-enables it. It recovers some of the
performance loss seen at go/layoutng-loading-perf:
https://pinpoint-dot-chromeperf.appspot.com/job/1605b070140000

Change-Id: I071fd5b4dd177245aa402718ce6f737549aa1b12
Bug: 635619
Reviewed-on: https://chromium-review.googlesource.com/c/1341741
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609694}

Used async functions, arrow functions, and const, and added some comments.

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

Reload type has two variants: RELOAD and RELOAD_BYPASSING_CACHE. PlzNavigate
currently sets net::LOAD_NORMAL to load_flags and false to skip_service_worker
as BeginNavigationParams, so RELOAD_BYPASSING_CACHE doesn't affect those. This
CL tries to change those parameters according to the reload type.

Bug: 906542
Change-Id: Ib2f9f645007966d86a694d54dccbb476ec0fb45d
Reviewed-on: https://chromium-review.googlesource.com/c/1343875Reviewed-by: Camille Lamy <clamy@chromium.org>
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609692}

Change-Id: I1867a301c4bb0c9cd95edc94473ff783b9504cdf
Reviewed-on: https://chromium-review.googlesource.com/c/1341922Reviewed-by: Michael van Ouwerkerk <mvanouwerkerk@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609691}

When the kCompositorTouchAction flag is on, we use the white listed
touch action to process a gesture event. This CL adds histogram to
measure how often a GSB and GSU is allowed / filtered / deferred by
the main thread / compositor thread touch action.

Bug: 745718
Change-Id: I2a8b16904ad9fa3f75249d4a1bb10aa0849094ce
Reviewed-on: https://chromium-review.googlesource.com/c/1340588
Commit-Queue: Xida Chen <xidachen@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609690}

TBR=wzang@chromium.org

Bug: 904644
Change-Id: I8cd86ab57a5a5fc782447569e933f095d34a8d4d
Reviewed-on: https://chromium-review.googlesource.com/c/1344049Reviewed-by: Maxim Kolosovskiy <kolos@chromium.org>
Commit-Queue: Maxim Kolosovskiy <kolos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609689}

Enable ReadableStream objects to be transferred by postMessage().
Internally, the ReadableStream is converted to a MessagePortChannel and
it is that that is transferred. This involves adding a "stream_channels"
field to the TransferableMessage mojo struct for the channels that will
be used by ReadableStream (and in future WritableStream and
TransferableStream objects).

Additional code is added to V8ScriptValueSerializer and
V8ScriptValueDeserializer to recognise ReadableStream objects.
SerializedScriptValue has new methods and an array of
MessagePortChannels as a member variable to transfer them.

The new code is behind the "TransferableStreams" Blink feature and must
be explicitly activated. A set of new layout tests provides basic
verification that postMessage() of ReadableStream objects work. They are
run with the feature enabled via a new VirtualTestSuite.

The changes are covered in more detail in the design doc:
https://docs.google.com/document/d/1_KuZzg5c3pncLJPFa8SuVm23AP4tft6mzPCL5at3I9M/edit

Bug: 894838
Cq-Include-Trybots: luci.chromium.try:linux_mojo
Change-Id: I032306415aa0c4e146af25439f42bcff70436416
Reviewed-on: https://chromium-review.googlesource.com/c/1315367
Commit-Queue: Adam Rice <ricea@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609688}