GitLab

1) Support preview for updating the layout of the currently set
   wallpaper.

2) Updates the spec of the preview top bar based on new spec.

3) Support highlighting the offline wallpaper when device is
   not connected (similar to the old picker).

Bug: 836396, 835025
Change-Id: I0732bfa63efec6fa6baf4fabb253f7aa2f5bc9f3
Reviewed-on: https://chromium-review.googlesource.com/1089998
Commit-Queue: Wenzhao (Colin) Zang <wzang@chromium.org>
Reviewed-by: Oliver Chang <ochang@chromium.org>
Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568721}

This makes GetAssertionOperation decrypt the matching credential id
id into its UserEntity value and carry those values as well as the
credential id into the returned response. It was previously returning
incomplete responses.

Also fix the signature counter to 1, rather than 0, because webauthndemo
insists that the number be greater than 0.

Bug: 803842
Change-Id: I42e22ca9fb571ad6dea924bd765aa276d8c62d1a
Reviewed-on: https://chromium-review.googlesource.com/1103518
Commit-Queue: Martin Kreichgauer <martinkr@google.com>
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568720}

Tbr: geofflang@chromium.org
Bug: 854100
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: I36ec64561f48b12d04269a3b3c031496902292ab
Reviewed-on: https://chromium-review.googlesource.com/1107275Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568719}

https://chromium.googlesource.com/angle/angle.git/+log/4004ae0e033a..a914f7ff310d


git log 4004ae0e033a..a914f7ff310d --date=short --no-merges --format='%ad %ae %s'
2018-06-20 jiawei.shao@intel.com Use ShaderMap in Statemanager11 - Part II


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

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=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: Id1ab00613120775a74f87059f6f97a9a22f933b9
Reviewed-on: https://chromium-review.googlesource.com/1106860Reviewed-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@{#568718}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/9cccc5ce4fb9..2ac4352aea17


git log 9cccc5ce4fb9..2ac4352aea17 --date=short --no-merges --format='%ad %ae %s'
2018-06-19 chrome-bot@chromium.org Update config settings by config-updater.


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

The AutoRoll server is located here: https://chromite-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.


TBR=chrome-os-gardeners@chromium.org

Change-Id: I0be686bfae67b05024ac73b64e83b27707332e9b
Reviewed-on: https://chromium-review.googlesource.com/1106980Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#568717}

Allow BrowserCompositorMac to transition between different parent UI
layers, if needed.

Bug: 853302
Change-Id: I85596a1fe42c490d770f023c68d9a4093f050dcc
Reviewed-on: https://chromium-review.googlesource.com/1107047Reviewed-by: Robert Liao <robliao@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568716}

This CL renames an API setrContainerViewInternals to
setAccessDelegate and migrates to ViewEventSink that handles
view-related methods for content layer, in preparation of
deleting the class ContentViewCore.

Bug: 598880
Change-Id: I3023d0ac2959d88ad82cfe91a8c6cf2fc3955320
Reviewed-on: https://chromium-review.googlesource.com/1106649Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568715}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/4e454ce4..9edff1c2

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,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org

Change-Id: I0e42269e853a903edd722d7eb1f2af131a7bf45a
Reviewed-on: https://chromium-review.googlesource.com/1107256Reviewed-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@{#568714}

This is the correct constant that is expected by host devices.

Bug: 824568, 752273
Change-Id: I7f29159de6eb66f92f4534cd558fe82027175914
Reviewed-on: https://chromium-review.googlesource.com/1105621Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Ryan Hansberry <hansberry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568713}

cryptauth::SecureChannel requires that the client call the Initialize()
function before it starts connecting. I had forgotten to add this call
when I originally implemented BleConnectionManager.

Bug: 824568, 752273
Change-Id: I9464ee842382f53ed8cc253b5a4e93daf1af78d2
Reviewed-on: https://chromium-review.googlesource.com/1107297Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568712}

The basic settings page (via MainPageBehavior) searches its children
for settings-sections to hide when it expands a subpage. Because CL
https://chromium-review.googlesource.com/c/chromium/src/+/1105185
pushed the multidevice settings-section down the DOM tree, it is no
longer automatically hidden. To avoid dealing with the /deep/ selector
(see https://bugs.chromium.org/p/chromium/issues/detail?id=852098)
I just had the basic page take page expansion into account directly
when deciding whether to attach the
multidevice-settings-section-container.

Bug: 854400
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: I89e08e5af79163146737d7ae5a9637536cb032c2
Reviewed-on: https://chromium-review.googlesource.com/1107168
Commit-Queue: Jordy Greenblatt <jordynass@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568711}

https://skia.googlesource.com/skia.git/+log/846bb413e161..47c29fa64b3f


git log 846bb413e161..47c29fa64b3f --date=short --no-merges --format='%ad %ae %s'
2018-06-20 recipe-roller@chromium.org Roll recipe dependencies (trivial).
2018-06-19 angle-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/angle2 7df52383cfdf..4004ae0e033a (8 commits)


Created with:
  gclient setdep -r src/third_party/skia@47c29fa64b3f

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;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=kjlubick@chromium.org

Change-Id: I923f1d5ae0ab01a3ffd691e88d3d05ad33120d67
Reviewed-on: https://chromium-review.googlesource.com/1107179Reviewed-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@{#568710}

# This is an automated release commit.
# Do not revert without consulting chrome-pmo@google.com.
NOAUTOREVERT=true
TBR=mmoss@chromium.org

Change-Id: I36e2f8319ff878d53ede39aace6419eebdf4bd3a
Reviewed-on: https://chromium-review.googlesource.com/1107282Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568709}

Bug: 854081
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: Ib73d38ea25ca0ea70e3322b1e5066cd6a2b5ded9
Reviewed-on: https://chromium-review.googlesource.com/1106421Reviewed-by: calamity <calamity@chromium.org>
Commit-Queue: Esmael El-Moslimany <aee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568708}

Bug: 729800
Change-Id: I194f3f4b86794236cc90fbc8614b1da680c8aaa6
Reviewed-on: https://chromium-review.googlesource.com/1107315Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Commit-Queue: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568707}

This moves the responsibility of generating the CredentialMetadata
'secret' parameter (formely profile_id) into the
AuthenticatorRequestDelegate. CredentialMetadata uses the parameter to
derive the HMAC and AEAD keys for encrypting/encoding credential
metadata before storing it in the macOS keychain.

For Chrome, implement profile-specific secrets by storing the value in
the browser profile PrefService. This guarantees that credentials will
be logically separated by user profile.

Bug: 678128
Change-Id: I8c3d12c6db266105eeb63191e9d277d8cdb173ee
Reviewed-on: https://chromium-review.googlesource.com/1102179
Commit-Queue: Martin Kreichgauer <martinkr@google.com>
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Dominic Battré <battre@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568706}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/208cf41c691b..7c2b573628be


Created with:
  gclient setdep -r src-internal@7c2b573628be

The AutoRoll server is located here: https://src-internal-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.



BUG=chromium:835029
TBR=mmoss@chromium.org

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

When a Chromebook is flipped into tablet mode, scrolling
and gesture fling events should follow the same curve
used by android in order to have a smoother and more
fluid experience.

BUG=813911,822455

Change-Id: I39b42bdda08a3c20e1b7fab4d8f7e41c2a69b61a
Reviewed-on: https://chromium-review.googlesource.com/1087641Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Sahel Sharifymoghaddam <sahel@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568704}

crrev.com/c/1100535 landed a DCHECK that does not verify from ARC++,


[1814:1814:0619/160631.868318:FATAL:vaapi_picture_factory.cc(48)] Check failed: picture_buffer.texture_target() == GetGLTextureTarget() (0 vs. 36197)
#0 0x59c50521b4dc base::debug::StackTrace::StackTrace()
#1 0x59c50518f620 logging::LogMessage::~LogMessage()
#2 0x59c5026cc721 media::VaapiPictureFactory::Create()
#3 0x59c5026d2a94 media::VaapiVideoDecodeAccelerator::AssignPictureBuffers()
#4 0x59c506967623 arc::GpuArcVideoDecodeAccelerator::AssignPictureBuffers()
#5 0x59c50269c433 arc::mojom::VideoDecodeAcceleratorStubDispatch::Accept()
...

This CL corrects it.

Bug: 822346
Test: YT App playing back correctly with dcheck_always_on=true on nautilus.
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: Icff42847518df24dcc38998acdc2903e7928469f
Reviewed-on: https://chromium-review.googlesource.com/1106670Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568703}

See https://bugs.chromium.org/p/chromium/issues/detail?id=613096#c5 for
rationale

These two files:
third_party/closure_compiler/externs/accessibility_private.js
third_party/closure_compiler/externs/autofill_private.js
were updated in this commit, as an example of the change.

A follow-up commit will update other *_private.js files.

Bug: 613096
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: Ica4ab471956052b37c8bb6a9aabe4a7502408cfb
Reviewed-on: https://chromium-review.googlesource.com/1090425
Commit-Queue: Nigel Tao <nigeltao@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568702}

This should ensure the delete tasks get run.

Bug: 854032
Cq-Include-Trybots: luci.chromium.try:linux_mojo
Change-Id: I73304bee8ee59e3e30ecb060cd3288c2630c8191
Reviewed-on: https://chromium-review.googlesource.com/1106479Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568701}

Note that the only two production uses of this function are in
restoring this value either from (a) a session restored tab or
(b) a discarded tab. This formalizes the "set on creation"
nature of the property.

It also means that it is available immediately when a session
restored contents is added to a tab strip, rather than only
afterwards, which simplifies some tab manager code.

Change-Id: I2ee17ac809a5ad834e7207eee101f167512d9737
Reviewed-on: https://chromium-review.googlesource.com/1103317Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Sébastien Marchand <sebmarchand@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568700}

R=gayane

Change-Id: Ia43fcdad17628e63397ffa735da6d7439fd0baad
Reviewed-on: https://chromium-review.googlesource.com/1107133Reviewed-by: Gayane Petrosyan <gayane@chromium.org>
Commit-Queue: Varun Khaneja <vakh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568699}

It looks like every client of this code is passing in a delegate,
so we can simplify it a little by removing the if checks.

Change-Id: Ie32edc629117d9c204482d518f13c7beb5bf1cf7
Reviewed-on: https://chromium-review.googlesource.com/1106801Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: Peter Collingbourne <pcc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568698}

Adds expectations for Pixel 2 and Pixel 2 XL devices in
WebVrDeviceTest#testDeviceCapabilitiesMatchExpectations. Not a big deal
since we currently don't run automated tests on Pixel 2 devices, but
this should prevent local testing from having a few constantly failing
test cases.

TBR=bajones@chromium.org

Change-Id: I4cc1cfc0a8e74347274db4403e46b27bb0bf95d4
Reviewed-on: https://chromium-review.googlesource.com/1107271Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568697}

heap_page.h is used in 6,000+ compilation units, and this CL reduces its
estimated expanded size from 1.72MB to 1.40MB.

This CL relands https://chromium-review.googlesource.com/1104080 .
With the original code, GetRandomMagic() was folded into GetMagic(), and
GetMagic() was not folded into IsValid().
With https://chromium-review.googlesource.com/1104080,
ComputeRandomMagic() was not folded into GetMagic(), and GeMagic() and
IsValid() were folded into IsValid() callsites.  So the binary size
increased.
With this CL, GetMagic() isn't folded into IsValid() like the original
code. So this CL won't increase the binary size, and should not have
performance regression.

Bug: 242216
Change-Id: I7b6cf78a454abbbf3a3e41d821ac23e208b6dbdb
Reviewed-on: https://chromium-review.googlesource.com/1105208Reviewed-by: Keishi Hattori <keishi@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568696}

Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I5953a6d5c0256bcf37cc8038effb7f7ca65f2a55
Reviewed-on: https://chromium-review.googlesource.com/1107280Reviewed-by: Justin Cohen <justincohen@chromium.org>
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568695}

This fence is used to measure render time in VR Browsing mode. Replacing the
gpu_fence_ member after GVR Submit has a race condition - GVR internally
creates a fence when submitting and blocks the next Submit until the previous
submitted frame's fence is complete, but the separate render time fence was
created after submitting, so we may end up with a situation where this second
fence hasn't registered as complete yet.

Update the order to create the new fence first in a locally scoped variable
before GVR submit, then overwrite the previous fence only after GVR submit
completes.

BUG=854347

Change-Id: I8359f67859016039b2ddf5d54d5f391c5e212918
Reviewed-on: https://chromium-review.googlesource.com/1107013Reviewed-by: Bill Orr <billorr@chromium.org>
Commit-Queue: Klaus Weidner <klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568694}

Updates fonts, spaces, colors in omnibox-related code to match the new
specs.

Bug: 852787
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Ibe22b985011ce7ed3da9f83291f293e3942728c4
Reviewed-on: https://chromium-review.googlesource.com/1101026Reviewed-by: Justin Cohen <justincohen@chromium.org>
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568693}

A namespace could be purged between creation and being bound to, so
this removes purging of namespaces to prevent that.

When in the FETCHING_METADATA state, RunWhenConnected would run run
callbacks in an infinite loop. This removes that state.

R=mek@chromium.org

Bug: 854102, 848651, 854359
Change-Id: I0fe09caa251ed29bed279c66578cfbaec08da13d
Reviewed-on: https://chromium-review.googlesource.com/1106806
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568692}

- Make sure we're on the right thread
- Make sure SaveSubresourceFactories() is called only when non-null
  subresource factories is created (when NetworkService is enabled)

Bug: 849929
Change-Id: I53456bd67f10309940e89eab58c163173597611e
Reviewed-on: https://chromium-review.googlesource.com/1104083
Commit-Queue: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Jay Civelli <jcivelli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568691}

In preparing for http://crrev/c/1102157, make it easier for us to handle
the behavior change.

Bug: 847192
Change-Id: I0f67b894e38737339efa2aafe3093324876f5368
Reviewed-on: https://chromium-review.googlesource.com/1106598
Commit-Queue: Shimi Zhang <ctzsm@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568690}

Bug was introduced by https://chromium-review.googlesource.com/c/chromium/src/+/1083880

Bug: 854428
Change-Id: Id33c4c21595becfff4664b1bce24aa6e1eb81fa4
Reviewed-on: https://chromium-review.googlesource.com/1107266
Commit-Queue: Jared Saul <jsaul@google.com>
Commit-Queue: Mathieu Perreault <mathp@chromium.org>
Reviewed-by: Mathieu Perreault <mathp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568689}

Bug: 854124
Change-Id: I6ea086eff680f1085f1bbd3125bf994c3c7d3d96
Reviewed-on: https://chromium-review.googlesource.com/1106603Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Mathieu Perreault <mathp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568688}

https://chromium.googlesource.com/catapult.git/+log/f704817cbbab..f153b902bec3


git log f704817cbbab..f153b902bec3 --date=short --no-merges --format='%ad %ae %s'
2018-06-19 nednguyen@google.com Asserting that all story names are unique within a story set


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

The AutoRoll server is located here: https://catapult-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=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:849363
TBR=sullivan@chromium.org

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

The search and bookmark icons are the same as was already being used for
Touchable. The "page" icon is now a globe, which will be used for MD
Refresh (standard and touch) but not non-Refresh touch.

The colors will be updated in a future CL that addresses both icon color
and row highlight color.

Bug: 846407
Change-Id: Ieb9d020bfe27d6610694fd8c773ef1934e9d8c36
Reviewed-on: https://chromium-review.googlesource.com/1104874
Commit-Queue: Justin Donnelly <jdonnelly@chromium.org>
Reviewed-by: Dave Schuyler <dschuyler@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568686}

To make things easier AshWindowTreeHostPlatform also creates an
InputMethodMus. This way the right driver/registrar code is used.

BUG=837686
TEST=covered by tests

Change-Id: I82142be913f5a4a8ae1a368bea6b8579de8b251c
Reviewed-on: https://chromium-review.googlesource.com/1107007
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568685}

Bug: 853364
Change-Id: I319156aaae497b6900781ec20e212aa9c5ee2aa7
Reviewed-on: https://chromium-review.googlesource.com/1106601Reviewed-by: Marc-André Decoste <mad@chromium.org>
Commit-Queue: Owen Min <zmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568684}

This CL fixes some comment typos. Along the way, so other style changes
are made.

There are no logic changes in this CL.

Bug: None
Change-Id: Ib23f1e3964b45dddf81f0c14c1136f8a83c4c300
Reviewed-on: https://chromium-review.googlesource.com/1105480
Commit-Queue: Dave Schuyler <dschuyler@chromium.org>
Reviewed-by: Trent Apted <tapted@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568683}

the remoting client plugin.

WebRTC will use the metrics macros in
webrtc/system_wrappers/include/metrics.h to log all metrics that are
currently recorded by MetricsObserverInterface.

Bug: None
Change-Id: I3bdddbaf436c461a07bbd91ff763bb9351516253
Reviewed-on: https://chromium-review.googlesource.com/1107255Reviewed-by: Lambros Lambrou <lambroslambrou@chromium.org>
Commit-Queue: Qingsi Wang <qingsi@google.com>
Cr-Commit-Position: refs/heads/master@{#568682}