GitLab

https://chromium.googlesource.com/catapult.git/+log/86b118ed994e..f056cc5a549e


git log 86b118ed994e..f056cc5a549e --date=short --no-merges --format='%ad %ae %s'
2018-09-05 anthonyalridge@google.com Implements error bars for bar plotter.


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

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:866423
TBR=sullivan@chromium.org

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

self.browserState was nil at the point of initialization.

Bug: 845472
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: Id3fb457b493cecc1686144160a486fb6446fdea2
Reviewed-on: https://chromium-review.googlesource.com/1186334
Commit-Queue: Javier Ernesto Flores Robles <javierrobles@chromium.org>
Reviewed-by: Mark Cogan <marq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588884}

Change-Id: Ib619f3bdc7f3c6e6da3a0f16b2b3feddf9592478
Reviewed-on: https://chromium-review.googlesource.com/1207010Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: Jonathon Kereliuk <kereliuk@google.com>
Cr-Commit-Position: refs/heads/master@{#588883}

https://android.googlesource.com/platform/external/perfetto.git/+log/a8d99e51faf0..1d289218f53f


git log a8d99e51faf0..1d289218f53f --date=short --no-merges --format='%ad %ae %s'
2018-09-05 hjd@google.com perfetto-ui: Plumb notifyEof from UI to WASM


Created with:
  gclient setdep -r src/third_party/perfetto@1d289218f53f

The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-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=perfetto-bugs@google.com

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

Bug: 880608
Cq-Include-Trybots: luci.chromium.try:linux_mojo
Change-Id: I065803782935f7e69310a791ecb3053d573fcc61
Reviewed-on: https://chromium-review.googlesource.com/1205534Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Eric Roman <eroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588881}

We would like to verify Skia DDL correctness for rastering work. So a
new flag --enable-oop-rasterization-ddl is added. With this flag, the
raster decoder will record raster work into a DDL first, and then play it
back into a SkSurface. Right now, recording and playing back are on the
GPU main thread. In future, the recording could be moved to raster worker
threads.

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: Iba462c6a2376b9ab6fc663c97b913e568a5a8bce
Reviewed-on: https://chromium-review.googlesource.com/1169150Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588880}

https://webrtc.googlesource.com/src.git/+log/b29409064e87..e10f3b7403d0


git log b29409064e87..e10f3b7403d0 --date=short --no-merges --format='%ad %ae %s'
2018-09-05 yinwa@webrtc.org Reland "Remove steveanton from api/ watchlist"
2018-09-05 sakal@webrtc.org Update Android to use limited range YCbCr.
2018-09-05 ssilkin@webrtc.org Test setting of spatial index.
2018-09-05 danilchap@webrtc.org Replace WeakPtr with CancelablePeriodicTask in RtcpTransceiverImpl
2018-09-05 henrika@webrtc.org Relands Adds WebRTC.Audio.Record/PlayoutSampleRateOffsetInPercent UMA stats to native WebRTC


Created with:
  gclient setdep -r src/third_party/webrtc@e10f3b7403d0

The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-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:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng

BUG=chromium:None,chromium:b/113648245
TBR=webrtc-chromium-sheriffs-robots@google.com

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

Some of these files were including SkColorSpaceXform.h
where they really just wanted SkColorSpace.h.

One file was including SkColorSpaceXformCanvas.h but
not using it, and relying on a transitive include for
SkColorSpaceXform.h from another header that wasn't
using it at all.

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: I62774b88da06b98899aa9ed52633aa4acbb0073f
Reviewed-on: https://chromium-review.googlesource.com/1203912Reviewed-by: Florin Malita <fmalita@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588878}

This CL moves features::kVaapiJpegImageDecodeAcceleration so that it can
be accessed easily by GpuServiceImpl. GpuServiceImpl will use it to
decide whether it should instantiate an implementation of the image
decode acceleration mojo interface when requested by a renderer.

Bug: 868400
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: I93aa630792adae723236c8403ff807a31469ea8c
Reviewed-on: https://chromium-review.googlesource.com/1203430Reviewed-by: Camille Lamy <clamy@chromium.org>
Reviewed-by: Miguel Casas <mcasas@chromium.org>
Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
Commit-Queue: Andres Calderon Jaramillo <andrescj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588877}

Can repro the failure via:
  cd out/Debug
  rm gen/arsc/apks/MonochromePublicTestAr.ap_
  rm lib.java/third_party/android_system_sdk/android_system.jar
  ninja gen/arsc/apks/MonochromePublicTestAr.ap_

Change-Id: I6885219d272510ec024263a3567fb27acf68050f
Reviewed-on: https://chromium-review.googlesource.com/1205500Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org>
Commit-Queue: agrieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588876}

[ios] Subclass MDCAppBarViewController to prevent it from dismissing on Accessibility Z-gesture in Settings

This is already managed well by SettingsNavigationController.

Video: https://drive.google.com/open?id=1P3kKX_m8_xnaS2lF58BKvaRL5tTbsuyw


Bug: 877162, 874471
Change-Id: Ieb95fe427cece1d1fdb8f223bb16c0f0bbf05ce3
Reviewed-on: https://chromium-review.googlesource.com/1197411
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588875}

Split the condition on viewport-enabled between the gpu-raster decision
and the setting-up-the-viewport state. Expand the comment about the
gpu-raster decision. Remove an if condition for a possible null pointer
that was already dereferenced above.

R=bokan@chromium.org

Change-Id: I93110b078cc372fde1b1e490101d879a392acdd1
Reviewed-on: https://chromium-review.googlesource.com/1205310Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588874}

R=enne@chromium.org

Bug: 854256
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ieeae7911be96a95f961062262d24a454ec10da26
Reviewed-on: https://chromium-review.googlesource.com/1204925Reviewed-by: enne <enne@chromium.org>
Commit-Queue: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588873}

This patch adds ActivityTabProvider to ChromeActivity. This class
provides an easy mechanism for classes that care about the tab
that is currently in the foreground (i.e. not in the tab
switcher/toolbar swipe/animation layout).

The observer provides either the activity's tab or null depending
on the state of the browser. The null event can be ignored depending
on the listener.

The ActivityTabObserver interface only has a single method:
onActivityTabChanged(Tab t)

When an observer is attached to the provider, onActivityTabChanged is
called on only that observer with the current tab (giving it access
without requiring a handle to a larger object).

Bug: 871279
Change-Id: Ice961224c6690dc79c38f5d6cb255fed4730c8ce
Reviewed-on: https://chromium-review.googlesource.com/1165489
Commit-Queue: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588872}

Bug: 760811
Change-Id: If4f19ebfeb32cfdfca8aa94eac26c9c7afbf44fa
Reviewed-on: https://chromium-review.googlesource.com/1204591
Commit-Queue: Evan Stade <estade@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588871}

https://skia.googlesource.com/skia.git/+log/d0f0cb8ffc5e..74b1c01cdd1d


git log d0f0cb8ffc5e..74b1c01cdd1d --date=short --no-merges --format='%ad %ae %s'
2018-09-05 egdaniel@google.com Fix freeing of vulkan feature structs is test context.


Created with:
  gclient setdep -r src/third_party/skia@74b1c01cdd1d

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

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

RegKeyPath in pup.mojom has the only registry handle passed from the
chrome_cleaner target process to the broker process. This handle is always a
root key (eg. HKCU or HKLM) so it can be represented directly using the
PredefinedHandle enum. This simplifies the serialization slightly and is a
first step to switching to a move-only interface for registry handles.

Also update copyright headers and an obsolete comment on the EngineCommands
interface.

R=wfh

Bug: 830892
Change-Id: I687773b545d199b765345b2a7dd8e310b7609265
Reviewed-on: https://chromium-review.googlesource.com/1197223Reviewed-by: Will Harris <wfh@chromium.org>
Commit-Queue: Joe Mason <joenotcharles@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588869}

If a tab dragging is ended by a second finger tap down, PerformDeferredAttach()
might be called to merge the dragged tab into an overview window under the
current event position. The event position is calculated based on the current
attached tabstrip if it's a touch down event, thus we need to make sure the
current attached tabstrip is not nullptr when GetCursorScreenPoint() is called.

Bug: 877698
Change-Id: Ic2dcf9f2d4e79c00f3fd7ff0b724a8a45ba64781
Reviewed-on: https://chromium-review.googlesource.com/1200526Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Xiaoqian Dai <xdai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588868}

Element::setAttribute() modified to accept generic TrustedType
(StringOrTrustedHTMLOrTrustedScriptOrTrustedScriptURLOrTrustedURL)
(the name will be changed later).
This is the implementation used for setting attributes explicitly.

Added virtual GetCheckedAttributesNames() method, overriden in
HTMLXXXElement files, to return list of names of attributes that
need to have values checked against Trusted Types.

Added new implementations of Element::setAttribute(),
one per each Trusted Type, to be used internally
in HTMLElement functions.

Corrected existing TrustedXXX::GetString() implementations
to be concise.
Added TrustedScriptURL::GetString().

Bug: 739170
Change-Id: I3a9f51cbed5d75f8059141738b419cc66e529006
Reviewed-on: https://chromium-review.googlesource.com/1146563
Commit-Queue: Maja Kabus <kabusm@google.com>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588867}

Managed icon on the setting is read out as
"This setting is managed".

Bug: 878607
Change-Id: I8dcff087f8280fb1c9fdabdb17946c2917f94461
Reviewed-on: https://chromium-review.googlesource.com/1203375Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Commit-Queue: Vladislav Kuzkokov <vkuzkokov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588866}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/f20223d3..a330ed95

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: Ie83c1e9caf9294db2ecbc546ffa7e182e1041637
Reviewed-on: https://chromium-review.googlesource.com/1205608Reviewed-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@{#588865}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/d15b2011d9c0..bf7940726346


git log d15b2011d9c0..bf7940726346 --date=short --no-merges --format='%ad %ae %s'
2018-09-05 shapiroc@chromium.org Switch scarlet back to non-experimental
2018-09-05 vapier@chromium.org cros_portage_upgrade: drop x86 from required list
2018-09-05 vapier@chromium.org cros_mark_chrome_as_stable: stop passing CROS_SVN_COMMIT through


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

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: I7af1dceaad7a3f56a37663d4643efab87ffb8227
Reviewed-on: https://chromium-review.googlesource.com/1206774Reviewed-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@{#588864}

In https://chromium-review.googlesource.com/c/chromium/src/+/1205917:
"Set longer timeout to all tests in wpt/editing/run/", the test
external/wpt/editing/run/removeformat.html 's Timeout expectation was
removed (along with reference to crbug.com/813098). Likely as a result,
WebKit Linux Trusty Leak is flaking in webkit_layout_test for
removeformat.html. This CL undos the particular change to remove noise.

TBR=tkent@chromium.org,yoichio@chormium.org

Bug: 813098
Change-Id: I632084ec48cd8e3fb670a8d20c1210440b13fdc7
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/1207011Reviewed-by: Samuel Huang <huangs@chromium.org>
Commit-Queue: Samuel Huang <huangs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588863}

https://chromium.googlesource.com/catapult.git/+log/390e80705d70..86b118ed994e


git log 390e80705d70..86b118ed994e --date=short --no-merges --format='%ad %ae %s'
2018-09-05 chiniforooshan@chromium.org Telemetry: first_gesture_scroll_update_latency


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

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:760553
TBR=sullivan@chromium.org

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

Change-Id: Id4153b6fdd76aff58f682c92e5e67614cf30bfa4
Reviewed-on: https://chromium-review.googlesource.com/1205609Reviewed-by: agrieve <agrieve@chromium.org>
Commit-Queue: Ben Mason <benmason@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588861}

Removed TrustedHTML::escape(), TrustedHTML::unsafelyCreate(),
TrustedScriptURL::unsafelyCreate(), TrustedURL::create(),
TrustedURL::unsafelyCreate().

Current version of Trusted Types API is based on policies and no longer
uses the functions mentioned above.

Bug: 739170
Change-Id: I2bfc430bab3fa9a68ab9f3a0e5d76070841cec51
Reviewed-on: https://chromium-review.googlesource.com/1206474
Commit-Queue: Maja Kabus <kabusm@google.com>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588860}

We add one metric enum to represent each window shown/acceptance and one enum to denote the migration triggering source.

We record the histogram of each window shown/acceptance for each kind of the triggering source, which means for each entry point, we create a separate sub-histogram for the metric.

Bug: 852904
Change-Id: I2f1ac0561dcf44e81d8138b5250c68bf3b697be4
Reviewed-on: https://chromium-review.googlesource.com/1197326Reviewed-by: Jared Saul <jsaul@google.com>
Reviewed-by: Robert Kaplow (slow) <rkaplow@chromium.org>
Reviewed-by: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Commit-Queue: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588859}

I've run this test using the Linux Release (with dcheck) 1000 times locally,
and run 3 dry runs here.  I haven't been able to reproduce the flakiness
observed initially.  I'm unsure if there was an underlying issue that was fixed
or if I need to run on some additional architecture.  I plan to re-enable this
and monitor the run tracker so I have a better idea how to address the
flakiness if it still exists.

Bug: 874443
Change-Id: Ic3a839fd28a105b1b761ddffca5363803b357cc9
Reviewed-on: https://chromium-review.googlesource.com/1203933Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Commit-Queue: Eric Robinson <ericrobinson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588858}

https://skia.googlesource.com/skia.git/+log/9478f7a38e6c..d0f0cb8ffc5e


git log 9478f7a38e6c..d0f0cb8ffc5e --date=short --no-merges --format='%ad %ae %s'
2018-09-05 kjlubick@google.com Run lottie-web Gold collection at ToT


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

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

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

Before this CL  when dismissing the keyboard accessory, it might return
when new actions or tabs are added.

With this CL, dismissing the accessory means to only show it again when
it was explicitly requested (i.e. by the keyboard opening it).

Bug: 880188, 877008
Change-Id: I96187cbd29a1c98384b80b11a9ca40209aee4270
Reviewed-on: https://chromium-review.googlesource.com/1206473Reviewed-by: Ioana Pandele <ioanap@chromium.org>
Commit-Queue: Friedrich Horschig [CEST] <fhorschig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588856}

Make SearchByImage use ImageFetchTabHelper as "Copy Image" and "Save Image" do.

Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: I46251cec7c3a21fd0aea341a386a9f5766e9b52a
Reviewed-on: https://chromium-review.googlesource.com/1203712Reviewed-by: Mark Cogan <marq@chromium.org>
Commit-Queue: Yi Su <mrsuyi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588855}

Intent to Remove: https://groups.google.com/a/chromium.org/d/msg/blink-dev/35t5cJQ3J_Q/FH45dl0vAwAJ
PR against HTML: https://github.com/whatwg/html/pull/4001

Bug: 794548
Change-Id: I6a310aeeba12bc427062169c6397621725eb9bbd
Reviewed-on: https://chromium-review.googlesource.com/1206270
Commit-Queue: Mike West <mkwst@chromium.org>
Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588854}

The TabGridEmptyStateView is ignored in Voiceover, and changing the constraints
of the view can fix it. There is still a bug that happens when user open the
Voiceover in regular TabGrid for the first time, but that bugs exists before this
CL and will be fixed later.

Bug: 876873
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: Ifb07363b0e216bbb7b0ee4e3c05d7bfd59d4e415
Reviewed-on: https://chromium-review.googlesource.com/1202146Reviewed-by: Mark Cogan <marq@chromium.org>
Commit-Queue: Yi Su <mrsuyi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588853}

The initial lifecycle state is kStyleClean (in Document::Initialize). As
long as we are not scheduling layout tree updates, we will still be in
kStyleClean until we start scheduling updates. For the test in question
we are in a state where we have kStyleClean, but style isn't actually
clean because we haven't started scheduling updates. Make sure we are
actually updating style before checking and continuing testing.

Discovered this in the work with update roots where we were able to go
back to kVisualUpdatePending before the check.

Bug: 868810
Change-Id: Ie20d02b0e4be1d08914b056f4726627c40293414
Reviewed-on: https://chromium-review.googlesource.com/1206492Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588852}

Centers the dialog in the viewport rather than the ntp-contents div.

Before: https://screenshot.googleplex.com/kk5zQAxuCTr.png
After: https://screenshot.googleplex.com/NE4asURv2Dp.png

Bug: 880582
Change-Id: If5eac9aaf3bfd1d8e778aa684d6acffd874bab6d
Reviewed-on: https://chromium-review.googlesource.com/1205671
Commit-Queue: Mathieu Perreault <mathp@chromium.org>
Reviewed-by: Mathieu Perreault <mathp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588851}

Bug: 847528
Change-Id: Ie119a50be4dc4131954cac001a70821feb94018f
Reviewed-on: https://chromium-review.googlesource.com/1077147
Commit-Queue: Anna Malova <amalova@chromium.org>
Reviewed-by: Benoit L <lizeb@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Reviewed-by: Peter Conn <peconn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588850}

Bug: 878550
Change-Id: I2702b90cf5e59d211a93dfd18daa3d8977117005
Reviewed-on: https://chromium-review.googlesource.com/1193897
Commit-Queue: Vladislav Kuzkokov <vkuzkokov@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588849}

A number of changes have landed recently that may eliminate the
flakieness seen in this test. This CL re-enables the test, but feel
free to revert this if the flakes continue.

Bug: 833380
Change-Id: I013c87578e665cd91f111e2a1c6bb31a58cf6be1
Reviewed-on: https://chromium-review.googlesource.com/1205479Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Commit-Queue: James MacLean <wjmaclean@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588848}

Made the SetRemaining* ClearRemaining* instead since that was its only
use.

Discovered during the work with update roots.

Bug: 868810
Change-Id: Ia292127db574add6802ef09ee947b88725e7ee9e
Reviewed-on: https://chromium-review.googlesource.com/1206571Reviewed-by: Anders Ruud <andruud@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588847}

Several web-apps wish to use startEventLogging. Since all logs
are currently uploaded to Crash, we need a way to distinguish
which wep-app owns which log. We'll initially use an identifier,
incorporated into the filename.

Bug: 775415, 816510
Change-Id: I20cfda02bb679abe5ce1f816aa3f8239448f497d
Reviewed-on: https://chromium-review.googlesource.com/1201860Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Henrik Grunell <grunell@chromium.org>
Commit-Queue: Elad Alon <eladalon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#588846}