GitLab

This reverts commit b26b9d89.

Reason for revert: Added static initializers, see https://ci.chromium.org/buildbot/chromium.chrome/Google%20Chrome%20Linux%20x64/37632

Original change's description:
> Add X11 support for ATK key event listeners
> 
> ATK requires us to allow it to filter all key events. Add an AtkUtil
> mechanism to filter key events.
> 
> Bug: 866334
> Change-Id: I42383479ab78242325bda0714afb60b7dcf2fe65
> Reviewed-on: https://chromium-review.googlesource.com/c/1319709
> Commit-Queue: Martin Robinson <mrobinson@igalia.com>
> Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
> Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#607989}

TBR=sadrul@chromium.org,dmazzoni@chromium.org,mrobinson@igalia.com

Change-Id: I7cc1d2bfa85761af5c1704260646758ae3028063
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 866334
Reviewed-on: https://chromium-review.googlesource.com/c/1336437Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608166}

This CL starts to separate Coordinator from UI layer in BVC.
BrowserCoordinator owns BVC. BrowserViewWrangler owns the
BrowserCoordinator.

Bug: 904622
Change-Id: I6f259061d045584ce4d878621b083d9ebdc023c2
Reviewed-on: https://chromium-review.googlesource.com/c/1332779
Commit-Queue: edchin <edchin@chromium.org>
Reviewed-by: Mark Cogan <marq@chromium.org>
Reviewed-by: edchin <edchin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608165}

Bug: None
Change-Id: Ic1a16a5cf023718a401404e62070203090bd3bd7
Reviewed-on: https://chromium-review.googlesource.com/c/1320214Reviewed-by: David Tseng <dtseng@chromium.org>
Commit-Queue: Zach Helfinstein <zhelfins@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608164}

For better test output when it fails.

R=ikilpatrick@chromium.org

Change-Id: I6800cba6f137ab1b87c094b08baeed8551689203
Reviewed-on: https://chromium-review.googlesource.com/c/1336549Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608163}

This reverts commit 7bd7f065.

Reason for revert: most likely fix for a gn failure on win gpu fyi

Original change's description:
> Roll src/third_party/SPIRV-Tools/src a6150a3fe778..dc9d155d6216 (1 commits)
> 
> https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/a6150a3fe778..dc9d155d6216
> 
> 
> git log a6150a3fe778..dc9d155d6216 --date=short --no-merges --format='%ad %ae %s'
> 2018-11-14 stevenperron@google.com Fix folding of volatile store. (#2048)
> 
> 
> Created with:
>   gclient setdep -r src/third_party/SPIRV-Tools/src@dc9d155d6216
> 
> The AutoRoll server is located here: https://autoroll.skia.org/r/spirv-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=dsinclair@chromium.org
> 
> Change-Id: I0406b560139f9213b5d117496462133318f5e03c
> Reviewed-on: https://chromium-review.googlesource.com/c/1335842
> Reviewed-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@{#608123}

TBR=dsinclair@chromium.org,chromium-autoroll@skia-public.iam.gserviceaccount.com

Change-Id: I20b1a38321fd39c527e5ebac99510a004649f4d5
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/1336436Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Commit-Queue: Robert Kroeger <rjkroege@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608162}

A few Android-only features used kSomeBaseFeature.name rather than a
constant string like the others. On other platforms, these trip a static
initializer check. On Android, chrome/android/static_initializers.gni's
count actually included it. Fix them and clear it.

(Along the way, fix some arraysize vs base::size warnings from presubmits.)

See discussion in
https://chromium-review.googlesource.com/c/chromium/src/+/1334412/2/chrome/browser/about_flags.cc#b2609

An earlier iteration of this CL also switched to constexpr per that discussion,
but that seems to upset Windows.

Note to reviewers: it's worth double-checking I didn't copy one of the strings
wrong.

Change-Id: If53659e2ea93c972edba4c4246d22044a8fdd20c
Reviewed-on: https://chromium-review.googlesource.com/c/1334654
Commit-Queue: David Benjamin <davidben@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608161}

Frames from deduplicated samples were being left in the current sample
state on the class, resulting in incorrect extra frames being added when
the next sample was recorded. This change eliminates the current sample
state to avoid this problem, and adds a test for this case.

Bug: 905379
Change-Id: I5fe0ccd3e50675669d4c7124fb7f64ebb85fe807
Reviewed-on: https://chromium-review.googlesource.com/c/1336247Reviewed-by: Xi Cheng <chengx@chromium.org>
Commit-Queue: Mike Wittman <wittman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608160}

Move WaylandKeyboardDelegate out of server.cc
This CL only moves code around.

Bug: 896710
Test: Built on ChromeOS
Change-Id: I09a062796c987ca23137acb081b05ea129badeba
Reviewed-on: https://chromium-review.googlesource.com/c/1318576
Commit-Queue: Shawn Gallea <sagallea@google.com>
Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608159}

Intercept DidFinishNavigation events and cancel in-flight auto-fetch requests.

Bug: 883486
Change-Id: I41d5f1fdcc22c119fa0024abc1dd8fea13483576
Reviewed-on: https://chromium-review.googlesource.com/c/1313249
Commit-Queue: Dan H <harringtond@google.com>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Reviewed-by: Carlos Knippschild <carlosk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608158}

* Add ScopdExclude class.
 The window specified will be ignored in occlusion tracking process.
* Exclude the dragging window in overview mode.

Bug: 902074
Test: covered by unit tests.
  Manaully tested on slate and make sure that dragging window
  in tablet overview mode doesn't not trigger frame evictor.

Change-Id: I4312f2dbc1928ac7cbbd4eac562547e7009fdbc0
Reviewed-on: https://chromium-review.googlesource.com/c/1318360Reviewed-by: François Doray <fdoray@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608157}

This reverts commit 36f90a0e.

Reason for revert: causing crash loop

Bug: b:119569166

Original change's description:
> Use cast http connection in libassistant.
> 
> Bug: b:118193766
> Test: Manual
> 
> Change-Id: Ia0cd58e42761b35b9f7281344266505074d59936
> Reviewed-on: https://chromium-review.googlesource.com/c/1321956
> Commit-Queue: Yilei Li <yileili@google.com>
> Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#607318}

TBR=xiaohuic@chromium.org,yileili@google.com

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

Bug: b:118193766
Change-Id: I187d2d105ec65b561a7ab498c38fce66f56f454b
Reviewed-on: https://chromium-review.googlesource.com/c/1335962Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Commit-Queue: Xiaohui Chen <xiaohuic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608156}

If, in the future, someone else needs to track down how this works, this
will hopefully save them a lot of time.

Change-Id: I212ceeefaff08a69a34efe1ea808ff9061edd982
Reviewed-on: https://chromium-review.googlesource.com/c/1336489Reviewed-by: Martin Kreichgauer <martinkr@google.com>
Commit-Queue: Martin Kreichgauer <martinkr@google.com>
Cr-Commit-Position: refs/heads/master@{#608155}

We never care about scrollbars
in LayoutGrid::PopulateGridPositionsForDirection(),
that's fine if the scrollbars are at the end
(e.g. on the right in horizontal writing mode and LTR direction)
but it causes problems when they're at the beginning
(e.g. on the left in horizontal writing mode and RTL direction).

The patch modifies the method so it takes into account scrollbar size
in order to compute the position of the columns/rows
depending on the direction and the writing mode.

BUG=904438
TEST=external/wpt/css/css-grid/grid-model/grid-container-scrollbar-001.html
TEST=external/wpt/css/css-grid/grid-model/grid-container-scrollbar-vertical-lr-001.html
TEST=external/wpt/css/css-grid/grid-model/grid-container-scrollbar-vertical-rl-001.html

Change-Id: I9c8307638647e449f6975cacf99f89e29d4fa655
Reviewed-on: https://chromium-review.googlesource.com/c/1334370Reviewed-by: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Sergio Villar <svillar@igalia.com>
Commit-Queue: Manuel Rego <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#608154}

In audio focus there is a concept of an "active"
media session. This is the top most non-temporary
session. This is slightly different from the current
focused session which may be temporary. We use the
active media session for media controller too.

This adds a method for tracking the current active
media session. This will be used for the media
notification for hiding/showing it. At the moment
it uses focus which may result it being shown
incorrectly.

BUG=897836

Change-Id: I0e2f82ffe23394e04d72622aa0d27cd4e8834d7a
Reviewed-on: https://chromium-review.googlesource.com/c/1330696
Commit-Queue: Becca Hughes <beccahughes@chromium.org>
Reviewed-by: Tommy Steimel <steimel@chromium.org>
Reviewed-by: Dan Erat <derat@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608153}

Remove the dialog because it's no long being used

Change-Id: Ifda9684ee338543cd46de2caaf995e3813f53029
Reviewed-on: https://chromium-review.googlesource.com/c/1332414
Commit-Queue: Owen Min <zmin@chromium.org>
Reviewed-by: David Roger <droger@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608152}

This prevents us from having to mutate the flags variable each time a bubble is
shown or hidden.

Bug: 905436
Change-Id: Ia40f2d0b9aa949fd6c67b46dcf22a5e5272f60a7
Reviewed-on: https://chromium-review.googlesource.com/c/1336254
Commit-Queue: Quan Nguyen <qnnguyen@chromium.org>
Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608151}

The width and height of the selected outline should be equal to
the dimensions of the parent subtract two times the pixel width
of the outline.

Bug: 899683
Change-Id: I9c2c8fc669651fe713e1aa431438c3fe02881543
Reviewed-on: https://chromium-review.googlesource.com/c/1335780Reviewed-by: Kristi Park <kristipark@chromium.org>
Commit-Queue: Kyle Milka <kmilka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608150}

Change-Id: Iaa00593f0d2e86582f788c90929b1ab04417e75b
Reviewed-on: https://chromium-review.googlesource.com/c/1336251Reviewed-by: Samuel Huang <huangs@chromium.org>
Reviewed-by: Eric Stevenson <estevenson@chromium.org>
Commit-Queue: Samuel Huang <huangs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608149}

R=khorimoto@chromium.org

Bug: 899324
Test: none
Change-Id: I0c579f604635d89ba2b1394d5142fbb21de12560
Reviewed-on: https://chromium-review.googlesource.com/c/1330828Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: James Hawkins <jhawkins@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608148}

Bug: 905125
Change-Id: I76b2e9279ffadcec025a7cb730da7275de0eb367
Reviewed-on: https://chromium-review.googlesource.com/c/1335030Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Commit-Queue: Yue Cen <rsgingerrs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608147}

This can easily save ~1k if not ~10k+ per message file.  Looking at an
example CrOS image today, this can add up to MB of data in the rootfs.

We don't make this optional for now as it's not clear whether anyone
really cares, and it's easy enough for people to pretty print the json
files after the fact.

Bug: 852585
Change-Id: I1d2331dfc38d404ea03facd3d0a8845f32c4f981
Reviewed-on: https://chromium-review.googlesource.com/c/1320515Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Mike Frysinger <vapier@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608146}

GetResultAs returns a pointer to the transfer buffer. Under some
conditions, the transfer buffer may be reallocated, so we need to make
sure a GetResultAs-returned pointer isn't used across such a
reallocation.

Bug: 905336
Change-Id: I1a9699d38149c56ee5430bff125a1168ca053696
Reviewed-on: https://chromium-review.googlesource.com/c/1336152
Commit-Queue: Antoine Labour <piman@chromium.org>
Reviewed-by: James Darpinian <jdarpinian@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608145}

This CL makes vector icon selection for AutocompleteMatch instances more
direct and simple by moving some of the complexity out of a static
method that was increasingly requiring callers to examine fields of the
instance to compose the call.  By empowering instances to use available
state for icon selection, it is now easy to specialize.  This was done
first for Drive document icons, and will also be used to differentiate
Pedals.  This CL only specializes one using an omnibox icon but all
Pedals will get their own.

Bug: 893183
Change-Id: I460c6202f1220b18091a9178f471464943190072
Reviewed-on: https://chromium-review.googlesource.com/c/1329895
Commit-Queue: Orin Jaworski <orinj@chromium.org>
Reviewed-by: Christopher Grant <cjgrant@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608144}

The only difference between the new chrome_elf_arm64.def and existing chrome_elf_x64.def is that RegisterNonABICompliantCodeRange_ExportThunk and UnregisterNonABICompliantCodeRange_ExportThunk are not included because they are defined as x64 specific.

Bug: 893460
Change-Id: Id0d11fb9264309b3c6ce97d81eeab1a39e158fba
Reviewed-on: https://chromium-review.googlesource.com/c/1325149Reviewed-by: Bruce Dawson <brucedawson@chromium.org>
Reviewed-by: Cait Phillips <caitkp@chromium.org>
Commit-Queue: Tom Tan <Tom.Tan@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#608143}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/ee14affed4c5..e04de3408e65


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

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: Iad77194fcb52a123da0445e5948d69c9f8f997ec
Reviewed-on: https://chromium-review.googlesource.com/c/1336213Reviewed-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@{#608142}

Corresponds to http://cl/221021676

Bug: 868246
Change-Id: I26f7fe58f07ecfcbe1b540b7c805f575b8b73320
Reviewed-on: https://chromium-review.googlesource.com/c/1198363Reviewed-by: Mark Pearson <mpearson@chromium.org>
Commit-Queue: Fergal Daly <fergal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608141}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/5986b744..c10b4254

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;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: I90be4db3c4b15d03d66feb822574d54eadf23455
Reviewed-on: https://chromium-review.googlesource.com/c/1336249Reviewed-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@{#608140}

Until macOS 10.13, the relative ordering of a view's subviews' layers and
unassociated sublayers is undefined, so view layers can end up hidden behind
the compositor layer. See:

  https://developer.apple.com/library/archive/releasenotes/AppKit/RN-AppKit/index.html#10_13Layer-backed%20Views

This change re-adds a dedicated compositor view, but with less plumbing than
what was removed in r594160.

Bug: 865901, 899499
Change-Id: Ibbec83da2e8785e06522008dfc2d9eab7ca43bf9
Reviewed-on: https://chromium-review.googlesource.com/c/1334290
Commit-Queue: Sidney San Martín <sdy@chromium.org>
Reviewed-by: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608139}

https://chromium.googlesource.com/catapult.git/+log/35d4c6c88f92..4925b069e1cf


git log 35d4c6c88f92..4925b069e1cf --date=short --no-merges --format='%ad %ae %s'
2018-11-14 benjhayden@chromium.org Add polymer-svg-template to third_party for v2spa
2018-11-14 benjhayden@chromium.org Temporarily permit alerts to have lists of ownership components.
2018-11-14 benjhayden@chromium.org Add triage-existing for v2spa
2018-11-14 benjhayden@chromium.org Disable telemetry tests that fail on Luci Android.
2018-11-14 benjhayden@chromium.org Add timeseries-descriptor for v2spa
2018-11-14 benjhayden@chromium.org Fix timestamp x-axis in V1 charts.


Created with:
  gclient setdep -r src/third_party/catapult@4925b069e1cf

The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-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_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel

BUG=chromium:902796,chromium:886940
TBR=sullivan@chromium.org

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

The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-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:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast
TBR=cr-fuchsia+bot@chromium.org

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

We were previously only updating the layout sizes used
for the browser compositor layouts, but not the underlying
web contents.

BUG=905270

Change-Id: I1f36a46db4bf5f83e6adc8dce75551a059ec7b57
Reviewed-on: https://chromium-review.googlesource.com/c/1335952
Commit-Queue: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608136}

This will help identify which case has a null callback.
See: crash/b2f5fa086babf323

Bug: 889972
Change-Id: Ife0279dbb07fc0c2201981b70796c365d49ea36e
Reviewed-on: https://chromium-review.googlesource.com/c/1334547Reviewed-by: Nathan Parker <nparker@chromium.org>
Commit-Queue: Varun Khaneja <vakh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608135}

https://chromium.googlesource.com/angle/angle.git/+log/fca8fd620190..ccad5e333472


git log fca8fd620190..ccad5e333472 --date=short --no-merges --format='%ad %ae %s'
2018-11-14 geofflang@chromium.org GL: Work around driver returning negative GL_MAX_SERVER_WAIT_TIMEOUT
2018-11-14 syoussefi@chromium.org Vulkan: Implement EXT_texture_filter_anisotropic


Created with:
  gclient setdep -r src/third_party/angle@ccad5e333472

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

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

When the browser starts in Kiosk mode, it should enter into full screen
mode without top Chrome UI. This CL fixes this, and also re-enables a
browser test that relied on this behavior.

BUG=470724

Change-Id: Icb043b1000d29908c7f4114c327c1d7355585bd4
Reviewed-on: https://chromium-review.googlesource.com/c/1334942
Commit-Queue: Wei Li <weili@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608133}

Bug: 881076
Change-Id: I41d7f87d46225ebc919473e8bd165268d699e45e
Reviewed-on: https://chromium-review.googlesource.com/c/1334411
Commit-Queue: Sorin Jianu <sorin@chromium.org>
Reviewed-by: Minh Nguyen <mxnguyen@chromium.org>
Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608132}

--hash-style=gnu can be moved into the common shared library template.
While merging these, I noticed that one instance uses mips64el, while
the other uses mipsel64.  This is suspect.

BUG=

Change-Id: I09e8db4f4c049da69a96f9afd442f2dbd5296252
Reviewed-on: https://chromium-review.googlesource.com/c/1331632Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org>
Reviewed-by: David Turner <digit@chromium.org>
Commit-Queue: Christopher Grant <cjgrant@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608131}

Bug: None
Change-Id: Iaf37dc41d24d3fb28d0f26ceab8691145126a019
Reviewed-on: https://chromium-review.googlesource.com/c/1334292Reviewed-by: Cait Phillips <caitkp@chromium.org>
Reviewed-by: Moe Ahmadi <mahmadi@chromium.org>
Commit-Queue: Mathieu Perreault <mathp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608130}

Fixes a theoretical race where tracing could be stopped and immediately
started again, and as we PostTask the destruction of the tracing session
in theory the new tracing session could be destroyed rather than
the old one.

R=eseckler@chromium.org

Bug: 900920
Change-Id: I2763100bb0915718cf1f1f0f685172d12fc24600
Reviewed-on: https://chromium-review.googlesource.com/c/1335953
Commit-Queue: Eric Seckler <eseckler@chromium.org>
Reviewed-by: Eric Seckler <eseckler@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608129}

Previously, the code would create a set from all the known
flags and compare the specified flags against them.

But actually this is less efficient than just the O(n*m) search,
because n being the number of flags set by the user and m being
the number of available flags, since n will likely be small or 0
and then we don't need to do a lot of work. In particular, this
also avoids copying a bunch of strings.

Bug: 904575
Change-Id: I63e59d439c432338aea71eb6258e8f8b42f04921
Reviewed-on: https://chromium-review.googlesource.com/c/1334413
Commit-Queue: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: ssid <ssid@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608128}

Rather than only forwarding USB requests to the Windows WebAuthn API,
we are going to forward all requests. This consequently renames the
FidoAuthenticator subclass to WinWebAuthnApiAuthenticator. The
corresponding FidoDiscovery is instantiated for all requests where the
WebAuthn API is available (i.e., the feature is flag enabled, and the
DLL can be loaded and is at least version 1). When it is indeed
available, all other discoveries are disabled and the UI is suppressed
via a newly introduced option in the TransportAvailabilityInfo struct
relayed to embedders via the TransportAvailabilityObserver interface.

Note this temporarily breaks caBLE whenever the Windows API is
flag-enabled and available. (But the OS would presumably block the
device communication in that case anyway.)

Bug: 898718
Change-Id: If2bddac4bac519d1aa5aa9cb5d8fdc326297de73
Reviewed-on: https://chromium-review.googlesource.com/c/1330897
Commit-Queue: Martin Kreichgauer <martinkr@chromium.org>
Reviewed-by: Jun Choi <hongjunchoi@chromium.org>
Reviewed-by: Adam Langley <agl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608127}