GitLab

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

Right now, we determine whether to store the record of a lazy listener
in the extension prefs based only on the type of context - if the
context registering the listener is a lazy context (like an event page),
then we store a lazy listener in extension prefs.

This is incorrect for webview events.  Webview events are exposed on a
<webview> DOM object, but are implemented behind-the-scenes as
extension events (including the listener bookkeeping). However, having a
lazy listener for a webview event doesn't make sense:
- the only time a listener would be considered lazy is when the listener
  was added in a lazy context
- a lazy listener will only be used to wake up an inactive context
- webview events are tied to a specific webview
Thus, a lazy listener would only be used for a webview which has since
been torn down.

With this in mind, we can avoid registering any lazy listeners for
webview-related events. Introduce the key supportsLazyListeners into the
JSON schema and add it for webview events. When this key is present,
events don't register lazy listeners.

Wire this up for both native and JS-based bindings, and add unit tests
for the bindings and an end-to-end test to ensure that webview event
listeners will never be registered as lazy listeners.

A followup will add logic to clean up current prefs to remove traces of
the listeners.

BUG=736381

Review-Url: https://codereview.chromium.org/2973903002
Cr-Commit-Position: refs/heads/master@{#487991}

Reland "Reland "Persist broken and recently-broken alt-svcs to prefs in HttpServerPropertiesManager""

This is a reland of 9c083706
Original change's description:
> Reland "Persist broken and recently-broken alt-svcs to prefs in HttpServerPropertiesManager"
> 
> This is a reland of a66ebc8a
> Original change's description:
> > Persist broken and recently-broken alt-svcs to prefs in HttpServerPropertiesManager
> > 
> > Modify TickClock dependency injection for BrokenAlternativeServices to use a setter instead of a constructor param.
> > Add TickClock dependency injection for HttpServerPropertiesImpl and HttpServerPropertiesManager for testing.
> > 
> > Add BrokenAlternativeService::Clear() and update HttpServerPropertiesImpl::Clear() to call that.
> > 
> > CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_chromium_ubsan_rel_ng
> > 
> > BUG=705029
> > 
> > Change-Id: Idb411192e47d275cde3362b479a6b9e9fa773a17
> > Reviewed-on: https://chromium-review.googlesource.com/562604
> > Reviewed-by: Zhongyi Shi <zhongyi@chromium.org>
> > Reviewed-by: Steven Holte <holte@chromium.org>
> > Commit-Queue: Yixin Wang <wangyix@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#486519}
> 
> Bug: 705029
> Change-Id: I14f36cc6014f001d9aefa4678a7bfa8f621b2834
> Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_ubsan_rel_ng
> Reviewed-on: https://chromium-review.googlesource.com/571044
> Reviewed-by: Zhongyi Shi <zhongyi@chromium.org>
> Reviewed-by: Steven Holte <holte@chromium.org>
> Commit-Queue: Yixin Wang <wangyix@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#487342}

Bug: 705029
Change-Id: Iefb798a8c4d54263e5e8f47bc5d1c63c04d72f77
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_ubsan_rel_ng
Reviewed-on: https://chromium-review.googlesource.com/576349Reviewed-by: Mark Pearson <mpearson@chromium.org>
Reviewed-by: Ryan Hamilton <rch@chromium.org>
Commit-Queue: Yixin Wang <wangyix@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487990}

For the first time, the flag expectations file now includes expectations for all
platforms the CQ runs layout tests on (Linux, Mac, Win).  This process was used:

1. Triggered CQ dry run with empty flag expectations file and RLS forced on in
   test runner (see patch set 1).

2. Saved {linux,mac,win}_chromium_rel_ng layout_test_results from new viewer in
   TestExpectations format, to local files named "Linux", "Mac", and "Win".

3. Ran this hacky Python script, piping stdout to the flag expectations file:
   https://pastebin.com/ikHTt5zf

Bug: 711468
Change-Id: Iebe35ae4a637aaaae85bc9adba1d278bde80d381
Reviewed-on: https://chromium-review.googlesource.com/576353
Commit-Queue: Steve Kobes <skobes@chromium.org>
Reviewed-by: Stefan Zager <szager@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487989}

https://swiftshader.googlesource.com/SwiftShader.git/+log/4d97f36..010a464

BUG=737384

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,linux_chromium_cfi_rel_ng;master.tryserver.chromium.android:android_optional_gpu_tests_rel

Change-Id: Ib297a22f55426153c816bf59fe6701a41ccef6a2
Reviewed-on: https://chromium-review.googlesource.com/578246Reviewed-by: Alexis Hétu <sugoi@chromium.org>
Commit-Queue: Nicolas Capens <nicolascapens@google.com>
Cr-Commit-Position: refs/heads/master@{#487988}

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

Revert of Add libc++ __tree to ubsan blacklist. (patchset #2 id:20001 of https://codereview.chromium.org/2109663003/ )

Reason for revert:
Issued fixed upstream

Original issue's description:
> Add libc++ __tree to ubsan blacklist.
>
> libc++ __tree is not ubsan clean. It floods compile and run steps
> with "runtime error: downcast" and "runtime error: upcast" errors,
> making ubsan much less usable.
> This is a KI with libc++: https://llvm.org/bugs/show_bug.cgi?id=19302
>
> Committed: https://crrev.com/e2abe2366d707ac6ad308e2643f41423971f81fc
> Cr-Commit-Position: refs/heads/master@{#402902}

TBR=dpranke@chromium.org,ochang@chromium.org,thakis@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.

Review-Url: https://codereview.chromium.org/2983093003
Cr-Commit-Position: refs/heads/master@{#487986}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/67c78739..b55b2e87

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;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

TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org

Change-Id: Ieb9dcea8393b4dc4c37c0f37722f8d8575567868
Reviewed-on: https://chromium-review.googlesource.com/577915Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487985}

BUG=703369

Review-Url: https://codereview.chromium.org/2981073002
Cr-Commit-Position: refs/heads/master@{#487984}

This reverts commit a207e0dd.

Reason for revert: Lint error in downstream code.

Original change's description:
> Android: Re-enable lint
> 
> Android lint has been failing due to API level mismatch between lint and
> platform-tools (26 vs 25). This is causing new lint errors to be
> introduced. Ignore the API mismatch for now and re-enable lint so it at
> least catches all other issues.
> 
> API warning will be re-enabled after platform-tools is rolled.
> 
> Bug: 739746,746409
> Change-Id: I339560498544462732300c5030381a0c67f25f1b
> Reviewed-on: https://chromium-review.googlesource.com/577593
> Reviewed-by: Andrew Grieve <agrieve@chromium.org>
> Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
> Commit-Queue: Peter Wen <wnwen@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#487918}

TBR=mthiesse@chromium.org,wnwen@chromium.org,agrieve@chromium.org

Change-Id: I4857cf1ba5f10b009155693a803df922036f1878
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 739746, 746409
Reviewed-on: https://chromium-review.googlesource.com/578059Reviewed-by: Tien-Ren Chen <trchen@chromium.org>
Commit-Queue: Tien-Ren Chen <trchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487983}

In preparation for https://skia-review.googlesource.com/c/24644/8

NOTRY=True

Bug: 746578
Change-Id: Ia5a59056598e6db62ca2417eaddc2a783d4625b4
Reviewed-on: https://chromium-review.googlesource.com/578487
Commit-Queue: Mike Reed <reed@chromium.org>
Reviewed-by: Florin Malita <fmalita@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487982}

Bug: 
Change-Id: I5f05a943778b6a56abf5535cd0d2b43389ef733f
Reviewed-on: https://chromium-review.googlesource.com/577723
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487981}

This is responsible for a major video playback regression on android
webview.

Revert "gpu: Allow empty sync tokens in mailboxes."

This reverts commit d698cc2f.

Revert "cc: Explicitly set sync tokens for mailbox resources."

This reverts commit 61b4a9e4.

TBR=piman,sandersd

Bug: 745941
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;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: I8609150bf4b2069010e2f7c8cb5fd6f75f95acf8
Reviewed-on: https://chromium-review.googlesource.com/577990
Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487980}

Move all chrome.send calls to the native layer
Rename native layer functions to match names of messages being sent.

Bug: 717296
Change-Id: Ie69391d107183c4fd0e97339d4014ea89f1181e3
Reviewed-on: https://chromium-review.googlesource.com/575374Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487979}

In change r484950 (https://codereview.chromium.org/2967193003),
AXNodeObject::ComputeAriaOwnsChildren was modified to handle both
ARIA attributes and AOM properties.

The change resulted in calling AxObjectCache().UpdateAriaOwns() with an
empty vector in a case where it wasn't called before, and when calling it
on an element with no Node (like on an anonymous block, for example),
that led to a crash. Fix that by only calling it when GetNode() is valid.

Bug: 740375
Change-Id: I058c9760e600e3e582778788a12950cbbeeb77a9
Reviewed-on: https://chromium-review.googlesource.com/574765Reviewed-by: Alice Boxhall <aboxhall@chromium.org>
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487978}

Bug: none
Change-Id: I38806a0f1bd878e9e7e51c7dc95b833488ac7754
Reviewed-on: https://chromium-review.googlesource.com/578310Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Commit-Queue: Will Chen <chenwilliam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487977}

BookmarksIOFunction used to retrieve default path in FILE
thread. Use a task with traits:
1. MayBlock: Since this requires IO
2. USER_VISIBLE: As this is part of importing/exporting bookmarks.
3. SKIP_ON_SHUTDOWN: There's no point to continue on or block shutdown
  because additional operations are required (e.g. showing a file
  select dialog) for this to complete.

Bug: 689520
Change-Id: Ibed8ea5213ca71f07a47cbb4e2c45cadeb9da429
Reviewed-on: https://chromium-review.googlesource.com/577112
Commit-Queue: Istiaque Ahmed <lazyboy@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487976}

Renamed TrayDetailsView::InfoLabel to TrayInfoLabel and moved it to its own file. It also now subclasses ActionableView instead of View, so it can be clickable. TrayInfoLabel::Delegate keeps track of whether or not the label is clickable, and handles clicks.

BUG=672263,735642

Review-Url: https://codereview.chromium.org/2957043002
Cr-Commit-Position: refs/heads/master@{#487975}

https://skia.googlesource.com/skia.git/+log/0c15ae82f0d5..edfe4a5ca018

$ git log 0c15ae82f..edfe4a5ca --date=short --no-merges --format='%ad %ae %s'
2017-07-19 borenet [infra] Add protoc asset
2017-07-19 ethannicholas run skslc output through clang-format
2017-07-19 bsalomon Remove GrLegacyMeshDrawOp and GrPipelineBuilder
2017-07-19 fmalita Revert "Use raster pipeline for repeat/mirror radial gradients"
2017-07-19 bsalomon Fix Google3 Roller?
2017-07-19 bsalomon Move GrTypesPriv.h to include/private
2017-07-19 fmalita Use raster pipeline for repeat/mirror radial gradients

Created with:
  roll-dep src/third_party/skia


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


CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_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;master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=caryclark@chromium.org

Change-Id: I2c56cc2aeb11acba1586fb643118f244c2a849b5
Reviewed-on: https://chromium-review.googlesource.com/578322Reviewed-by: Skia Deps Roller <skia-deps-roller@chromium.org>
Commit-Queue: Skia Deps Roller <skia-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487974}

Bug: 738540
Change-Id: If0782f8983263d500285de3c986de180c268f2b3
Reviewed-on: https://chromium-review.googlesource.com/575762Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Ryan Hansberry <hansberry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487973}

Bug:skia:6828
Change-Id: I8456ac491ce4f140349545ba086cc0a1ba0d1f4c

TBR=
removing unused param (null)

Change-Id: I8456ac491ce4f140349545ba086cc0a1ba0d1f4c
Reviewed-on: https://chromium-review.googlesource.com/577668
Commit-Queue: Mike Reed <reed@chromium.org>
Reviewed-by: Florin Malita <fmalita@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487972}

Changes:
1. Makes the launcher go back to PEEKING state when you click close
button in HALF mode.
2. Modifies the corresponding unit test.

BUG=745156
TEST=SearchBoxViewFullscreenTest.CloseButtonTest

Change-Id: I12b6743cdf49ddbac254004d053d60db2df602e5
Reviewed-on: https://chromium-review.googlesource.com/576115
Commit-Queue: Weidong Guo <weidongg@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487971}

The WebVR 1.1 spec was updated to clarify the behavior of getFrameData.
Now, GetFrameData should return false unless called within a
VRDisplay.requestAnimationFrame callback.

BUG=736023

Change-Id: I14d9442a016817a78232ed7b1e71956c8dac614a
Reviewed-on: https://chromium-review.googlesource.com/578188Reviewed-by: Brandon Jones <bajones@chromium.org>
Commit-Queue: Bill Orr <billorr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487970}

Revert "[Payment Request] Adds tests for accessibility on main pages of Paymnet Request - Second Relanding"

This reverts commit c7c107f1.

Reason for revert: payments_accessibility_egtest Tests are failing on various devices:
https://uberchromegw.corp.google.com/i/internal.bling.main/builders/ipad9-device-x64/builds/12117/steps/steps/logs/stdio

https://uberchromegw.corp.google.com/i/internal.bling.main/builders/ipad10-device-x64/builds/5818/steps/ios_chrome_ui_egtests%20%28iPad%20Air%20iOS%2010.0.1%29%20on%20iOS-10.0.1/logs/stdio

I tried to run the test locally and they are failing as well 

Original change's description:
> [Payment Request] Adds tests for accessibility on main pages of Paymnet Request - Second Relanding
> 
> 
> The previous reland of this CL did not include the command line arguments for one of the build bots.
> This reland adds the command line argument for that build bot.
> 
> TBR=lpromero@chromium.org,michaeldo@google.com
> 
> Change-Id: Ia20efa783eb763ae97f7e0df2f80e710823d7482
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 734571
> 
> Change-Id: If9fd7b6d2741178b307c3c51763cc89fdcb44073
> Reviewed-on: https://chromium-review.googlesource.com/574690
> Reviewed-by: Eugene But <eugenebut@chromium.org>
> Reviewed-by: mahmadi <mahmadi@chromium.org>
> Commit-Queue: Randall Raymond <rayraymond@google.com>
> Cr-Commit-Position: refs/heads/master@{#487861}

TBR=eugenebut@chromium.org,rayraymond@google.com,mahmadi@chromium.org

Change-Id: Icaea64b4801e9240c4daa25933c65149b3e051d9
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 734571
Reviewed-on: https://chromium-review.googlesource.com/578135Reviewed-by: Sergio Collazos <sczs@chromium.org>
Commit-Queue: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487969}

This CL enables GlobalResourceCoordinator (e.g. resource_coordinator
service, GRC) by default. Several projects depend on the GRC service.
Features using GRC should be guarded by their own feature flag and run
their own finch trials.

Several fixes needed to occur to make this happen:
- Remove buggy GRC process CPU profiling infrastructure. An updated
  version will be added in:
   https://chromium-review.googlesource.com/c/565906/
- Improve MockRenderProcessHost to allow GetProcessResourceCoordinator
  to be called with connections to the test ServiceManager
- ResourceCoordinatorWebContentsObserver::IsEnabled checks to make sure
  ServiceManagerConnection is available to connect to.
- Disable FrameResourceCoordinator because WebFrameClient subclasses 
  do not implement GetInterfaceProvider and crash when being called.

This CL has been extended and migrated from CodeReview:
https://codereview.chromium.org/2958133003
which was originally being landed on behalf of zhenw@:
https://codereview.chromium.org/2943563002

R=oysteine@chromium.org, zhenw@chromium.org,lpy@chromium.org,rockot@chromium.org,nasko@chromium.org
BUG=691886

patch from issue 2958133003 at patchset 710001 (http://crrev.com/2958133003#ps710001)

Change-Id: Ie6b61e93666ba9e753a218a79e2cff64646e7644
Reviewed-on: https://chromium-review.googlesource.com/572429
Commit-Queue: Matthew Halpern <matthalp@google.com>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Reviewed-by: Zhen Wang <zhenw@chromium.org>
Reviewed-by: Oystein Eftevaag <oysteine@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487968}

When disconnecting the main HttpURLConnection, close the OutputStream if
it has not yet been closed (e.g. when enterUploadErrorState() is called).

BUG=745870

Change-Id: I16930d0b3dd17d8d17c36e90cd5c1fe8d6f86964
Reviewed-on: https://chromium-review.googlesource.com/575275
Commit-Queue: Miriam Gershenson <mgersh@chromium.org>
Reviewed-by: Miriam Gershenson <mgersh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487967}

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}

There is an option to configure the maximum size of the NetLog. The
default is 100MiB.

This is a re-land of https://chromium-review.googlesource.com/c/571514/

Bug: 679030
Change-Id: I79eb7e6012deb0979b94a1c0f487068e7800105b
Reviewed-on: https://chromium-review.googlesource.com/578048
Commit-Queue: Eric Roman <eroman@chromium.org>
Reviewed-by: Helen Li <xunjieli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487965}

This CL fixes an issue where the controller converts the required task
start time to seconds which causes the OS to sometimes schedule the task
a fraction of second before the entry is expired. In that case the file
monitor won't remove the file as the entry is still not expired. Also
once the cleanup is done, we should check if we have more COMPLETE
entries for which we have to schedule cleanup.

Bug: 
Change-Id: Id2f1a6a236dfd3a60f460d463419974d79e73d38
Reviewed-on: https://chromium-review.googlesource.com/576890
Commit-Queue: Shakti Sahu <shaktisahu@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487964}

This seems to fix the black flashing that was happening with the
extension popup UI. WS_EX_COMPOSITED was originally hiding this issue in
most cases (except possibly http://crbug.com/586454 ), possibly because
it didn't allow GDI painting outside of WM_PAINT (like is happening here).

Bug: 739724
Change-Id: I897deedb3bf7f2c2ff799cb24a98e0f94f835ea9
Reviewed-on: https://chromium-review.googlesource.com/564147Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Ananta Iyengar <ananta@chromium.org>
Commit-Queue: John Bauman <jbauman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487963}

Bug: 
Change-Id: I398b76a5424d3a4fb66ec78a58855a87cf914ba7
Reviewed-on: https://chromium-review.googlesource.com/575269Reviewed-by: David Benjamin <davidben@chromium.org>
Commit-Queue: Steven Valdez <svaldez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487962}

Bug: 90277
Change-Id: If7168191fc8c80acc45831731f016494ba4352ba
Reviewed-on: https://chromium-review.googlesource.com/576767Reviewed-by: David Benjamin <davidben@chromium.org>
Commit-Queue: Matt Mueller <mattm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487961}

Skia Blur image filter has a new mode to clamp pixels outside image to
image edge. This can resolve the bleeding black issue at the bounds of
texture.

BUG=622128
TEST=manual tested with lock screen and new app launcher.

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Id13383910327882d61bd908bff51d2c3fdc36bb9
Reviewed-on: https://chromium-review.googlesource.com/559935
Commit-Queue: Tao Wu <wutao@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Reviewed-by: Stephen White <senorblanco@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Vladimir Levin <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487960}

So we don't lose data in the debugging visualization in
DebugRectHistory::SaveTouchEventHandlerRectsCallback, we now
iterate through the rects independently from each touch action 
as opposed to using the union of these values. DebugRect
stores a TouchAction bit that is populated within
SaveTouchEventHandlerRectsCallback.

In HeadsUpDisplayLayerImpl::DrawDebugRects, the
|debug_rects|'s touch action is added to the
HeadsUpDisplayLayerImpl::DrawDebugRect's
label in the case |debug_rects|'s type is
TOUCH_EVENT_HANDLER_RECT_TYPE.

Bug: 
Change-Id: I7af79e490481b485b11601f7c44cf290d5707e46
Reviewed-on: https://chromium-review.googlesource.com/571032
Commit-Queue: Hayley Ferr <hayleyferr@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Reviewed-by: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487959}

for low-end Android devices.

TBR=piman@chromium.org

Bug: 746018
Change-Id: I40f0dbddd1efc8a751fc3d48c97446e1f04bbeeb
Reviewed-on: https://chromium-review.googlesource.com/576607
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Eric Karl <ericrk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487958}

Added an UMA_HISTOGRAM_ENUMERATION to report how often we hit each touch
action.

Bug: 745718
Change-Id: I21d48c48a30f5b7699b078212ae105d34506c156
Reviewed-on: https://chromium-review.googlesource.com/571270Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Hayley Ferr <hayleyferr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487957}

This is preparation to remove MockCryptohomeClinet,
as preparation to replace Callback by OnceCallback in chromeos/dbus.

BUG=739622
TEST=Ran trybot.

Change-Id: I2c326050e48dae5671a796f152c7e723ccba601d
Reviewed-on: https://chromium-review.googlesource.com/570119
Commit-Queue: Hidehiko Abe <hidehiko@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Reviewed-by: Ryo Hashimoto <hashimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487956}

BUG=575778
TBR=dpranke@chromium.org
NOTRY=true

Change-Id: I7fd31e3bd0b2d35e3a26b49a1a85c45b3efd7315
Reviewed-on: https://chromium-review.googlesource.com/578442Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487955}

These two tests are flaky on the Linux ChromiumOS bot:
https://uberchromegw.corp.google.com/i/chromium.chromiumos/waterfall?show=Linux%20ChromiumOS%20Tests%20(1)

TBR=zork@chromium.org

Bug: 746526
Change-Id: Id2bcf3b9ece0fb25efeff129569d8e96e598ba52
Reviewed-on: https://chromium-review.googlesource.com/578319Reviewed-by: Scott Little <sclittle@chromium.org>
Commit-Queue: Scott Little <sclittle@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487954}

Also, disabes HarfBuzz's atomic refptr TSan warning

Bug: 730692
Change-Id: I69c7fd5ab20896b6abd864506ae394732f8aa6e1
Reviewed-on: https://chromium-review.googlesource.com/544625
Commit-Queue: Fernando Serboncini <fserb@chromium.org>
Reviewed-by: Justin Novosad <junov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487953}