GitLab

Bug: 878178
Change-Id: I90a27bea589fafc048cb165ffb698c44cb7bb049
Reviewed-on: https://chromium-review.googlesource.com/1212762
Commit-Queue: Kevin Strohbehn <ginko@google.com>
Reviewed-by: Weidong Guo <weidongg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589672}

Create opaque SecurityOrigins for nonstandard schemes, unless
they are local. Allow creation of url::Origins for local,
nonstandard schemes.

The root problem here was inconsistency between url::Origin and
SecurityOrigin -- url::SchemeHostPort (and thus url::Origin)
rejects anything with a nonstandard protocol, but
SecurityOrigin::Create(KURL) would allow this creation to
proceed as a tuple origin ("protocol", "", 0).

The allowance of local+nonstandard schemes seems to be
necessary, at least temporarily, to avoid breaking the
Android-only "content:" scheme, and the ChromeOS-only
"externalfile:" scheme.

Other nonstandard schemes shouldn't generally commit, but this does
seem to be possible via LoadDataWithBaseUrl; for example in the test
"NavigationControllerBrowserTest.CrossDomainResourceRequestLoadDataWithBaseUrl"

BUG=862282

Change-Id: I351a067521cd846d2c77cca2498e58580613b4e2
Reviewed-on: https://chromium-review.googlesource.com/1208811
Commit-Queue: Nick Carter <nick@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589671}

Fixes a NOTREACHED crash on eng builds whenever you touch the screen.

Bug: internal b/112437110
Test: touch screen on eng build
Change-Id: Iab827b9943df6869a919443b43bfd2eba43da3fc
Reviewed-on: https://chromium-review.googlesource.com/1211707
Commit-Queue: Luke Halliwell <halliwell@chromium.org>
Reviewed-by: Sergey Volk <servolk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589670}

When resources for a screen density are missing in a WebAPK (e.g. the
WebAPK only contains an icon for xxxhdpi),
Resources#getDrawableForDensity() returns a scaled bitmap.

On Android versions up to Android M, Resources#getDrawableForDensity()
would sometimes return an incorrectly scaled cached bitmap instead of
rerequesting the resource and scaling it for the passed in density. See
the bug for more details.

This CL moves the icons to the mipmap-nodpi folder in order to disable
the automatic scaling when requesting a resource. The scaling now occurs
inside of ImageView. The move fixes the caching bug.

It also increases how often we use the webapp_splash_screen_no_icon.xml
layout on high density devices. In particular, if the WebAPK only has
a 144x144px sized icon on xxxhdpi devices:
Prior to this CL: We used webapp_splash_screen_small.xml and
                  upscaled the icon.
With this CL: We will use webapp_splash_screen_no_icon.xml

BUG=879194

Change-Id: I3c87898ca39cc7a47b614d4b219aee5f1e41ce74
Reviewed-on: https://chromium-review.googlesource.com/1199768Reviewed-by: Xi Han <hanxi@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589669}

CL was reverted here:
https://chromium-review.googlesource.com/c/chromium/src/+/1214105

The issue was another CL that renamed a function landed at the same
time.

It used to get the Primary Account's email but should get the active
account's one instead if in Butter state.

Bug: 881730
Change-Id: I9b5b489bc5237d044e7e36fde5eda7f7da7ada27
Reviewed-on: https://chromium-review.googlesource.com/1214063
Commit-Queue: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Reviewed-by: Mathieu Perreault <mathp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589668}

This change modifies the disk_cache API to support 64-bit cache sizes.
Individual entries are still limited to 32-bit sizes.  The blockfile
and memory backends will enforce a 32-bit cache size limit at runtime.
The simple backend is currently the only implementation that fully
supports 64-bit cache sizes.

R=jsbell@chromium.org, morlovich@chromium.org

Bug: 653630
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs;luci.chromium.try:linux_mojo
Change-Id: I9278b9e14e0a3253a66d20e57cf77026a462b4ac
Reviewed-on: https://chromium-review.googlesource.com/1194508
Commit-Queue: Ben Kelly <wanderview@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Reviewed-by: Maks Orlovich <morlovich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589667}

MDCAppBar will be deprecated soon, so eliminating any existing imports now will prevent errors later.

Bug: 874471
Change-Id: I67073fc90e935daee1c55d94db84eced20062999
Reviewed-on: https://chromium-review.googlesource.com/1213373Reviewed-by: Sergio Collazos <sczs@chromium.org>
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589666}

Google-internal design doc:
https://docs.google.com/document/d/1X6Xoz9hl3qoAj3EhAKcvZ6hWLVcY_QpQgmUexpgDHKA/edit?usp=sharing

Move prefs creation from AwBrowserContext in PreMainMessageLoopRun to
AwBrowserMainParts in PreCreateThreads. This way, variations can use the
same pref service as the rest of WebView, while still being initialized
as early as possible. (See BrowserMainLoop::CreateStartupTasks() for an
overview of the startup sequence.)

Before, AwBrowserContext created and owned PrefService and
BrowserPolicyConnector. Now, AwBrowserMainParts creates them in
PreCreateThreads, and owns them until PreMainMessageLoopRun, at which
point ownership is transferred to AwBrowserContext.

BUG=866722

Change-Id: Ie8eb6df60bd4a0f872d8c6401cc14ff0bca38368
Reviewed-on: https://chromium-review.googlesource.com/1212268Reviewed-by: Richard Coles <torne@chromium.org>
Commit-Queue: Paul Miller <paulmiller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589665}

Previously we assumed that Chrome would always start-up
on regular browsing mode (never in incognito). The linked
bugs prove that this is not true - sometimes the app starts
in incognito. This CL sets the incognito state on initialize
with native.

Bug: 881837, 880178
Change-Id: I67cf33b4be10997c5f62a85d893febde0c278b87
Reviewed-on: https://chromium-review.googlesource.com/1213313
Commit-Queue: Pedro Amaral <amaralp@chromium.org>
Reviewed-by: Pedro Amaral <amaralp@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589664}

Some failures are caused by changed but valid results instead of the bug.
Rebaseline so that we can track real flakiness.

TBR=yoichio@chromium.org

Bug: 774437
Change-Id: If7f5664902b67700bd18ab70a209cbc160e028d5
Reviewed-on: https://chromium-review.googlesource.com/1213269Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589663}

This makes us more consistent in how the ImmersiveFullscreenController
gets enabled. This patch also fixes the UMA for Chrome app windows.

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

https://chromium.googlesource.com/chromiumos/chromite.git/+log/990810e4ba69..6dd7eccb9a96


git log 990810e4ba69..6dd7eccb9a96 --date=short --no-merges --format='%ad %ae %s'
2018-09-07 bhthompson@google.com Add grunt-android-pi-pre-flight-branch builder for R70


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

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: Iff7f27d540739234f83832944ae556f2e12150d6
Reviewed-on: https://chromium-review.googlesource.com/1213943Reviewed-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@{#589661}

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


git log 515e7fe03790..1cefd62ebe68 --date=short --no-merges --format='%ad %ae %s'
2018-09-07 recipe-roller@chromium.org Roll recipe dependencies (trivial).


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

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.


TBR=agable@chromium.org

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

This fix would actually apply to desktop views if the test created
DesktopNativeWidgetAura there as well.

This also removes a CHECK in event_generator_test that was added here:
https://codereview.chromium.org/147203004/diff/140001/ui/aura/test/event_generator.cc
and makes EventGenerator reset current_target_ if the dispatcher is destroyed.
This assumes either the target is reset, or the generator destroyed.

BUG=594260
TEST=test only changes

Change-Id: I860f7e254a0d9a5826955011b74da8e25d50f042
Reviewed-on: https://chromium-review.googlesource.com/1213374Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589659}

This simplifies conditions around the code.

Bug: 561800
Change-Id: Iaa24aeb45df5465e88de8f48b504b98737557dbd
Reviewed-on: https://chromium-review.googlesource.com/1180635
Commit-Queue: Nicolas Zea <zea@chromium.org>
Reviewed-by: Nicolas Zea <zea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589658}

This also fixs a bug when using operator= with an event. Specifically we
were not correctly calling ReleaseCopiedNativeEvent() as well as
CopyNativeEvent(). I suspect not many places use operator=, so it wasn't
really an issue. I was tempted to make Event's operator= private, but KeyEvent
explicitly has operator=, which implies we need to support at Event as well.

BUG=881893
TEST=covered by tests

Change-Id: I16480937b04d881849ca7ac222f2df48d20e763d
Reviewed-on: https://chromium-review.googlesource.com/1213584Reviewed-by: Will Harris <wfh@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589657}

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.

If this CL sticks, then all tests related to this bug have been
re-enabled.

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

The tests have been running for a while now and look stable.  Move them over
to the main waterfall so they start being run by the CQ.

Bug: 874090
Bug: 847585
Change-Id: I8b013c568d0abbfb2697d5166dd6edda31bbbf88
Reviewed-on: https://chromium-review.googlesource.com/1212093
Commit-Queue: Ryan Cui <rcui@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589655}

- added images/ directory
- placing .svg images in images/
- moved default_N_percent directory to images/
- replaced the help_outline PNGs with SVG

Bug: 852872
Change-Id: I7c3083526a64304f461ed964b040767ba6d8afe4
Reviewed-on: https://chromium-review.googlesource.com/1210962Reviewed-by: Edward Jung <edwardjung@chromium.org>
Reviewed-by: Asanka Herath <asanka@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Dan H <harringtond@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589654}

Chrome extensions do not have direct access to a user's Chrome profile information, information such as saved passwords and autofill profiles.
However, the Action Recorder Extension may derive a user's saved passwords and autofill profile by observing the password fields, shipping info fields and payment fields that Chrome autofills.

To land this change, I also had to change how the extension detects the Chrome Autofill action. Prior to this change, the extension detects Chrome Autofill using a combination of keydown and onchange event listeners. This strategy can distinguish user typing actions from Chrome autofill actions, but this stategy does not distinguish Chrome autofill actions from Page JavaScript changing input values. In this change, I switched the extension to using the method outlined in https://medium.com/@brunn/detecting-autofilled-fields-in-javascript-aed598d25da7 to detect Chrome autofill.

Bug: 855284
Change-Id: I22283d5684237084ca2a8b95d9f4723be46b7746
Reviewed-on: https://chromium-review.googlesource.com/1208446
Commit-Queue: Yiming Zhou <uwyiming@google.com>
Reviewed-by: Jared Saul <jsaul@google.com>
Cr-Commit-Position: refs/heads/master@{#589653}

Per https://drafts.csswg.org/cssom/#serialize-a-string double quotes
should be used when serializing strings.

Bug: 873527
Change-Id: I3b7a3c6425c6a5d0d6f96399663f5ae8b3929a59
Reviewed-on: https://chromium-review.googlesource.com/1213171
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589652}

The patch to call Unalias caused a nullptr dereference, because of
another bug that previously only triggered a DCHECK. This patch ensures
to do a "safe unalias" where we first check for null.

This check can be reverted once the underlying issues that trigger the
DCHECK are fixed (see the two referenced bugs for the nullptr
dereference and for the DCHECK failure).

R=pdr@chromium.org, trchen@chromium.org

Bug: 881788, 853357
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I412d60581466a40e4543b0ce78b18fb1a739f02b
Reviewed-on: https://chromium-review.googlesource.com/1213869Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589651}

As per [1], CaptureRequest.get() may return nullptr. Crash reports show
that for some phone models some of these calls actually do. This leads
to nullptr exception when the return value is directly converted to a
primitive value.

This CL checks for null before assuming that the return value can be
converted to a primitive.

[1] https://developer.android.com/reference/android/hardware/camera2/CaptureRequest#get(android.hardware.camera2.CaptureRequest.Key%3CT%3E)

Bug: 880855
Change-Id: I4f83499f78208b97c181fa621a1ea621d5e08de1
Reviewed-on: https://chromium-review.googlesource.com/1214047Reviewed-by: Emircan Uysaler <emircan@chromium.org>
Commit-Queue: Christian Fremerey <chfremer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589650}

In preparation for enabling an ErrorProne check to ban them

Bug: 878853
Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester
Change-Id: I9cf9b07303fb3b00ce4d904f8fe56f47bb0b6268
Reviewed-on: https://chromium-review.googlesource.com/1213880Reviewed-by: Misha Efimov <mef@chromium.org>
Commit-Queue: Aiden Benner <abenner@google.com>
Cr-Commit-Position: refs/heads/master@{#589649}

If we haven't gone through prepaint since the LayoutObject was attached,
we will crash accessing the transform node.

Bug: 881921, 881735, 881643
Change-Id: I3c27c045a87319a3da2f1803707d42139d41cbfd
Reviewed-on: https://chromium-review.googlesource.com/1213805
Commit-Queue: Steve Kobes <skobes@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589648}

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

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: I4d48ac9270d7a9f897967fc13c58c335e0257206
Reviewed-on: https://chromium-review.googlesource.com/1213867Reviewed-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@{#589647}

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

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

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


CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia_arm64_cast_audio;luci.chromium.try:fuchsia_x64_cast_audio
TBR=cr-fuchsia+bot@chromium.org

Change-Id: I876ff2904f00f7030f771a13a10e9faff8bf1e6c
Reviewed-on: https://chromium-review.googlesource.com/1214088Reviewed-by: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#589646}

Bug: 876111
Change-Id: I8338c42e716142c4280336ea223205941002c6bf
Reviewed-on: https://chromium-review.googlesource.com/1185724Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589645}

We're consolidating roller accounts to ~1 per target repo.

Bug: skia:8291
Change-Id: I0e81d5062f30d051898d98a2008aa321c4a8f396
Reviewed-on: https://chromium-review.googlesource.com/1213934Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Eric Boren <borenet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589644}

Split out the logic that draws this highlight out of
CalculateIdealBounds which is becoming a bit long.

Bug: 880664
Change-Id: I3b36b93e2c6030b2e25552558d6a1321e647dda9
Reviewed-on: https://chromium-review.googlesource.com/1212082Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Manu Cornet <manucornet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589643}

https://webrtc.googlesource.com/src.git/+log/7cd2a9514837..d7027dc081cb


git log 7cd2a9514837..d7027dc081cb --date=short --no-merges --format='%ad %ae %s'
2018-09-07 mbonadei@webrtc.org Revert "Fix no_global_constructors in audio_processing/agc2/rnn_vad."
2018-09-07 jonasolsson@webrtc.org Reland "Consolidate loggability checks and replace streams."
2018-09-07 philipel@webrtc.org Reland "Remove RTPVideoHeader::vp8() accessors."
2018-09-07 philipel@webrtc.org Revert "Remove RTPVideoHeader::vp8() accessors."
2018-09-07 philipel@webrtc.org Renamed GetCodecHeader to GetRtpVideoHeader in RtpFrameObject.
2018-09-07 philipel@webrtc.org Remove RTPVideoHeader::vp8() accessors.
2018-09-07 nisse@webrtc.org Use function-local static variable for MessageQueueManager singleton.
2018-09-07 ilnik@webrtc.org Reenable simulcast video full stack test on MAC
2018-09-07 asapersson@webrtc.org Add option to only request a frame interval change via OnOutputFormatRequest.
2018-09-07 ssilkin@webrtc.org Handle empty GOF.
2018-09-07 buildbot@webrtc.org Roll chromium_revision d03e9be2..de648460 (589368:589477)
2018-09-07 nisse@webrtc.org Reland "Delete class EventTimerWrapper."
2018-09-07 philipel@webrtc.org Removed old and unused WebRTC-NewVideoJitterBuffer field trial from VideoReceiveStreamTest.
2018-09-07 danilchap@webrtc.org Use signed integers for limiting packet size in video packetizers
2018-09-07 mbonadei@webrtc.org Fix no_global_constructors in audio_processing/agc2/rnn_vad.


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

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:none,chromium:none,chromium:none,chromium:None,chromium:879584,chromium:None,chromium:none
TBR=webrtc-chromium-sheriffs-robots@google.com

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

https://chromium.googlesource.com/catapult.git/+log/32654a45d3da..febcf8764dc1


git log 32654a45d3da..febcf8764dc1 --date=short --no-merges --format='%ad %ae %s'
2018-09-07 nednguyen@google.com Ignore files/directory that are not tracked by git when generating BUILD.gn for Telemetry
2018-09-07 jbudorick@chromium.org devil: move gn files over from chromium.
2018-09-07 nastasoiuf@google.com Additional features for stacked plot
2018-09-07 simonhatch@chromium.org Dashboard - Remove TestMetadata._pre_put_hook
2018-09-07 simonhatch@chromium.org Dashboard - Remove stray print
2018-09-07 simonhatch@chromium.org Dashboard - Refactor find_anomalies to support stats later


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

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

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

Some omnibox janks are related to singleton not yet initialized.

We believe there can be lot of code running under the hood on the first
key stroke. We observed font cache initialisation, localisation loading, etc...

The intend of this metrics is to be able to compare popupation for the
first key stroke and for the normal use of omnibox.

R=mpearson@chromium.org

Bug: 868419
Change-Id: I191fd6ee564aa584b633b66a2f90fc7752b64633
Reviewed-on: https://chromium-review.googlesource.com/1210167Reviewed-by: Mark Pearson <mpearson@chromium.org>
Commit-Queue: Etienne Bergeron <etienneb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589640}

This adds a mechanism to report statistically-interesting
events to Chrome OS listeners.  A Chrome OS daemon (such
as the memory daemon "memd") can register as a client
of the Metrics Event Service, and receive signals on the
occurrence of related events (for instance, a tab discard).

This CL adds the supporting machinery and its first use,
signaling of a tab discard.

CQ-DEPEND=CL:1199965
BUG=chromium:729335
TEST=ran on DUT, verified that D-Bus signal is sent as expected

Change-Id: I6eddf4b0d18aa4c8a3fd4aab7f0770d87ddc7aeb
Reviewed-on: https://chromium-review.googlesource.com/1062078
Commit-Queue: Luigi Semenzato <semenzato@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Dan Erat <derat@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589639}

The code that adds padding to too small icons was breaking the larger
ones by cutting the minimal size (22x22px) out of their center.

Bug: 799427
Change-Id: I7a87d0229e063420a4814256528fbd070c62e503
Reviewed-on: https://chromium-review.googlesource.com/1173235
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589638}

This change moves most availability annotations to the class/ivar level so that
Touch Bar-specific classes can use Touch Bar APIs without internal availability
checks.

Change-Id: I63a73683456685057909d3414f5b6cd8293d9a41
Reviewed-on: https://chromium-review.googlesource.com/1211545Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Sarah Chan <spqchan@chromium.org>
Commit-Queue: Sidney San Martín <sdy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589637}

- Move ws::GpuInterfaceProvider into ws/public/cpp
- Move ash::ContentGpuInterfaceProvider into content as
  content::GpuInterfaceProvider;

This allows content_browsertests to use ContentGpuInterfaceProvider
for test_ws in single process mash.

Bug: 874089
Change-Id: Ia52f96c436c7d7cc2c034eaac8b20c5562a57f24
Reviewed-on: https://chromium-review.googlesource.com/1211973Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589636}

Based on skobes@ comments crbug.com/515257#c26, we decided not to
support "Prevent browser restoration if js scroll called before
browser restoration happens".

Layout.ScrollRestoration.PrecededByJsScroll is no longer needed.

This CL reverts crrev.com/c/889184.

Bug: 515257
Change-Id: I66f476c57bf59083a75a6b987d365515f1f3895e
Reviewed-on: https://chromium-review.googlesource.com/1213547Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Jianpeng Chao <chaopeng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589635}

A test for this new behavior is included as
external/wpt/xhr/abort-after-stop.htm.

This also means that XHR abort and readystatechange events from
navigation is no longer fired. Because of that,
external/wpt/xhr/open-url-multi-window-4.htm now times out rather than
fails on an assertion, aligning with Firefox. A TestExpectations entry
has been added with a bug that tracks fixing this test in spec or
upstream in WPT. A few other test expectations were updated as well to
account for this.

http/tests/navigation/reentrant-xhr-onabort-crash-during-commit.html no
longer works as intended, as abort event is no longer fired
synchronously (and thus does not expose the same crash surface). It is
replaced with an EventSource-based test that functions the same way as
XHR before this CL. Note, currently EventSource's error event suffers
from the same problem as XHR's abort event, and the class might undergo
the same change as this in the future. We will look into an alternative
for this test when that change is done.

Bug: 879620, 881180
Change-Id: I5a91047086d06347794656f92511a53c22401b5e
Reviewed-on: https://chromium-review.googlesource.com/1208672Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Timothy Gu <timothygu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589634}

Rename CompositorDelegate to GraphicsDelegate and VrShellGl to
GvrGraphicsDelegate.

Bug: 875291
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:linux_vr;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: Iecb896daaa47fc3681ca642e4dac4a654536d1c5
Reviewed-on: https://chromium-review.googlesource.com/1208675
Commit-Queue: Aldo Culquicondor <acondor@chromium.org>
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589633}