GitLab

Previously when starting subprocesses test launcher would clone
some namespace dirs, but not all of them. Update test launcher to use
fdio_ns_export_root() to get namespace of the current process so the
child process can get complete namespace clone, except for /data that
needs to be overridden.

Change-Id: I0e49aa12a4a98e036acdf6549252478e6c771936
Reviewed-on: https://chromium-review.googlesource.com/c/1351888
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Wez <wez@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611815}

SafeCast a sequence to int in bindings.
Add explicit cast in heap_page.h

BUG=879657

Change-Id: I1c6cf9b1748b84795ed81d903e3e19684bd6d0e3
Reviewed-on: https://chromium-review.googlesource.com/c/1354062Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611814}

This reverts commit 5fd55b4b.

Reason for revert: I am fairly certain this is causing static initializer check failures on the official builder, because it changes BookmarkItem to be a non-POD type, and there are static BookmarkItem constants in the build: https://crbug.com/909828 

Original change's description:
> Navi: Localize Google Apps strings.
> 
> Bug: 894499
> Change-Id: I698b51eac47cdb7af63e4bb2ace338f87c5e7493
> Reviewed-on: https://chromium-review.googlesource.com/c/1351779
> Reviewed-by: Scott Chen <scottchen@chromium.org>
> Commit-Queue: Hector Carmona <hcarmona@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#611759}

TBR=hcarmona@chromium.org,scottchen@chromium.org

Change-Id: I72aff79d75c2c578c509bf4525d120c0e402cc17
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 894499
Reviewed-on: https://chromium-review.googlesource.com/c/1352682Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#611813}

Bug: 462296
Change-Id: I14fade7b9324f869192c4131d2d41d282278d85a
Reviewed-on: https://chromium-review.googlesource.com/c/1352536Reviewed-by: Alex Newcomer <newcomer@chromium.org>
Commit-Queue: Weidong Guo <weidongg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611812}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/da575ec6b7fc..dbc542d5f0f3


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

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: Ic4699b49a79f91b99ff25da701ab450b90184505
Reviewed-on: https://chromium-review.googlesource.com/c/1352807Reviewed-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@{#611811}

This commit is an intermediate commit on the path to adding support
for IETF QUIC's STREAM_ID_BLOCKED frame and MAX_STREAM_ID frame.
This is an intermediate/safety commit while working on a test issue.

R=rch@chromium.org

Change-Id: Ie2c24114cb62b640beb31252ee4c216f08b59533
Reviewed-on: https://chromium-review.googlesource.com/c/1344197Reviewed-by: Ryan Hamilton <rch@chromium.org>
Commit-Queue: Frank Kastenholz <fkastenholz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611810}

Adds flags to clear and add to the local blacklist. These flags are
evaluated on startup.

These flags are needed for Chrome Driver testing.

Bug: 908491
Change-Id: Id67f9393d826c9e6bd267eb8ac39dc1118a4bce7
Reviewed-on: https://chromium-review.googlesource.com/c/1351880Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Commit-Queue: Robert Ogden <robertogden@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611809}

It's possible for a new Intent with the same WebContents, but
different values for mutable parameters like enableTouchInput.
When this happens, the WebContents would be reinitialized, which
breaks an assertion in WebContentsImpl.

By storing the WebContents in a separate Controller, we allow it
to persist across a reactivation of mStartParamsState where the
new WebContents is equal to the previous instance.

Bug: internal b/120089917
Test: cast_shell_junit_tests
Change-Id: Id9d58b577a887ffff4002ec6fcde578a71752b1f
Reviewed-on: https://chromium-review.googlesource.com/c/1352077
Commit-Queue: Simeon Anfinrud <sanfin@chromium.org>
Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611808}

Changing InkDropGestureHandler to InkDropEventHandler to
unconditionally handle mouse events in addition to gesture events for
ink drops.
This makes the ink drop less error prone as previously InkDropHostView
depended on parents to call InkDropHostView::OnMouseEvent after
handling it themselves

Bug: 901183
Change-Id: Iee9c259b44d1057b2ba5d0c81b29602c9f6b77a4
Reviewed-on: https://chromium-review.googlesource.com/c/1344262
Commit-Queue: Charlene Yan <cyan@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Reviewed-by: Peter Boström <pbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611807}

This reverts commit 65453a44.

Reason for revert: broke the build: https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8928590708886404784/+/steps/compile/0/stdout

Original change's description:
> [MacOS Host] Fixing a memory leak in the alert dialog
> 
> Follow-up CL fixing a leak identified post check-in.
> 
> Bug: 902041
> Change-Id: Ic900c107f13185fa8c823163b2278990ed543ff2
> Reviewed-on: https://chromium-review.googlesource.com/c/1352030
> Reviewed-by: Robert Sesek <rsesek@chromium.org>
> Commit-Queue: Joe Downing <joedow@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#611777}

TBR=joedow@chromium.org,rsesek@chromium.org

Change-Id: I346b4a43995959ce2c289d5f2ff31feb722b4233
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 902041
Reviewed-on: https://chromium-review.googlesource.com/c/1354231Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#611806}

Add grouped audio focus. This means that a media session
can provide an unguessable token when requesting audio
focus. This means that the media session service will
treat all media sessions with the same group id as the
same session when it comes to audio focus.

BUG=906285

Change-Id: I184f8de58cfe3cec67db0bb5877f3b352c794f13
Reviewed-on: https://chromium-review.googlesource.com/c/1342939
Commit-Queue: Becca Hughes <beccahughes@chromium.org>
Reviewed-by: Chrome Cunningham <chcunningham@chromium.org>
Reviewed-by: Tommy Steimel <steimel@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611805}

TabObserverRegistrar adds observers to a static ObserverList in
PageLoadMetrics, and removes them when receiving callbacks about the tab:
didCloseTab or tabRemoved. These callbacks don't get called if the
activity is killed in background, thus a memory leak. It doesn't happen
though when activity is killed via back button, the reasons for that
boil down to different values of mIsClosing boolean in CustomTabActivity.
But we shouldn't rely on such details of other classes and do explicit
cleanup in destroy() method of each class.

Change-Id: I46138b02a3cbb81a5b82e5dc6499ebbef75bb817
Reviewed-on: https://chromium-review.googlesource.com/c/1353931Reviewed-by: Peter Conn <peconn@chromium.org>
Commit-Queue: Pavel Shmakov <pshmakov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611804}

known issues:
 * skia doesn't support GL_RG8 format uv texture.
 * gpu::GetGrBackendTexture() doesn't support GL_R8 and GL_RG8
   formats.


Bug: 908842
Change-Id: Ice3ffa1135a5b9fdbbb69bcb8175c5f9e196e778
Reviewed-on: https://chromium-review.googlesource.com/c/1347108Reviewed-by: weiliangc <weiliangc@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611803}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/03ba418f..dad75d09

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: I011f908680dac90227732ea061759bea04c77200
Reviewed-on: https://chromium-review.googlesource.com/c/1354122Reviewed-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@{#611802}

NOTE TO CHROMIUM SHERIFF:
  If Tracing unittests are flaky, please revert this CL and ping me.

Change-Id: Ia4a6a57e190afd82eec4b133ce8e1f33bc6c1f0f
Reviewed-on: https://chromium-review.googlesource.com/c/1349495
Commit-Queue: Etienne Bergeron <etienneb@chromium.org>
Reviewed-by: oysteine <oysteine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611801}

R=ochang@google.com

Bug: 907103
Change-Id: I6a6f7f6eb33574e415d71ee72c35a2eecfa22c87
Reviewed-on: https://chromium-review.googlesource.com/c/1352827Reviewed-by: Eric Roman <eroman@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Reviewed-by: Albert J. Wong <ajwong@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Oliver Chang <ochang@chromium.org>
Reviewed-by: Ryan Hamilton <rch@chromium.org>
Reviewed-by: Noel Gordon <noel@chromium.org>
Reviewed-by: Max Moroz <mmoroz@chromium.org>
Commit-Queue: Abhishek Arya <inferno@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611800}

This CL fixes crash in notifications settings page. This is reproduced on
devices where multidevice features are disabled by policy. In this case
MultiDeviceSetupClient is not instantiated, causing the look up for
android messages info in the notifications settings page to crash. This
was fixed by guarding the look up by a loadtime value that indicates
whether multidevice features are allowed policy or not.

Bug: 905908
Change-Id: Ic637768802e4e15b3643fe20dcc40d1bb3cea9da
Reviewed-on: https://chromium-review.googlesource.com/c/1345729
Commit-Queue: Azeem Arshad <azeemarshad@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Jeremy Klein <jlklein@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611799}

https://boringssl.googlesource.com/boringssl/+log/6965d25602754bc419c5f757d008ba1f4da49ae4..0f5ecd3a854546d943104e1f7421e489b7f4d5aa

Bug: none
Change-Id: I047aef10bbd47bf50c567d2d22c250aae5fabf85
Reviewed-on: https://chromium-review.googlesource.com/c/1351138
Commit-Queue: David Benjamin <davidben@chromium.org>
Reviewed-by: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611798}

When overview and splitview are both active, tab dragging might cause
the misplacement of the divider bar, see the bug description for
details. The reason is that in tab dragging, it's possible the window
gets activated between the drag ends and window snap, this CL makes sure
this case is also properly handled.

Bug: 908992
Change-Id: I767504153b153f3325dfce9212c647e5f390c0c9
Reviewed-on: https://chromium-review.googlesource.com/c/1352412
Commit-Queue: Xiaoqian Dai <xdai@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611797}

In the initial version, the calculation crashes when it tries to intersect the
object's rect with the viewport's rect for certain values. It's because
intersect indicates a calculation of maxX = x + width, which has overflow issue
when x and width is very big.

To fix this issue, the sizes of each rect in intersect must do saturated
arithmetic.

Bug: 908974
Change-Id: Ida184dd69dfa0008d7c878e292ab908b1536f7ba
Reviewed-on: https://chromium-review.googlesource.com/c/1352570Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Liquan (Max) Gǔ <maxlg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611796}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/d2ede8935345..e7e7a29184f5


git log d2ede8935345..e7e7a29184f5 --date=short --no-merges --format='%ad %ae %s'
2018-11-28 chrome-bot@chromium.org Update config settings by config-updater.


Created with:
  gclient setdep -r src/third_party/chromite@e7e7a29184f5

The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-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=chrome-os-gardeners@chromium.org

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

Bug: 900603
Change-Id: If567eedb4071af1d53072bad81c10731c4515fa0
Reviewed-on: https://chromium-review.googlesource.com/c/1353998
Commit-Queue: oysteine <oysteine@chromium.org>
Reviewed-by: oysteine <oysteine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611794}

Bug: 909799
Change-Id: I9fdeec4f569d7ee272f8a384012fec3a201908eb
Reviewed-on: https://chromium-review.googlesource.com/c/1354220Reviewed-by: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#611793}

This patch mimics the style code in that it tries not to propagate the
invalidation up the container chain if the element is locked for display

When the lock commits and the element needs layout, then it marks
the ancestor chain so that the code can reach it in layout.

R=chrishtr@chromium.org, mstensho@chromium.org

Bug: 882663
Change-Id: I499e91e6a14f61e5dfbeae74d3c93ac8b321e944
Reviewed-on: https://chromium-review.googlesource.com/c/1344825Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611792}

APIs that have Ash dependencies can only run on ChromeOS so bind them
only when building for ChromeOS. This allows EXO to build on Chromecast.

Bug: 896710
Test: None
Change-Id: I60acf956b5a0f682f89c97b5818bb54cefcc7113
Reviewed-on: https://chromium-review.googlesource.com/c/1328702Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Commit-Queue: Daniel Nicoara <dnicoara@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611791}

Bug: 903983
Change-Id: If4a6bdd236a82267e4b8302992dc9c0d3b3a8cc0
Reviewed-on: https://chromium-review.googlesource.com/c/1344908
Commit-Queue: Sky Malice <skym@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Reviewed-by: Filip Gorski <fgorski@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611790}

This CL lets FindInPage support searching over multiple HTML Nodes, and
adds a unittest case for that.

Bug: 228585
Change-Id: Iec2715034bebb36afcf9160e2bad6c4276ca8008
Reviewed-on: https://chromium-review.googlesource.com/c/1352153
Commit-Queue: Yi Su <mrsuyi@chromium.org>
Reviewed-by: Peter Lee <pkl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611789}

Removing unused histogram value:

  WebCore.IndexedDB.LevelDB.Transaction.CommitTime

Bug: 902193
Change-Id: I0274825b6ca8a289e86166b070bfba68382b87fd
Reviewed-on: https://chromium-review.googlesource.com/c/1351484
Commit-Queue: Chris Mumford <cmumford@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Reviewed-by: Brian White <bcwhite@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611788}

Bug: 898868
Change-Id: I067bf23c3838c6a7576dc91b090f79c12ce798ea
Reviewed-on: https://chromium-review.googlesource.com/c/1351427Reviewed-by: Mohammad Reza Zakerinasab <zakerinasab@chromium.org>
Commit-Queue: Fernando Serboncini <fserb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611787}

After this change there are no more callers. The next cl will remove the implementations of that
method.

Bug: 908955
Change-Id: Ie424e9d6be5d6bb8702962198c61e718968ac2a7
Reviewed-on: https://chromium-review.googlesource.com/c/1352510Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611786}

This patch implements touch-action rects in composite-after-paint by
generalizing the ScrollingCoordinator UpdateLayerTouchActionRects
function to work with both SPV1 and SPV2.

Several tests are failing due to cc::Layer::position being zero,
though the touch-action rects are correct. Expectation entries have
been added for these.

This patch also reorders some lines in internals.h. This was found in
the review of http://crrev.com/611376 but was mistakenly left out when
the patch landed.

Bug: 909749

Change-Id: I9d66ebdfef25d46388ce5740121a7b4844de1ca5
Reviewed-on: https://chromium-review.googlesource.com/c/1351802
Commit-Queue: Philip Rogers <pdr@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611785}

https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/703305b1a5a2..3ee605d7ccb9


git log 703305b1a5a2..3ee605d7ccb9 --date=short --no-merges --format='%ad %ae %s'
2018-11-28 zoddicus@users.noreply.github.com Ensure that only whitelisted extensions are used in WebGPU (#2127)


Created with:
  gclient setdep -r src/third_party/SPIRV-Tools/src@3ee605d7ccb9

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: I4388244673ad41cef1c8e72be31a15252d393815
Reviewed-on: https://chromium-review.googlesource.com/c/1352802Reviewed-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@{#611784}

This CL removes ConsentBumpFragment and ConsentBumpMoreOptionsFragment
and the code that was only used by these fragments.

Bug: 909649
Change-Id: Id9be789a5542ecc9d0f73581801bf7eaaf0426a3
Reviewed-on: https://chromium-review.googlesource.com/c/1352781Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Boris Sazonov <bsazonov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611783}

https://chromium.googlesource.com/catapult.git/+log/17079a5cc1f2..6457c042bc7b


git log 17079a5cc1f2..6457c042bc7b --date=short --no-merges --format='%ad %ae %s'
2018-11-27 bpastene@chromium.org devil: When setting flags on the device, log the file location.
2018-11-27 perezju@chromium.org [soundwave] Finish merging soundwave.dashboard_api into dashboard_service
2018-11-27 perezju@chromium.org [soundwave] Move timeseries (v1) API to dashboard_services
2018-11-26 eyaich@google.com Create method to add shared diagnostics to histograms not created through tbmv2


Created with:
  gclient setdep -r src/third_party/catapult@6457c042bc7b

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:907899,chromium:890691,chromium:890691,chromium:714231
TBR=sullivan@chromium.org

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

When a SecureChannel disconnects due to authentication failures,
BleConnectionManagerImpl invokes the relevant failure callback, which
then causes ConnectionAttemptBase to cancel the connection attempt.

When the attempt is cancelled, the SecureChannel object is deleted via
BleConnectionManagerImpl::ProcessPotentialLingeringChannel(), but
BleConnectionManagerImpl::HandleSecureChannelDisconnection() assumed
that the object was still valid and tried to to remove itself as an
observer, causing a segfault.

The fix is to check whether the object has been deleted before
attempting to call RemoveObserver().

Bug: 905904
Change-Id: Ic593ef4047ff481e218c89028324eb0863131cdc
Reviewed-on: https://chromium-review.googlesource.com/c/1352855Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611781}

Currently ash_perftests fails to build due to undefined symbol
errors of keyboard::mojom::KeyboardConfig::KeyboardConfig() in
ash/public/cpp/test/test_keyboard_controller_observer.cc

Bug: none
Test: autoninja ash_perftests
Change-Id: Ib6c8ecd34295269ee27a1f63eb62f2c7a582f006
Reviewed-on: https://chromium-review.googlesource.com/c/1352044Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Jun Mukai <mukai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611780}

This CL fixes the Settings EG tests by calling [super tearDown].
It also fixes the Autofill profile tests by scrolling the view if
needed to find the element. This is because the new cells are slightly
bigger and not fully displayed now.

Bug: 909765
Change-Id: Ia8aae51529da054d902c11b3d640dcc344532943
Reviewed-on: https://chromium-review.googlesource.com/c/1353930Reviewed-by: edchin <edchin@chromium.org>
Commit-Queue: Gauthier Ambard <gambard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611779}

This change prevents unhighlighting if the anchor button has not changed. Highlighting was added to a button when a widget is anchored to that button. On entering fullscreen, a widget's anchor is reset regardless of whether it was changed. This would unhighlight then rehighlight the button but only be noticable on Mac.

Bug: 905992
Change-Id: I4989a45101c704105f5b4a572e028c851b6165b7
Reviewed-on: https://chromium-review.googlesource.com/c/1351106
Commit-Queue: Caroline Rising <corising@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611778}

Follow-up CL fixing a leak identified post check-in.

Bug: 902041
Change-Id: Ic900c107f13185fa8c823163b2278990ed543ff2
Reviewed-on: https://chromium-review.googlesource.com/c/1352030Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611777}

Delete three policies that causes issue or confusion on Admin Console.
ReportMachineIDData
ReportUserIDData
ReportVersionData

Remove policy migrator as it's not used by local reporting and
cloud reporting policies are going to be decoupled from the extension
policies.

Tbr: karandeepb@chromium.org
Change-Id: I5fcfa665aee3899dbd0d446427af2c4821de13fc
Reviewed-on: https://chromium-review.googlesource.com/c/1351288
Commit-Queue: Owen Min <zmin@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611776}