GitLab

TBR=phajdan.jr@chromium.org

Change-Id: I37975dc4f4db873685696955e7739305b2be8b7f
Reviewed-on: https://chromium-review.googlesource.com/579067
Commit-Queue: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488464}

The feature is described in https://github.com/WICG/device-memory
and the intent to ship is here:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/8qlTjzRY9Mc

Bug: chromium:710702,chromium:718622
Change-Id: If738affc6e171c60ad4b4540c2fec19959a1561a
Reviewed-on: https://chromium-review.googlesource.com/579795Reviewed-by: Shubhie Panicker <panicker@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Fadi Meawad <fmeawad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488463}

TBR=bmcquade

Change-Id: Id0933c23c20b818dc322ca7f487d1a242df61b4b
Reviewed-on: https://chromium-review.googlesource.com/530095
Commit-Queue: Steven Holte <holte@chromium.org>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488462}

RGB texture backed by native GMB cannot be bound to FBO on Intel, but BGR
texture backed by native GMB can be bound.

When GL_EXT_texture_format_BGRA8888 is supported, as-is chromium doesn't allow
BGRA and glTexStorage2D together, because the extensions doesn't define BGRA8
storage format.

Now native GBM needs BGR for WebGL hardware overlay, so this CL allows
both of them for WebGL context.

It's safe because WebGL API doesn't expose BGRA, and DrawingBuffer never use
glTexStorage2D(BGRA8).

BUG=746069
TEST=run WebGL Aquarium on eve
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I0e74f738beff16826dcc7af5684791712923851c
Reviewed-on: https://chromium-review.googlesource.com/576967
Commit-Queue: Dongseong Hwang <dongseong.hwang@intel.com>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Dongseong Hwang <dongseong.hwang@intel.com>
Cr-Commit-Position: refs/heads/master@{#488461}

It was landed almost a year ago, but was never used. If it turns out we
really do need it, can bring it back.

Bug: none
Change-Id: I8635219b8a3af3c46711ff7931403bf32854f351
Reviewed-on: https://chromium-review.googlesource.com/580387Reviewed-by: Miriam Gershenson <mgersh@chromium.org>
Commit-Queue: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488460}

This service is currently used only within the same process, and
potentially large amounts of data are transfered over its interfaces, so
this seems a prime candidate for lazy serialization, and should help
some with mojo localstorage performance.

Bug: 730475
Change-Id: Iff573b33f1bfda2193d6bfb5366b9d24f8190150
Reviewed-on: https://chromium-review.googlesource.com/580509Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488459}

This reverts commit 8a8b48bb.

Reason for revert: Speculative revert to fix broken WebUIWebViewBrowserTests, see http://crbug.com/747125

Original change's description:
> Enable field trial testing config for GuestViewCrossProcessFrames.
> 
> Bug: 655753
> Change-Id: I756aada2893846878657fe33b405bdb70b23df54
> Reviewed-on: https://chromium-review.googlesource.com/576207
> Commit-Queue: James MacLean <wjmaclean@chromium.org>
> Reviewed-by: Alexei Svitkine (slow) <asvitkine@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#487966}

TBR=asvitkine@chromium.org,lfg@chromium.org,wjmaclean@chromium.org

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

Bug: 655753, 747125
Change-Id: Id7486ff811442a5fd5e639deaef152e4382a70bc
Reviewed-on: https://chromium-review.googlesource.com/580547Reviewed-by: Scott Little <sclittle@chromium.org>
Commit-Queue: Scott Little <sclittle@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488458}

This CL is a refactor and has no intended behavior change.

By default, TestUkmRecorder no longer sets itself as the global UkmRecorder,
which doesn't work for browser tests. TestAutoSetUkmRecorder has the same
behavior as the previous TestUkmRecorder. All previous instances of
TestUkmRecorder were replaced by TestAutoSetUkmRecorder.

Bug: 
Change-Id: I10da73ff030c0d62cb7c9b1b9d6b4512572ad846
TBR: jam@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/580147
Commit-Queue: Erik Chen <erikchen@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488457}

Almost all callsites specify the |ok| argument. We should not use default
argument for rare cases.

Bug: 746157
Change-Id: I1cbc3491a510666a4269a6c993e0d811c29ecf5c
Reviewed-on: https://chromium-review.googlesource.com/579108Reviewed-by: Takayoshi Kochi <kochi@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488456}

The PDF plugin can receive a request to display a print preview with a 0
page count. It is a special meaning reserved for when the source of the
print preview is a PDF. In which case, just load the preview PDF in one
shot, instead of loading it incrementally.

BUG=746789

Change-Id: I3f9d99ebddffe9cedcc977dca03ccc2638f45011
Reviewed-on: https://chromium-review.googlesource.com/580495Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488455}

- This API can be used to exit VR when we encounter an unsupported
  feature.
- Make unhandled page info request use this API.

Change-Id: I974466cc40241f570aecb1ac08bb15b510bd57d2
Reviewed-on: https://chromium-review.googlesource.com/578209Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488454}

Previously, the importer would sometimes abandon a potential import
even when it passed CQ if there were any failing (flaky) jobs.

This CL should make it so that when deciding whether the CQ passed,
importer looks only at the latest builds for each builder.

Bug: 739119
Change-Id: I126e33191ddc24797501f97ff0834e3f9e45d4bc
Reviewed-on: https://chromium-review.googlesource.com/578141
Commit-Queue: Quinten Yearsley <qyearsley@chromium.org>
Reviewed-by: Jeff Carpenter <jeffcarp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488453}

SurfaceManager::RequestSurfaceResolution and
SurfaceDependencyTracker::RequestSurfaceResolution take in an unused
SurfaceDependencyDeadline parameter. This CL removes it.

Bug: none
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I914cd1f45423ef231f76a5b58a29a178a8bbb941
Reviewed-on: https://chromium-review.googlesource.com/580528Reviewed-by: John Bauman <jbauman@chromium.org>
Commit-Queue: Fady Samuel <fsamuel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488452}

Existing layout is bizarre. Margins for a child are calculated inside the
childs layout. This includes the auto margins calculation as far as we
can tell.

This just does the "simple" margin calculation (no auto etc) as auto margins
etc only occur within block layout, which we now control.

We may have to refine this to include more behaviour if we discover other
cases we don't cover.

Bug: 635619
Change-Id: I944ae3435074441f06e118c59f8d2ad317227b32
Reviewed-on: https://chromium-review.googlesource.com/580291
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488451}

https://pdfium.googlesource.com/pdfium.git/+log/77417ec9e131..3f753f20e9c5

$ git log 77417ec9e..3f753f20e --date=short --no-merges --format='%ad %ae %s'
2017-07-20 rharrison Change length calculation in CFX_StringCTemplate constructor
2017-07-20 art-snake Use enum for pdf object type
2017-07-20 npm Upgrade LibTIFF to 4.0.8

Created with:
  roll-dep src/third_party/pdfium


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

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls


TBR=dsinclair@chromium.org

Change-Id: Iedf571faf2d80398ea6a3fb126fc57d53d8d0446
Reviewed-on: https://chromium-review.googlesource.com/580352
Reviewed-by: <pdfium-deps-roller@chromium.org>
Commit-Queue: <pdfium-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488450}

This adds the chrome://safe-browsing/ WebUI page to WebView. This allows
WebView to hardcode URLs for testing Safe Browsing. This includes the
resources for the basic chrome://safe-browsing page.

As part of this, this adds WebUI to WebView for the first time.

This contains 2 changes to get things running for our tests:

 - Changes a DCHECK_EQ in content layer. This assumption doesn't
   hold for single process, so it crashes tests running in single
   process mode.
 - Adds more SandboxedProcessServices for the test shell. No change is
   needed for the actual WebView apk, because it already has more than
   enough SandboxedProcessServices (20).

The additional resources result in the following APK size increases for
the system_webview_google_apk target:

 - en-US.pak: 6896 -> 6947 (+51 bytes)
 - resources.pak: 434005 -> 436285 (+2280 bytes)

Bug: 709626
Test: run_webview_instrumentation_test_apk -f SafeBrowsingTest#testSafeBrowsingHardcodedUrls
Change-Id: Ie312521b323a5ba5ec37f8c44eaa1f0427587e34
Reviewed-on: https://chromium-review.googlesource.com/576404Reviewed-by: Nasko Oskov <nasko@chromium.org>
Reviewed-by: Bo Liu <boliu@chromium.org>
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488449}

Increasing timeout (https://codereview.chromium.org/2826253004)
lowered the failure rate. This indicates the tests are not inherently
flaky. They just run for longer.

Bug: 713172, 747073
Change-Id: I20a039776aa2aa9f70560e8d688f27ef34e6eb6a
Reviewed-on: https://chromium-review.googlesource.com/580256Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488448}

On other platforms we recored hardware timestamp to measure end-to-end
latency, however on Android the 'hardware timestamp' we got is actually
a resample (or latest) timestamp due to it's event batching mechanism.

This patch switched to use the oldest historical event time to match
other platforms and for better measuring of end-to-end performance.

Expecting to see regressions in UMA similar to
'Event.Latency.ScrollUpdate.Touch.TimeToScrollUpdateSwapBegin2',
e.g. Probably a 10ms ~ 20ms increase.

Note: This patch has no effect on telemetry tests.

Bug: 737379
Change-Id: I3bb4349ec1a47dc497817d70c2c5a64ed40f910a
Reviewed-on: https://chromium-review.googlesource.com/577962Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Alexandre Elias <aelias@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Chong Zhang <chongz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488447}

This reverts commit 17aced14.

Reason for revert: I only tested on iPhone 7, however, it seems that testNavigationByTappingReturn is broken on iPhone 5s. I'm going to investigate and then reland. Sorry for the inconvenience.

Original change's description:
> Make showcase home screen not translucent.
> 
> EarlGrey 1.10.1 has a bug that the scrollToTop action hangs
> indefinitely if the UITableView's navigation bar is translucent. Given
> that it makes no difference whether the view is translucent or not,
> this CL makes it not translucent to unblock rolling EarlGrey to 1.10.1.
> 
> Bug: 747116
> Change-Id: Idd48cf6f3f024c4b88bedcca412692598cd1a493
> Reviewed-on: https://chromium-review.googlesource.com/580357
> Reviewed-by: Ed Chin <edchin@chromium.org>
> Commit-Queue: Yuke Liao <liaoyuke@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#488417}

TBR=edchin@chromium.org,liaoyuke@chromium.org

Change-Id: I2669a23928d1f4ce230bb25bd852a6f441019f17
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 747116
Reviewed-on: https://chromium-review.googlesource.com/580194Reviewed-by: Yuke Liao <liaoyuke@chromium.org>
Commit-Queue: Yuke Liao <liaoyuke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488446}

This doesn't handle all the cases (e.g. plugins, downloads) but these don't work
yet with the network service. However it does fix 900 new wpt tests that 
started failing after r487304 since these generated *worker.html files weren't
being served with a mime type which was causing their load to fail.

BUG=746144,729849

Change-Id: I232c9af1dca32f1c641736c8ccd61978096559ef
Reviewed-on: https://chromium-review.googlesource.com/577507Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488445}

BUG=735285

Change-Id: I3982cc46b68fecf6b6f82193ad6739be265212e2
Reviewed-on: https://chromium-review.googlesource.com/578469
Commit-Queue: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488444}

Bug: 678800
Change-Id: If3bd8d215c2bf85e31472b73e4f6ffd7c13750cd

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

Change-Id: If3bd8d215c2bf85e31472b73e4f6ffd7c13750cd
Reviewed-on: https://chromium-review.googlesource.com/578382Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: John Bauman <jbauman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488443}

This CL disables certain items on the ToolsMenu based on the following 
criteria:
-No Tabs Opened. (Will disable Close All Tabs/Incognito Tabs)
-In New Tab Page. (Will disable Find in Page and Request Desktop/Mobile
sites).

In order to do this a new Bitmask is added to the ToolsMenuModel and it
is used by the ToolsMediator to check if the item should be enabled or
not.

Bug: 682880
Change-Id: I2318f7c3d6308317cb9c07e6b5a4692a4fdd9a5e
Reviewed-on: https://chromium-review.googlesource.com/571922Reviewed-by: Mark Cogan <marq@chromium.org>
Commit-Queue: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488442}

Previously, SecurityInfoForRequest updated cert_missing_subject_alt_name
only if a certificate was present. It should instead set the field to
false if a certificate is not present.

Bug: 733308
Change-Id: Ieff93a1b6c243d2019c23fb1484d727211eeab20
Reviewed-on: https://chromium-review.googlesource.com/576114Reviewed-by: Adrienne Porter Felt <felt@chromium.org>
Commit-Queue: Eric Lawrence <elawrence@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488441}

As part of Project Ribbon, separate the parsing logic for CSS
properties -webkit-perspective and perspective from
the parser into an API.

Bug: 668012
Signed-off-by: Rob Buis <rob.buis@samsung.com>
Change-Id: I504248e8561a9f97f741a5b5e3338b29d6caa395
Reviewed-on: https://chromium-review.googlesource.com/578213Reviewed-by: Bugs Nash <bugsnash@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488440}

This reverts commit 8a3c2e92.

Reason for revert: Causing compile issues.

Original change's description:
> Add test support for WebVR auto presentation
> 
> Adds test utility code that allows Chrome to think it's received an intent
> from a trusted app. This allows us to test Chrome's ability to auto present
> WebVR content when given a link from a trusted app (or test its rejection
> if the app is not trusted). Also adds one test using the new code.
> 
> Also contains a drive-by fix for flakiness in
> WebVrTransitionTest#testNfcFiresVrdisplayactivate caused by a race
> condition when adding the vrdisplayactivate listener.
> 
> Bug: 746086
> Change-Id: Ic6b55df18d915a4e36b36ca43bd11f4c773f6d33
> Reviewed-on: https://chromium-review.googlesource.com/578527
> Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
> Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
> Reviewed-by: Andrew Grieve <agrieve@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#488408}

TBR=mthiesse@chromium.org,agrieve@chromium.org,ymalik@chromium.org,bsheedy@chromium.org

Change-Id: I232fc7dd751f948caf5a20cd8de248560d87a529
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 746086
Reviewed-on: https://chromium-review.googlesource.com/580208Reviewed-by: Selim Gurun <sgurun@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488439}

The assertion on quic detail error code is flaky.
Sometimes we get QUIC_PACKET_READ_ERROR.
The test is meant to test that there is no crash.
The detail error information is not crucial. This test removes it.

Bug: 746575
Change-Id: I53800ee57aced2cd5aa22d67d39de022f47ac9ce
Reviewed-on: https://chromium-review.googlesource.com/580533Reviewed-by: Miriam Gershenson <mgersh@chromium.org>
Commit-Queue: Helen Li <xunjieli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488438}

Expand deqp/functional/gles3/shaderindexing/tmp.html Flaky to all Mac AMD

BUG=659871
TBR=kbr@chromium.org

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I8825bb13d51449137960331dbfc0fc66de945064
Reviewed-on: https://chromium-review.googlesource.com/580388
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488437}

BUG=485931,490423,397449

Change-Id: I169ae0cadb64a898364039948ad87447a6f8990b
Reviewed-on: https://chromium-review.googlesource.com/580130
Commit-Queue: Emil A Eklund <eae@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488436}

Bug: 
Change-Id: Id8c07997ba50f6d5592f54148f423cfeb920426f
Reviewed-on: https://chromium-review.googlesource.com/580071
Commit-Queue: Jared Saul <jsaul@google.com>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Mathieu Perreault <mathp@chromium.org>
Reviewed-by: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488435}

https://chromium.googlesource.com/angle/angle.git/+log/4cff8d6..0d2ecb4

BUG=2110,,chromium:740560

TEST=bots

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

Change-Id: Ifb40c58cbb5f6438e6518d1a639aa5fb0a84273f
Reviewed-on: https://chromium-review.googlesource.com/580399
Commit-Queue: Frank Henigman <fjhenigman@chromium.org>
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488434}

This CL is part of the Mojo Video Capture work.
Design doc for dev work [1].

Before this CL, the following situation could happen:
1. VideoCaptureManager calls ServiceVideoCaptureProvider::GetDeviceInfosAsync(
     callback).
2. ServiceVideoCaptureProvider makes a request to the service and waits for an
   answer
3. The service process crashes (or otherwise loses connection)
=> |callback| is never run

This CL also adds a test for the scenario described above and a fix in the
production code. The approach for the fix is to wrap the callback in a media::ScopedCallbackRunner to makes sure that  it always gets run. This change required moving some of the Callback types to OnceCallback, which is work we
want to do anyway.

Bug: 584797

[1] https://docs.google.com/a/chromium.org/document/d/1Qw7rw1AJy0QHXjha36jZNiEuxsxWslJ_X-zpOhijvI8/edit?usp=sharing

Change-Id: Id60b6ffd04de4f7118218099cc1ccd437744d5fb
Reviewed-on: https://chromium-review.googlesource.com/575786
Commit-Queue: Christian Fremerey <chfremer@chromium.org>
Reviewed-by: Taiju Tsuiki <tzik@chromium.org>
Reviewed-by: Emircan Uysaler <emircan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488433}

threaded-rendering@chromium.org doesn't exist. Change the name to valid
threaded-rendering-dev@.
As tdresser@ suggested, we should try to avoid including
public lists as owners. Updated the two entries created by me.

Bug: 
Change-Id: Idac0ea44dbdf4d30e4ff0199ada90d76e0559737
Reviewed-on: https://chromium-review.googlesource.com/579959Reviewed-by: Jesse Doherty <jwd@chromium.org>
Commit-Queue: Yi Gu <yigu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488432}

(remove SK_SUPPORT_LEGACY_TILED_BITMAPS)

Change-Id: Ic4552ede98e6690d3067695e01c90c81cb357cef
Reviewed-on: https://chromium-review.googlesource.com/545816
Commit-Queue: Florin Malita <fmalita@chromium.org>
Reviewed-by: Mike Klein <mtklein@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488431}

Bug: 
Change-Id: Iea73537e5b586307596579afe1eb1e5d5ea4de89
Reviewed-on: https://chromium-review.googlesource.com/579729
Commit-Queue: Tommi <tommi@chromium.org>
Reviewed-by: Emircan Uysaler <emircan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488430}

BUG=737067

Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I29bbaeec11a59d8b1e9cab9cf584b03442ec1086
Reviewed-on: https://chromium-review.googlesource.com/580392Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Commit-Queue: Toni Barzic <tbarzic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488429}

This URL was provided by the Help Content team. Note that it is not currently
active, but the site will be uploaded soon.

Bug: 672263
Change-Id: I702a36b79b1d667049daf8358431105ee8f9ce0f
Reviewed-on: https://chromium-review.googlesource.com/580350Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488428}

We suspect that library prefetching slows startup on low-end devices.
This CL adds an experiment to verify that hypothesis.

Bug: 735799
Change-Id: I5bc969e7d417f07520caef28fc4e0598e545d51b
Reviewed-on: https://chromium-review.googlesource.com/578711
Commit-Queue: Dmitry Skiba <dskiba@chromium.org>
Reviewed-by: Maria Khomenko <mariakhomenko@chromium.org>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Reviewed-by: Egor Pasko <pasko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488427}

From 16 min to 25

Seems to timeout occasionally:
https://build.chromium.org/p/chromium.linux/builders/Android%20Tests/builds/43919
https://build.chromium.org/p/chromium.linux/builders/Android%20Tests/builds/43911
https://build.chromium.org/p/chromium.linux/builders/Android%20Tests/builds/43907
https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/44123

R=jbudorick@chromium.org

Bug: 
Change-Id: I95f1c034c4c5154b44e4cec5df956456ad53eedc
Reviewed-on: https://chromium-review.googlesource.com/580248Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Benjamin Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488426}

This CL eliminates the redundant css rules for paper-button in favor of reusing the styling in the shared cr_elements location.

Bug: 740758
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Ieba6ab6bf03e2c063a52323ecacaafc5919e4dfa
Reviewed-on: https://chromium-review.googlesource.com/577027Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: Scott Chen <scottchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488425}