GitLab

This CL records touch action rects for TablePainter. A layout
test is added to ensure its correctness.

Bug: 851674
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ic82e47898ed2b1bf97955dc7fffcf86d9eb7c7e3
Reviewed-on: https://chromium-review.googlesource.com/1213535Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589737}

Before this CL, the ranking order is:
1) visible main frame
2) visible subframe in viewport
3) visible subframe outside of viewport
4) invisible main frame
5) invisible subframe in viewport
6) invisible subframe outside of viewport

This CL moves 4) above 3).

This complicates the comparison algorithm quite a bit, since it's no
longer ok to compare fields independently.

Expand testRanking to cover all cases in the list above.
Also make failures in unit test easier to debug by using
assertArrayEquals.

Bug: 855037
Change-Id: I4aa1c785fcdb6978cfeca9bf8e6989dd6d3153ea
Reviewed-on: https://chromium-review.googlesource.com/1213924Reviewed-by: Siddhartha S <ssid@chromium.org>
Commit-Queue: Bo <boliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589736}

Bug: 868213
Change-Id: Ic990e6dd681159e7c214bfbba54a460c56bb0588
Reviewed-on: https://chromium-review.googlesource.com/1214563Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Commit-Queue: Ryan Tseng <hinoka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589735}

TBR=smut

Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: I189b8ef718f2be0a9591c8914c39d87ee70ebaed
Reviewed-on: https://chromium-review.googlesource.com/1214382
Commit-Queue: iOS Autoroller <ios-autoroller@chromium.org>
Reviewed-by: iOS Autoroller <ios-autoroller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589734}

1 - Fixed empty view being chopped off
2 - Hooked up PrefetchStatusProvider to the value of feature

Bug: 882011
Change-Id: Ic4e89a4720b52da84b433092d1de7ace702b431a
Reviewed-on: https://chromium-review.googlesource.com/1213520Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: Shakti Sahu <shaktisahu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589733}

In Polymer 2 the following syntax for registering event listeners
is no longer supported.

listeners: {
  'id.eventName': 'onEventName_',
},

Instead the listener must be added either programmatically, or
declaratively directly on the |id| element.

Bug:875470

Change-Id: I84f1d61b9b669dda1922f6c8d5f2bbc8de211c1c
Reviewed-on: https://chromium-review.googlesource.com/1213380Reviewed-by: Esmael El-Moslimany <aee@chromium.org>
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589732}

Array.p.sort does not expect comparator result of BigInt.

BUG=881884

Change-Id: I3215e4dab8dcfc1e4e830cebf07d1dcf674d0d2e
Reviewed-on: https://chromium-review.googlesource.com/1213928Reviewed-by: Erik Luo <luoe@chromium.org>
Commit-Queue: Alexei Filippov <alph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589731}

It is the initial implementation of UMA heap profiles collection controller.
Profile collection is performed periodically at random moments in time
distributed according to Poisson stream with the intensity of one profile
per 24 hours.

By default the profile collection and reporting is turned off.
It can be enabled with the flag:
--sampling-heap-profiler[=<sampling interval in KB>]
If the interval is not specified the default value of 128KB is used.

Also it can be enabled by a Finch experiment named "SamplingHeapProfiler".
It has a single parameter "sampling-rate-kb" which defaults to 128KB.

Profiles are reported via the same pipeline and format we currently
report CPU profiles.
The only difference is the trigger event for heap profiles is
PERIODIC_HEAP_COLLECTION.

BUG=878604

Change-Id: I172de2c02f41c5d2a073d33d10267fcdc2fdf3a8
Reviewed-on: https://chromium-review.googlesource.com/1194978Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Mike Wittman <wittman@chromium.org>
Commit-Queue: Alexei Filippov <alph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589730}

This CL modifies the media intent handler enabling logic to also enable
devices that are enterprise-managed.

This CL also moves MediaViewerUtils.updateMediaLauncherActivityEnabled
code into an AsyncTask to avoid the need for disk reads/writes on the
main thread.

Bug: 879647
Change-Id: I29794f2b0ac18e8ce65763c07c4a35b7c8607b8a
Reviewed-on: https://chromium-review.googlesource.com/1200405
Commit-Queue: Tommy Steimel <steimel@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589729}

Previously, the BackgroundVideoTrackOptimization flag was used to
control both src= and MSE videos. MSE videos has been fully decoupled
from the flag now. This CL also uses max_keyframe_distance as a fixed
value, determined by the previous finch experiment on MSE videos.

The chrome://flags entry is also being removed in preparation for the
experiment and (most likely) subsequent enabling of the feature.

Bug: 709302
Change-Id: I3875fc700ceb569da7a7c4fa39b28d938235e6a8
Reviewed-on: https://chromium-review.googlesource.com/1194794
Commit-Queue: Ted Meyer <tmathmeyer@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589728}

On the GmsCore side, EASY_UNLOCK_HOST is blacklisted from being
automatically disabled when BETTER_TOGETHER_HOST is disabled. This is
done to prevent CryptAuth from losing the enabled status of EasyUnlock
on host devices that have grandfathered-in EasyUnlock support. In order
to disable EasyUnlock, it must be done so explicitly. Therefore, when
the user chooses to manually disable all Better Together features via the
"Forget this device" button in Chrome OS or a comparable method on Android,
EASY_UNLOCK_HOST should be explicitly disabled in addition to
BETTER_TOGETHER_HOST.

  - before this change, EASY_UNLOCK_HOST was *not* disabled when "Forget
    this device" button was used, and
  - after this change, EASY_UNLOCK_HOST *was* disabled when "Forget this
    device" button was used.

Bug: 881612
Change-Id: If1f1898a8942f9c42a0f5cceb20095ad1ef087d5
Tested: Manually verified that when EASY_UNLOCK_HOST is blacklisted,
Reviewed-on: https://chromium-review.googlesource.com/1212742Reviewed-by: Jeremy Klein <jlklein@chromium.org>
Commit-Queue: Josh Nohle <nohle@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589727}

- Remove separate screen handlers
- Share screen handler with the OOBE screen handler

Bug: b/114310423
Test: Manual Test
Change-Id: I43ce2c88ef53f03f846b7598a9a02b9c4d1511a2
Reviewed-on: https://chromium-review.googlesource.com/1212446
Commit-Queue: Yue Li <updowndota@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589726}

While Chrome checks both the 32- and 64-bit registries to discover
native messaging hosts, Firefox only checks the native registry. This
poses a challenge, as 32-bit installers generally aren't allowed to
install 64-bit components (such as registry keys). However, it turns out
that it is possible to suppress the resulting error, and this CL does
just that, allowing the required keys to be installed in the native
registry on 64-bit Windows.

Bug: 880542
Change-Id: I2552d24ec7dd2e7cce8febdc42b048a1e5caf568
Reviewed-on: https://chromium-review.googlesource.com/1213956
Commit-Queue: Erik Jensen <rkjnsn@chromium.org>
Reviewed-by: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589725}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/1cefd62ebe68..aca984cbf105


git log 1cefd62ebe68..aca984cbf105 --date=short --no-merges --format='%ad %ae %s'
2018-09-07 cwallez@chromium.org Add test for a weirdness of gclient use_relative_paths and recurse_deps
2018-09-07 tandrii@chromium.org Make ehmaldonado top level OWNER.
2018-09-07 martiniss@google.com `git cl split`: Fix typos in cq_dry_run code
2018-09-07 cwallez@chromium.org gclient_test: use write() for hook tests
2018-09-07 nodir@google.com [bot_update] Pass git_repo param in test
2018-09-07 nodir@google.com Update tryserver to use buildbucket.build.input.gerrit_changes


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

The AutoRoll server is located here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.



BUG=chromium:878117,chromium:694348
TBR=agable@chromium.org

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

remove skip for fast/js/string-prototype-properties.html and fast/js/date-proto-generic-invocation.html

Bug: v8:7961,v8:7958
Change-Id: Ib71d4084c850824b73c834997683d446f7b62781
Reviewed-on: https://chromium-review.googlesource.com/1212702Reviewed-by: Jungshik Shin <jshin@chromium.org>
Commit-Queue: Frank Tang <ftang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589723}

The code used to assume that a keyboard device name
must include the string "keyboard" in it.
CL at crrev.com/c/1074336 built on this wrong assumption
to detect whether to show external keyboard key remap
settings in the system keyboard settings.

This CL fixes this assumption.

BUG=1074336
TEST=manually, unit test.

Change-Id: I174173097e6da0159c655f724690060ebe74529a
Reviewed-on: https://chromium-review.googlesource.com/1214322Reviewed-by: Kevin Schoedel <kpschoedel@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589722}

Bug: 881212
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: I02462453e8f62286861c9e299d4c7a5dde612666
Reviewed-on: https://chromium-review.googlesource.com/1213877Reviewed-by: Thomas Guilbert <tguilbert@chromium.org>
Commit-Queue: Dan Sanders <sandersd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589721}

This CL introduces the skeleton UI code for OfflineItems.
see https://docs.google.com/document/d/1xDRCoDYnOb9PvwJ8juSmG75jsE-YKzNomCMaoFtQWtQ/edit#

BUG=881499

Change-Id: Ie31f6bcc77c65a4343f2e5a0be54f3b9b5fdd5bc
Reviewed-on: https://chromium-review.googlesource.com/1211445
Commit-Queue: Min Qin <qinmin@chromium.org>
Reviewed-by: Shakti Sahu <shaktisahu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589720}

Connect selecting a script in the UI with the native side so that it can
be routed to the executor.

R=gogerald@chromium.org, szermatt@chromium.org

Bug: 806868
Change-Id: Icf85027c2e50a073d805dbcb3e99017ce66b5850
Reviewed-on: https://chromium-review.googlesource.com/1206373Reviewed-by: Ganggui Tang <gogerald@chromium.org>
Commit-Queue: Ganggui Tang <gogerald@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589719}

Bug: 877984
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: Idcecd7ba8d49fa8045483f7b2309c3e3eecb3b92
Reviewed-on: https://chromium-review.googlesource.com/1211670
Commit-Queue: Mohammad Refaat <mrefaat@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589718}

This enables callers to avoid doing it themselves (centralizing the `memset` in
1 place, rather than duplicating it at every call site that wants it), and to
allow the PartitionAlloc implementation to avoid doing it itself if the
operating system has already zero'd the new page(s).

This is a re-land, with fixes, of
https://chromium-review.googlesource.com/c/chromium/src/+/1162825.

Bug: 864462,680657
TBR: ajwong,haraken
Change-Id: Icfe05bca82c79c8a8029db40b2902271d3d10347
Reviewed-on: https://chromium-review.googlesource.com/1214173Reviewed-by: Chris Palmer <palmer@chromium.org>
Commit-Queue: Chris Palmer <palmer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589717}

https://skia.googlesource.com/skia.git/+log/24de64834600..24e8f58cfa9c


git log 24de64834600..24e8f58cfa9c --date=short --no-merges --format='%ad %ae %s'
2018-09-07 swiftshader-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/swiftshader a062f321768d..3655209d86f4 (1 commits)
2018-09-07 reed@google.com Revert "Revert "add flag to soften the blow of removing a legacy api for flutter""
2018-09-07 bsalomon@google.com Preseve tangents when converting cubics->quads in GrAAHairlinePathRenderer
2018-09-07 borenet@google.com [infra] Revert broken recipe rolls, add test for missing patch_ref
2018-09-07 brianosman@google.com Add support for gray + colorspace to SkCodec
2018-09-07 bungeman@google.com Simplify FreeType glyph bounds.
2018-09-07 caryclark@google.com reland fix picture subclass destructor doc
2018-09-07 mtklein@google.com add clamp_gamut
2018-09-07 jvanverth@google.com Revert "add flag to soften the blow of removing a legacy api for flutter"
2018-09-07 borenet@google.com Add new autoroll service accounts to AUTHORS check bypass
2018-09-07 mtklein@google.com remove -k 0 from builds


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

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

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;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:847759
TBR=jvanverth@chromium.org

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

This is to avoid a sequence checker debug error.

BUG=b/113298882
TEST=Manually tested on Linux workstation simulator.

Change-Id: I07b43e315335bf95e67b4567aedd4b7466cc5391
Reviewed-on: https://chromium-review.googlesource.com/1213950Reviewed-by: Nicholas Verne <nverne@chromium.org>
Commit-Queue: Tim Zheng <timzheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589715}

Ensures that a preview is not shown when the previews server cannot be
reached.

Bug: 864656
Change-Id: I417e7988bce7509ddbc31dfadfd48d91f1434e16
Reviewed-on: https://chromium-review.googlesource.com/1213664Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Commit-Queue: Robert Ogden <robertogden@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589714}

This reverts commit f79adf2a.

Reason for revert: The ChromeLauncherControllerWithArcTest.ArcCustomAppIcon test is failing repeatedly on the linux-chromeos-rel bot:

https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/linux-chromeos-rel

Starting with build 13071:

https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/linux-chromeos-rel/13071

Original change's description:
> arc: Fix shelf item icon flickering on app start.
> 
> When app is pinned, icon image is loaded via controller using loader
> owner by chrome launcher controller. Once new ARC app window appears in
> the system, it's icon is loaded asynchronously. In this flow, default
> app icon is applied first and then, once real image is loaded final icon
> is set. Each update of ARC window icon is reflected on shelf. That
> means default app icon appear on the shelf for a moment and in most cases
> this is very noticeable.
> This CL prevents setting default app in favor of final app icon and
> default icon is set only as a fallback when final icon could not be
> loaded.
> 
> TEST=Manual
> BUG=b:114246197
> 
> Change-Id: I2de9e9d99b313f7538dce9dd732164335f32a42a
> Reviewed-on: https://chromium-review.googlesource.com/1212348
> Commit-Queue: Yury Khmel <khmel@google.com>
> Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#589627}

TBR=xiyuan@chromium.org,khmel@google.com

Change-Id: I1005d78330dc87b1ce0a925d05d6df48cb68b9ad
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: b:114246197
Reviewed-on: https://chromium-review.googlesource.com/1213953Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Commit-Queue: Justin Donnelly <jdonnelly@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589713}

This CL adds support to observe the first time an <img> element paints
via the PerformanceObserver (no support for performance timeline yet)
and under a flag that is disabled by default.

Implementation proposal:
https://docs.google.com/document/d/1BvHknbj3T-fUuj4RxHF8qGRNxbswtBqUjKiPx7iLXCc

Intent to Implement:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/2twP4Xdd1VI

Bug: 879270
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I715bd71be088f8055ece493db208caa9b97d736b
Reviewed-on: https://chromium-review.googlesource.com/1197349
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Steve Kobes <skobes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589712}

This change modifies the current GetSharesInNetwork function so that a
callback is fired as soon a discovery is done to indicate that name
resolution is possible. Additionally, a new ShareFinder::DiscoveryHosts
method enables performing host discovery without querying each host for
its shares. This change will make it possible to perform name resolution
on reboot.

Bug: chromium:757625
Change-Id: I437ca8ad6400824a3fbc9b870b5fb0307cee2ac4
Reviewed-on: https://chromium-review.googlesource.com/1199685
Commit-Queue: Bailey Berro <baileyberro@chromium.org>
Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589711}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/3ee20bcf..6f64185a

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: I55b239a60848302d980d1accd3cdfdc70a6cdc53
Reviewed-on: https://chromium-review.googlesource.com/1214178Reviewed-by: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#589710}

Use WeakPtr instead of raw ptr for the callback used by
socket watchers when calling back into network quality
estimator.

Bug: 879071
Change-Id: I1f97fd391fe6b709c45dd87c242467d73ae36dfc
Reviewed-on: https://chromium-review.googlesource.com/1213932
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589709}

Bug: 880584
Change-Id: I6272bf7e5b99353a0b0b4f8e944747da7b83c944
Reviewed-on: https://chromium-review.googlesource.com/1214177Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Ryan Cui <rcui@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589708}

Using wpt-import in Chromium 821ebe6c.

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

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: If4240180a9804dfaea232f3c19cc714bb352c9d3
Reviewed-on: https://chromium-review.googlesource.com/1214067
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@{#589707}

This reverts commit 978c0e67.

Reason for revert: Breaks enrollment - it fails with this error:
"Oops! The system failed to authorize API access for this device."

Bug: 854101, 881867

Original change's description:
> Generify authentication during enrollment.
> 
> Add DMAuth class, that would be used during enrollment
> instead of individual tokens.
> 
> TBR: oshima@chromium.org
> Bug: 854101
> Change-Id: I150b9dd5a91c7ba37b14f6dffbaf62f8f00dbb8b
> Reviewed-on: https://chromium-review.googlesource.com/1194233
> Commit-Queue: Denis Kuznetsov <antrim@chromium.org>
> Reviewed-by: Sergey Poromov <poromov@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#588007}

TBR=antrim@chromium.org,oshima@chromium.org,poromov@chromium.org

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

Bug: 854101
Change-Id: I24b15104fb8e958832b83c7c32ce6bba990c7ab0
Reviewed-on: https://chromium-review.googlesource.com/1214224Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Commit-Queue: Maksim Ivanov <emaxx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589706}

https://chromium.googlesource.com/angle/angle.git/+log/d84b6737fa10..3b9680534909


git log d84b6737fa10..3b9680534909 --date=short --no-merges --format='%ad %ae %s'
2018-09-07 fjhenigman@chromium.org Clean up state in EGLDebugTest.
2018-09-07 jmadill@chromium.org Vulkan: Make ContextVk driver uniforms a dirty bit.
2018-09-07 jmadill@chromium.org Vulkan: Correct gl_FragCoord with default FBO.
2018-09-07 fjhenigman@chromium.org Fix ClearTest.RGB8WithMaskFramebuffer.


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

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

BUG=chromium:880495
TBR=fjhenigman@chromium.org

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

If mapping of a DLL into the sandboxed process is blocked then we unmap
it and return an "unsuccessful" status, but we left the DLL base-address
out-parameter set to a non-NULL value.

Reset the out-parameter to null when blocking a DLL, to ensure that
callers don't get confused into thinking the operation was successful.

This replicates the change from
https://chromium-review.googlesource.com/c/chromium/src/+/1211322 to
the ThirdPartyModulesBlocking implementation of NtMapViewOfSection().

Change-Id: I7c326a1c78870888c2141f24ae357d0f9be55a62
Reviewed-on: https://chromium-review.googlesource.com/1213561
Commit-Queue: Wez <wez@chromium.org>
Reviewed-by: Will Harris <wfh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589704}

R=gogerald@chromium.org

Bug: 806868
Change-Id: I1b7503c801916fb7bd7e0bcde2361f0bfd15d7cf
Reviewed-on: https://chromium-review.googlesource.com/1202205
Commit-Queue: Ganggui Tang <gogerald@chromium.org>
Reviewed-by: Ganggui Tang <gogerald@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589703}

Modify the function CanHandleToggleCapsLock: pressing any
redundant key will prevent triggering the Capslock shortcut.

In original code, pressing Alt + M + Search then releasing Alt
will trigger CapsLock. Because AcceleratorHistory will receive
Alt + Search when Search is pressed. The fact that key M is pr-
-essed is ignored.

R=afakhry@chromium.org

Bug: 789283
Test: ash unittests
Change-Id: Id359d11cda4562a0b90da97af6c3dde3faf33c53
Reviewed-on: https://chromium-review.googlesource.com/1199853
Commit-Queue: Andrew Xu <andrewxu@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589702}

Improve user experience by showing the "Start" page first, and the
"Password" page after, making for a less jarring experience.

Bug: 881610
Change-Id: I0a54c0d6c8b5ffc11e6bfdd2aba80adf6bab374d
Reviewed-on: https://chromium-review.googlesource.com/1214169Reviewed-by: Jeremy Klein <jlklein@chromium.org>
Commit-Queue: Ryan Hansberry <hansberry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589701}

In some instances, we receive a significant number of attribute changes within a short delay.

This change throws away attribute changes that generate the same output on the same target.

Test: manually on settings page. Verify that ChromeVox only announces the radio button once rather than > 30 times (and plays the radio button earcon 30 times).
Change-Id: I92127ad074b3a73ce269077cae6b69ba71f59c52
Reviewed-on: https://chromium-review.googlesource.com/1211972
Commit-Queue: David Tseng <dtseng@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589700}

Bug: 878975
Change-Id: If951e1f175c4103006845bda9bb740f2b2a6afc6
Reviewed-on: https://chromium-review.googlesource.com/1212090
Commit-Queue: Katie Dillon <kdillon@chromium.org>
Reviewed-by: Nate Chapin <japhet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589699}

The code in CompositorImpl currently assumes that only a single
CompositorImpl instance exists for an application in management
of the GPU process. This includes sending app foreground/background
state updates to the GPU process and to GpuDataManagerImpl. This is
a brittle assumption since the embedder can potentially create
multiple Compositor instances.
This CL uses the ApplicationStateListener to correctly detemine the
state of application.

Bug: 859723
Change-Id: Icdad848298f1cdd75995f496b2f0bdf70385336b
Reviewed-on: https://chromium-review.googlesource.com/1205202
Commit-Queue: vikas soni <vikassoni@chromium.org>
Reviewed-by: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589698}