GitLab

changes:
Add a switch to make the feature dev behind the flag.

Bug: 805046
Test: unit_tests --gtest_filter=AboutFlagsHistogramTest*
Change-Id: I1b63060cf6b08557d94447b4a87f9ab07b192e1c
Reviewed-on: https://chromium-review.googlesource.com/890633Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Commit-Queue: Qiang Xu <warx@google.com>
Cr-Commit-Position: refs/heads/master@{#532546}

We want to keep minimal symbols when remove_webcore_debug_symbols is
set, so that we can get readable backtrace.

On ChromeOS arm build, the size of debug file increases from
899MB to 1.244GB. It increases 245 MB.

Bug: chromium:792999
Change-Id: Ibc238308754a2727505cfbac3ce24f7a70027529
Reviewed-on: https://chromium-review.googlesource.com/862607Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Ryo Hashimoto <hashimoto@chromium.org>
Commit-Queue: Yunlian Jiang <yunlian@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532545}

The current flakiness occurs in the form of a timeout waiting for profiling to
start for renderers. On Android, there's a warm-up renderer that could start
before ProfilingProcessHost gets a chance to start up - as such, it will never
be profiled. This CL adds logic to force profiling to start for all renderers,
which should fix the flakiness.

This CL also fixes a bug in ProfilingClient, which was only keeping the most
recent binding.

Bug: 804412
Change-Id: I836e55650b30a6360e0bc0f9189aacb7a75ea0c9
Reviewed-on: https://chromium-review.googlesource.com/889999Reviewed-by: Maria Khomenko <mariakhomenko@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532544}

Bug: 608780
Change-Id: I4b699a8322702e117a0e2a5b81b61fd294e781b5
Reviewed-on: https://chromium-review.googlesource.com/889522Reviewed-by: Łukasz Anforowicz <lukasza@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532543}

R=dalecurtis@chromium.org

Change-Id: If38dfc4fb4deb50f8e82fe89e4d98fef5fd81863
Reviewed-on: https://chromium-review.googlesource.com/889782Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532542}

Bug: 761288
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I0630b778aa8b758c7742af15541e83162f13d431
Reviewed-on: https://chromium-review.googlesource.com/875165Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Commit-Queue: Xiaoqian Dai <xdai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532541}

Ports most of WebVrTransitionTest to have a WebXR equivalent. Does not
port testNfcFiresVrdisplayactivate or testTrustedIntentAllowsAutoPresent
since there is not currently an implemented equivalent of the
functionality they test in WebXR.

Bug: 804043
Change-Id: I20985416985ca777a541cf42e9a377c2c29a5456
Reviewed-on: https://chromium-review.googlesource.com/885098
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532540}

R=dpranke@chromium.org, jbudorick@chromium.org

No-Try: True
Bug: 731553
Change-Id: I12cd97bfee4d1cc7bf81f5c990014a27335a1c50
Reviewed-on: https://chromium-review.googlesource.com/891666Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532539}

NewApi warnings were suppressed accidentally and an AssertionError
constructor that requires API 19 was used. The NewApi warnings are back,
so this fix avoids using the AssertionError, and throws the exceptions
as they are.

This is an accidental leftover from the previous fixes, and is blocking
the CL that removes the NewApi error suppression.

Bug: 805509,803484
Change-Id: Ib2cc11c3ffdcfc50a4618d98d016ab52e0f1f624
Reviewed-on: https://chromium-review.googlesource.com/891578Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: Troy Hildebrandt <thildebr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532538}

This is a reland of b2b018c5.

Original change's description:
> Build Fuchsia packages for test and executable targets.
> 
> All targets that use the test() or fuchsia_executable_runner rules
> will produce Fuchsia packages, which contain the test executable and
> their runtime dependencies.
> 
> The packages are modules which can be deployed in an already-running
> system, as opposed to the current scheme which bakes the files into
> the system boot image.
> 
> Deployment and support for dynamic libraries will be addressed
> in followup CLs.
> 
> This CL also:
> * Fixes PathService logic for packaged invocations.
> * Adds a new "build_manifest.py" GN helper script.
> * Fixes the dependency graph for Fuchsia runner script generation
>   so that it accurately captures the real dependency ordering.
> 
> 
> Bug: 796779
> Change-Id: I4e3a38e0075573b328ad98425cc493e28cff1ca4
> Reviewed-on: https://chromium-review.googlesource.com/841749
> Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
> Reviewed-by: Wez <wez@chromium.org>
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Reviewed-by: Dirk Pranke <dpranke@chromium.org>
> Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#531288}

Bug: 796779
Change-Id: I8c365a51abb49c2542aec8f66073e7fb7217cf75
Reviewed-on: https://chromium-review.googlesource.com/886982
Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Scott Graham <scottmg@chromium.org>
Reviewed-by: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532537}

Upstream has allocated DRM_FORMAT_MOD_INVALID as a special modifier
that indicates the absence of a modifier. This is the legacy mode
where the kernel gets the tiling/layout information through back
channels, typically as a property of the BO.

It's a little more concise that passing addfb_flags around as we did
before and can be encoded into the NativePixmap handle as well.

Bug: b:70546200, b:71416883, chromium:789292, b:69238712, b:68003124
Change-Id: I4340355e56d4117afebb06e1d96d4f8b93900a6e
Reviewed-on: https://chromium-review.googlesource.com/885904
Commit-Queue: Kristian H. Kristensen <hoegsberg@chromium.org>
Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532536}

Ensure focusability is enabled along with the correct tool-tip.

Bug: 806706
Change-Id: Ic60278a2d57f1c23cf36c8633994eb39fc7a5417
Reviewed-on: https://chromium-review.googlesource.com/890388Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Commit-Queue: Allen Bauer <kylixrd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532535}

Removes myself from all owners files except tools/gn.

Replace myself with dpranke for owners of BUILDCONFIG.gn

TBR=jam@chromium.org

Change-Id: I015c6724ba04c07a9954107e1f5319ff3ef480ce
Reviewed-on: https://chromium-review.googlesource.com/891669Reviewed-by: Brett Wilson <brettw@chromium.org>
Commit-Queue: Brett Wilson <brettw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532534}

This lets additional non-RenderText tests leverage the RenderTextTestApi
class. Put the class to immediate use in a VR UI test.

BUG=

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_vr;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: Idf4d65a8e1b44430da72fe4bd5e3df6efb54719d
Reviewed-on: https://chromium-review.googlesource.com/881521
Commit-Queue: Christopher Grant <cjgrant@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532533}

SandboxedUnpacker::MessageCatalogsSanitized() does fall through some
error cases triggering a NOTREACHED.

Bug: 806926,177475
Change-Id: I9aaf62d1197a5885ab8871ca93197c6cb11cfdac
Reviewed-on: https://chromium-review.googlesource.com/891620
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532532}

This patch adds IsInlineBox() and IsInline() to NGPhysicalFragment
as we need claer distinction of inline boxes in NGPaint.

Also anonymous fragment was removed. This fragment type was used
to create an anonymous fragment for inline children, where two
fragments are generated for one LayoutBlockFlow.  This was changed
to create line boxes directly under the parent box fragment in
line-by-line refactoring by ikilpatrick@.

One crash was upgraded to failure because the logic to determine
anonymous fragment was wrong when ::first-line was used, and now
it is gone.

Bug: 636993, 714962
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: Iac918830f1696789008376e77d36557e373236f8
Reviewed-on: https://chromium-review.googlesource.com/890878Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532531}

This CL adds an argument option to print out debug info for diagnostics.

Bug: 801231
Change-Id: I53b23c6569c9938ef4c5b5a786ceaeee751ffc5d
Reviewed-on: https://chromium-review.googlesource.com/871506Reviewed-by: Abhishek Arya <inferno@chromium.org>
Commit-Queue: Yuke Liao <liaoyuke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532530}

Change-Id: I31e3e705624cab5cd5005fe46f3c88d2517c549d
Reviewed-on: https://chromium-review.googlesource.com/887284Reviewed-by: Bartosz Fabianowski <bartfab@chromium.org>
Commit-Queue: Sean Kau <skau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532529}

This reverts commit f9a22f3e.

Reason for revert: <INSERT REASONING HERE>

Original change's description:
> Oilpan: Immediatelly promptly free objects.
> 
> This CL brings the following changes to promptly freeing and coalescing:
> 1) Promptly freed objects on already swept pages are immediately added to the free list.
> 2) For promptly freed objects on not already swept pages we only clear the mark bit.
> 3) The promptly_freed_size_ counter is explicitly set to 0 before sweeping because sweeping will take care of coalescing as well.
> 4) The dead bit is removed.
> Note that coalescing before sweeping completed can not happen.
> 
> Future outlook: As a next step we will evaluate if we need coalescing and if we need it we have to make it jank friendly.
> 
> Bug: chromium:804279, chromium:633030
> Change-Id: I35dfae80ae0e7ed6cfbc91877d97d0b5fc26498e
> Reviewed-on: https://chromium-review.googlesource.com/873974
> Commit-Queue: Hannes Payer <hpayer@chromium.org>
> Reviewed-by: Kentaro Hara <haraken@chromium.org>
> Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#532509}

TBR=haraken@chromium.org,hpayer@chromium.org,mlippautz@chromium.org

Change-Id: I868bc9b51c18a546994de93a3a8ef80362b0ba19
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: chromium:804279, chromium:633030
Reviewed-on: https://chromium-review.googlesource.com/891640Reviewed-by: Samuel Huang <huangs@chromium.org>
Commit-Queue: Samuel Huang <huangs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532528}

Setting the pan attribute will set the value immediately instead of
dezippering from the current value to the new value.

Chromium Feature: https://www.chromestatus.com/features/5287995770929152
Intent to ship: https://groups.google.com/a/chromium.org/d/msg/blink-dev/YKYRrh0nWMo/aGzd3049AgAJ

Bug: 752985
Test: StereoPanner/dezipper.html
Change-Id: I13815d7cb3a6d4ea93dd8f0f1bab739e6768e561
Reviewed-on: https://chromium-review.googlesource.com/607028
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532527}

All socket writes need to be annotated with traffic annotation tag.
This CL adds this requirement to the API.

Bug: 721401
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Iee211a7812ba074f2788c879d0bc4b715e178fde
Reviewed-on: https://chromium-review.googlesource.com/881425Reviewed-by: Ramin Halavati <rhalavati@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Randy Smith <rdsmith@chromium.org>
Commit-Queue: Helen Li <xunjieli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532526}

https://chromium.googlesource.com/angle/angle.git/+log/d1434c048145..e4741fd0f2bc

$ git log d1434c048..e4741fd0f --date=short --no-merges --format='%ad %ae %s'
2018-01-25 lucferron Vulkan: Begin implementing caps mappings

Created with:
  roll-dep src/third_party/angle


The AutoRoll server is located here: https://angle-chromium-roll.skia.org

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

Change-Id: Id100844c51b2eb57e54b82ba0e1cdadc2db93713
Reviewed-on: https://chromium-review.googlesource.com/891300
Commit-Queue: angle-deps-roller . <angle-deps-roller@chromium.org>
Reviewed-by: angle-deps-roller . <angle-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532525}

Remove dezippering so that when the gain value is set, the output gain
immediately snaps to the value, instead of exponentially approaching
the target value.

Chromium Feature: https://www.chromestatus.com/features/5287995770929152
Intent to ship: https://groups.google.com/a/chromium.org/d/msg/blink-dev/YKYRrh0nWMo/aGzd3049AgAJ

Bug: 555647
Test: Gain/dezipper.html
Change-Id: I31c2b067c9eeade4127195b2eb9bc3b716f308b5
Reviewed-on: https://chromium-review.googlesource.com/602604Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532524}

This is a content/ concept that can remain soley in content/,
and it turns out the zygote doesn't do anything with it.

Change-Id: I91f81af707532c81f6fcc0d2fce6eea233ba3c27
Reviewed-on: https://chromium-review.googlesource.com/887822
Commit-Queue: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532523}

Using wpt-import in Chromium b04cb83b.
With Chromium commits locally applied on WPT:
9f32e9c0 "S13nServiceWorker: Add tests for network fallback for navigations with request bodies"


Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/11283

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

TBR=leon.han@intel.com

No-Export: true
Change-Id: I62cd59f2f13776df7201c3398ac643cef9cd8d0a
Reviewed-on: https://chromium-review.googlesource.com/889773
Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Reviewed-by: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532522}

https://skia.googlesource.com/skia.git/+log/cca86f386cfd..11e5bff1594c

$ git log cca86f386..11e5bff15 --date=short --no-merges --format='%ad %ae %s'
2018-01-29 ethannicholas workaround for Intel SPIR-V OpCompositeConstruct bug
2018-01-29 angle-skia-autoroll Roll skia/third_party/externals/angle2/ d1434c048..e4741fd0f (1 commit)

Created with:
  roll-dep src/third_party/skia


The AutoRoll server is located here: https://autoroll.skia.org

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

Change-Id: I1ef5368b90cf1e275c819defc640d7b41cbbf227
Reviewed-on: https://chromium-review.googlesource.com/891422
Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#532521}

Revert "Cros splitscreen: Disable the splitscreen for M65 stable but keep it enabled for all other channels."

This reverts commit ddccd3f6:
https://chromium-review.googlesource.com/c/chromium/src/+/869196

M65 has been cut. This CL is no longer needed. Revert it.

Bug: 800501
TBR: oshima@chromium.org
Change-Id: I1943f27874fa83b67ca7d42e1b292f93f52f86a0
Reviewed-on: https://chromium-review.googlesource.com/887878Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
Commit-Queue: Xiaoqian Dai <xdai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532520}

Patch https://chromium-review.googlesource.com/c/chromium/src/+/742162
got reverted because it caused cc_unittest failure on CFI bot. This
patch fixed the bug.

Commit message from the original patch:

The current cc/animations logic assumes a single animation has a single
keyframe effect and can only affect a single layer. To enable animations
with multiple keyframe effects, cc::AnimationPlayer need to support
multiple AnimationTickers each corresponding to one keyframe effect.

Currently there is a 1:1 relationship between AnimationPlayer and
AnimationTicker. This patch is to extend it to 1:n. Here is a summary of
changes:
- Introduce a sub-class of AnimationPlayer, a.k.a
SingleTickerAnimationPlayer, to handle the existing logic (single
effect). SingleTickerAnimationPlayer owns only one AnimationTicker as
the AnimationPlayer does today.
- Currently a AnimationTicker is created upon creating AnimationPlayer.
In this patch, tickers are created separately and added to the player
afterwards. Tickers that the player owns may belong to different targets
therefore the player needs to coordinate with AnimationHost regarding
this situation.
- Adjust existing unit tests according to the changes above.

Bug: 767043
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: If21bad1285c35bbc048fef6b619c8272c0760551
Reviewed-on: https://chromium-review.googlesource.com/890724Reviewed-by: Ian Vollick <vollick@chromium.org>
Commit-Queue: Yi Gu <yigu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532519}

The domain cdn.ampproject.org and its subdomains should be preloaded for
HSTS and pin to a Google certificate chain.

TBR=palmer@chromium.org

Change-Id: I5c0edd88b9cda350ab4c77d59f3d8b650d674518
Reviewed-on: https://chromium-review.googlesource.com/890045Reviewed-by: Eric Lawrence <elawrence@chromium.org>
Commit-Queue: Eric Lawrence <elawrence@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532518}

//chrome/browser correctly lists //chrome/common:service_process_mojom
in its public_deps. However, //chrome/browser/extensions and
//chrome/browser/ui are listed in allow_circular_includes_from, allowing
them to include headers from //chrome/browser without a dependency. Add
explicit dependencies from //chrome/browser/extensions and
//chrome/browser/ui to //chrome/common:service_process_mojom.

Bug: 805916
Change-Id: I83c2c7588e8056d413b9cccc8f5eceeb203986d7
Reviewed-on: https://chromium-review.googlesource.com/890686
Commit-Queue: Lei Zhang <thestig@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532517}

Original CL: https://chromium-review.googlesource.com/886863

Fix:
- Suppress unused resources for clank/ widgets

BUG=799070,806060
TBR=nyquist@chromium.org,twellington@chromium.org

Change-Id: Id42c5a626f4a0754bea3d4db7a10af9756c0002d
Reviewed-on: https://chromium-review.googlesource.com/891339
Commit-Queue: Peter Wen <wnwen@chromium.org>
Reviewed-by: Peter Wen <wnwen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532516}

This change moves Cocoa-only browser and test source files into variables, to
reduce merge conflicts while these files get integrated into the Views browser
builds as well.

Bug: 802257,804950
Change-Id: I123b778fb7614afc20a50a800eab5ae2a6290b24
Reviewed-on: https://chromium-review.googlesource.com/889792
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532515}

See https://bugs.chromium.org/p/chromium/issues/detail?id=722928#c72
which says that FALLTHROUGH is intended here.

This CL was uploaded by git cl split.

R=tdresser@chromium.org

Bug: 177475
Change-Id: I3555a1bb32d6b7ec5a2f68dd13266da2e48af62c
Reviewed-on: https://chromium-review.googlesource.com/890429Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532514}

This reverts commit 09ef7a92.

Reason for revert: the original revert did not fix ProcessManagerBrowserTest.NestedURLNavigationsToExtensionBlocked failing: https://bugs.chromium.org/p/chromium/issues/detail?id=806684#c8 

Original change's description:
> Revert "Use SCANOUT_* usage in GpuMemoryBufferVideoFramePool"
> 
> This reverts commit b6486594.
> 
> Reason for revert: speculative revert for fixing browser_tests
> failure on Win (32) Tests bot.
> 
> ProcessManagerBrowserTest.NestedURLNavigationsToExtensionBlocked started to fail
> continuously after the CL. I'm not fully confident of the 
> relationship between the failure and this change, but trying to
> revert to see if it helps. 
> 
> 
> Original change's description:
> > Use SCANOUT_* usage in GpuMemoryBufferVideoFramePool
> > 
> > Currently GpuMemoryBufferVideoFramePool allocates buffers with
> > GPU_READ_CPU_READ_WRITE usage. This means these buffers won't be used for
> > scanout (no fb added on CrOS).
> > 
> > This CL simply changes the usage used when allocating buffers to
> > SCANOUT_CPU_READ_WRITE, in this way this buffers will be created for
> > scanout, if possible.
> > 
> > Note that SCANOUT implies GPU_READ, meaning that in case the allocation
> > of the buffer for scanout will fail, the buffers will be allocated
> > exactly as they'd be if GPU_READ_CPU_READ_WRITE were used instead.
> > 
> > Bug: b/71837407
> > Change-Id: I3a03daf721f1cc04038a4f6f91985b5affe2a276
> > Reviewed-on: https://chromium-review.googlesource.com/884401
> > Commit-Queue: Daniele Castagna <dcastagna@chromium.org>
> > Reviewed-by: Miguel Casas <mcasas@chromium.org>
> > Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#532286}
> 
> TBR=dalecurtis@chromium.org,mcasas@chromium.org,dcastagna@chromium.org,hoegsberg@chromium.org,ddavenport@chromium.org
> 
> Change-Id: I13c479543ac53694f6f413c83aa15481e9c80c53
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: b/71837407
> Reviewed-on: https://chromium-review.googlesource.com/890978
> Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
> Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#532344}

TBR=dalecurtis@chromium.org,mcasas@chromium.org,dcastagna@chromium.org,shimazu@chromium.org,hoegsberg@chromium.org,ddavenport@chromium.org

Change-Id: I92a0379b36cdc6b21bf609ab69a467acbad23c9e
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: b/71837407
Reviewed-on: https://chromium-review.googlesource.com/891718Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Commit-Queue: Daniele Castagna <dcastagna@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532513}

Consolidate expectations for the imported Web Platform Tests for
legacy multibyte encodings (Chinese, Japanese, Korean) which exercise
tens of thousands of code points and often time out (>30s) even when
marked as slow.

TBR=kbr@chromium.org

Bug: 805725,736056,749070
Change-Id: I12051e3c3a20730783aabb39376b55e9788450f4
Reviewed-on: https://chromium-review.googlesource.com/889538Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Commit-Queue: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532512}

Updating from 65.0.3322.0_rc-r1.

This CL may cause a small binary size increase, roughly proportional
to how long it's been since our last AFDO profile roll. For larger
increases (around or exceeding 100KB), please file a bug against
gbiv@chromium.org. Additional context: https://crbug.com/805539

TBR=agrieve@chromium.org, gbiv@chromium.org

Bug: None
Test: CQ
Change-Id: I36614584245a42f039cf40690a3b9172b2c572c7
Reviewed-on: https://chromium-review.googlesource.com/891618Reviewed-by: agrieve <agrieve@chromium.org>
Commit-Queue: George Burgess <gbiv@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532511}

This CL adds an extra StateChangeDetail parameter to the
Observer::OnSecureChannelStatusChanged() function. This parameter is
currently unused, but it will be used by a future CL to better handle
connection retries.

Bug: 805218, 672263
Change-Id: I4dc80f324d74a6df54113b058dec0bb07459ae3f
Reviewed-on: https://chromium-review.googlesource.com/888038Reviewed-by: Jeremy Klein <jlklein@chromium.org>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532510}

This CL brings the following changes to promptly freeing and coalescing:
1) Promptly freed objects on already swept pages are immediately added to the free list.
2) For promptly freed objects on not already swept pages we only clear the mark bit.
3) The promptly_freed_size_ counter is explicitly set to 0 before sweeping because sweeping will take care of coalescing as well.
4) The dead bit is removed.
Note that coalescing before sweeping completed can not happen.

Future outlook: As a next step we will evaluate if we need coalescing and if we need it we have to make it jank friendly.

Bug: chromium:804279, chromium:633030
Change-Id: I35dfae80ae0e7ed6cfbc91877d97d0b5fc26498e
Reviewed-on: https://chromium-review.googlesource.com/873974
Commit-Queue: Hannes Payer <hpayer@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532509}

Changing the default mode to AllAccess from BlacklistOnly.
Changing the default so that we can show printers if the
NativePrintersAccessMode policy is unset.

Changes to policy_templates.json will be separate.

Bug: 805825
Change-Id: I62ef189749ad2209ba715835e4a1ffda8150573e
Reviewed-on: https://chromium-review.googlesource.com/887366Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
Commit-Queue: Sean Kau <skau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532508}

+ Speculative fix for ModalDialogManagerTest#testShow_UrlBarFocused:
  Wait for url bar focused callback to make sure dialogs are updated.
+ JavascriptTabModalDialogTest#testAlertModalDialogMessageFocus:
  Use landscape mode for test to make sure alert message is long enough.

Bug: 802254, 800377
Change-Id: Ic7549b81aa1ca8900858260f6311772014c7de37
Reviewed-on: https://chromium-review.googlesource.com/887823Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Becky Zhou <huayinz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532507}