GitLab

Using wpt-import in Chromium f6009cbd.
With Chromium commits locally applied on WPT:
14350ac7 "[PE] Don't truncate table cell's padding"


Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/13486

Note to sheriffs: This CL imports external tests and adds
expectations for those tests; if this CL is large and causes
a few new failures, please fix the failures by adding new
lines to TestExpectations rather than reverting. See:
https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md

Directory owners for changes in this CL:
domenic@chromium.org, ricea@chromium.org:
  external/wpt/streams
rouslan@chromium.org, mathp@chromium.org:
  external/wpt/payment-request

TBR=robertma

No-Export: true
Change-Id: I033e56672564886214422c5a25725ef3e0254b5b
Reviewed-on: https://chromium-review.googlesource.com/956024
Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Reviewed-by: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541889}

Fix errorprone NarrowingCompoundAssignment warnings and make
sure it is treated as error after this CL.

http://errorprone.info/bugpattern/NarrowingCompoundAssignment

Bug: 801268

Change-Id: Ief55318e789176288962359566d708af51c7c890
Reviewed-on: https://chromium-review.googlesource.com/953181Reviewed-by: Peter Wen <wnwen@chromium.org>
Reviewed-by: Joe Downing <joedow@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Rob Buis <rob.buis@samsung.com>
Cr-Commit-Position: refs/heads/master@{#541888}

Crash dumps contain sensitive data.

Bug: b/74372631
Test: kill -SEGV cast_shell and check for successful upload

Change-Id: I2c3877477bd652708838124ae43d1e24766e8edf
Reviewed-on: https://chromium-review.googlesource.com/955342
Commit-Queue: Michael Spang <spang@chromium.org>
Reviewed-by: Stephen Lanham <slan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541887}

changes:
Enable the feature by default. Also fix the bug that window cannot be
moved. display::CreateDisplayIdList is sorting using the first 8 bits,
pass that comparator to std::upper_bound too.

TBR=stevenjb@chromium.org

Bug: 778438
Test: tested on device.
Change-Id: Ic8b9df780f99f0466805f8857e2cb0414a163999
Reviewed-on: https://chromium-review.googlesource.com/954361
Commit-Queue: Qiang Xu <warx@google.com>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Qiang Xu <warx@google.com>
Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541886}

This scripts lives in depot_tools.

Bug: 759146
Change-Id: I3877d3b53ef2f91b34cebb61b04e6f285a006ae7
Reviewed-on: https://chromium-review.googlesource.com/911428
Commit-Queue: Sébastien Marchand <sebmarchand@chromium.org>
Reviewed-by: Lutz Justen <ljusten@chromium.org>
Reviewed-by: Sasha Morrissey <sashab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541885}

Bug: 773295
Change-Id: Id129cea8341c14bd8da4b5374034423223f03859
Reviewed-on: https://chromium-review.googlesource.com/884063
Commit-Queue: Mark Pilgrim <pilgrim@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541884}

We missed this line when we add the tail processing change. Let's add
it back in.

Bug: 731518
Change-Id: Id90cade41f311309ef60f049094478de0ad4c19e
Reviewed-on: https://chromium-review.googlesource.com/956318Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541883}

This should speed up the wall time of these browser tests significantly
h/t to jkarlin for discovering this issue.

Bug: 819721
Change-Id: I5368234cd3ea729eb262af22233df496e1368c4b
Reviewed-on: https://chromium-review.googlesource.com/953803Reviewed-by: Josh Karlin <jkarlin@chromium.org>
Commit-Queue: Charlie Harrison <csharrison@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541882}

BUG=714018

Change-Id: Ic6fa05a2ebd6ca21bd1b2a349a58f7a419a3465d
Reviewed-on: https://chromium-review.googlesource.com/952991Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541881}

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

Replaces the whole call chain for ShowUnhandledTapUIIfNeeded
between Blink and Chrome/WebView with Mojo messaging.

Removes the Blink WebTappedInfo class in favor of a new UnhandledTapInfo
that sends a Mojo construct of the same name to the Browser which
has a service installed via a RenderHostFrame observer.

All functionality should remain unchanged.

NEW CODE:
The CSTabHelper now creates an UnhandledTapWebContentsObserver that
connects the Mojo service via UnhandledTapNotifierImpl.  That Impl
calls back through Java to the CSTabHelper to the CSManager to notify
that a Tap has occurred.  The CSTabHelper ignores these notifications
when CS is disabled.

The mojo message is only sent to the browser if the tap is unhandled
and the other required conditions are met.

UPDATED TESTS:
Test notification is now done through mojo messaging, so we now only
know if the tap was unhandled, not whether the page changed or other
details about why the tap was unhandled.

Updated the test page by adding nodes that do not trigger, and removed
the mousemove handler since it's unrelated to tap handling.

BUG=754862

TBR=dcheng@chromium, yfriedman@chromium.org, kinuko@chromium.org

Original CL:

Reviewed-on: https://chromium-review.googlesource.com/841544Reviewed-by: Yoichi Osato <yoichio@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/952679
Commit-Queue: Donn Denman <donnd@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#541569}
Change-Id: I4da1704fe17fae6fe06d8a6167fbf9bc75a01303
Reviewed-on: https://chromium-review.googlesource.com/956086Reviewed-by: Donn Denman <donnd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541879}

This should fix the builder.
And there's no good reason to build all if chromium.webrtc doesn't.

Bug: chromium:820041
TBR: machenbach@chromium.org
No-Try: True
Change-Id: Id581397d0c1821dd17a0b76df540128ad71028ab
Reviewed-on: https://chromium-review.googlesource.com/955683
Commit-Queue: Oleh Prypin <oprypin@chromium.org>
Reviewed-by: Patrik Höglund <phoglund@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541878}

Bug: 244951
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I2dd6d733dff382548f1dc6e558ff5ae9973a209c
Reviewed-on: https://chromium-review.googlesource.com/952957
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Toni Barzic <tbarzic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541877}

The second phase of the post-quantum latency experiment involves sending
and receiving dummy data. We will deploy some number of public servers
that will echo the padding extension and this change adds latency
measurements for those cases.

Since the latency of servers that support echoing the extension will be
different from the latency of all TLS servers, we cannot use the
existing, general latency histogram for this and our control group will
send a 1-byte extension rather than no extension at all.

Bug: 801302
Change-Id: I017324047f66f0889df247b6581670f44e9e5fb5
Reviewed-on: https://chromium-review.googlesource.com/954329Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: David Benjamin <davidben@chromium.org>
Commit-Queue: Adam Langley <agl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541876}

Another round of the rebaseline from the bot result after CL:956162
and CL:956202 were landed.

This series of rebaselines are probably from CL:933805 that rounds
glyph positions when not sub-pixel positioning.

TBR=eae@chromium.org
NOTRY=true

Bug: 591099
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I13c41951f35129915a6eb939d965c10aa13be963
Reviewed-on: https://chromium-review.googlesource.com/954646
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541875}

Bug: 792131, 728324
Change-Id: I3b2ebe4a2073b6a03193dac5c497dbd3c53fc06d
Reviewed-on: https://chromium-review.googlesource.com/955726Reviewed-by: Reid Kleckner <rnk@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541874}

Not used anymore.

BUG=chromium:469980
TEST=manual

Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Ia5837d0b26dfac93e6de456be2625877da24eb69
Reviewed-on: https://chromium-review.googlesource.com/951222Reviewed-by: Denis Kuznetsov <antrim@chromium.org>
Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Commit-Queue: Roman Sorokin <rsorokin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541873}

The C++ standard doesn't allow implicit conversion of function pointers
(such as returned by GetProcAddress()) to void*.  MSVC does accept that,
and so does clang-cl (albeit with a warning).  To fix the warning,
just make LoadComBaseFunction() return FARPROC.

Bug: 550065
Change-Id: I95eeed86c31d45358aabc31414435ae79a1a0e5c
Reviewed-on: https://chromium-review.googlesource.com/955905Reviewed-by: Robert Liao <robliao@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541872}

BUG=808113

Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: Idba2b2dd7777db94281a766030edfa5ed3bef801
Reviewed-on: https://chromium-review.googlesource.com/954057Reviewed-by: Eugene But <eugenebut@chromium.org>
Commit-Queue: Peter Lee <pkl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541871}

BUG=811828
BUG=811794
BUG=811791
BUG=811823
BUG=811871
BUG=811830
BUG=812108
BUG=811867
BUG=811817
BUG=811800
BUG=811826
BUG=811833
BUG=811805
BUG=811824
BUG=811793
BUG=811868
BUG=811783
BUG=811818
BUG=811788
BUG=811784

Change-Id: I29ae4adcb3bb63dbe58e8a3de0c5fbb80a356978
Reviewed-on: https://chromium-review.googlesource.com/953087Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541870}

The original CL is http://crrev/c/923021, we split ClassRegister out
from that CL. This is the rest part.

Since Chrome uses SurfaceView for compositing, we will get nothing from
the ContentView passed to |SelectionPopupController| in
|HandleObserver|.

In this CL, we are passing SurfaceView to HandleObserver from
|CompositorViewHolder| through |WindowAndroid| if it's Chrome's case.

We set a flag to |SelectionPopupController| to let it know whether we
need to use SurfaceView.

Bug: 805531
Change-Id: I2c732231dd161a92d73b29be7f1ab546140eb41b
Reviewed-on: https://chromium-review.googlesource.com/953172Reviewed-by: David Trainor <dtrainor@chromium.org>
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Changwan Ryu <changwan@chromium.org>
Commit-Queue: Shimi Zhang <ctzsm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541869}

This reverts commit 69feeeb9 , as well as
 commit 182f8382 ("Fix 2 access violation
in resource_coordinator.")

There's also a few minor fixes to fix the presubmits:

- tab_manager_delegate_chromeos.cc:144 : Bind -> BindOnce
- tab_manager.cc: prepend the crbug urls with https://
- Fix a few minor revert conflicts caused by
    ddf2a4e4:
    - tab_manager.h: conflict in the "FRIEND_TEST_ALL_PREFIXES"
      declarations.
    - tab_manager_browsertest.cc: Conflict in the anonymous namespace
      at the top of the file.

TBR: thestig@chromium.org
Bug: 818454, 819973, 820065
Change-Id: I7c6307859d565769d239ef43c30fb50e5a797467
Reviewed-on: https://chromium-review.googlesource.com/955923
Commit-Queue: Sébastien Marchand <sebmarchand@chromium.org>
Reviewed-by: Chris Hamilton <chrisha@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541868}

https://pdfium.googlesource.com/pdfium.git/+log/04d792fb7510..507fb4ed09d5

$ git log 04d792fb7..507fb4ed0 --date=short --no-merges --format='%ad %ae %s'
2018-03-08 dsinclair Convert Before{Selection|Value}Change to return a bool
2018-03-08 dsinclair Remove BeforeFormImportData and BeforeFormReset
2018-03-08 dsinclair Remove uncalled AfterFormImportData

Created with:
  roll-dep src/third_party/pdfium


The AutoRoll server is located here: https://pdfium-roll.skia.org

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

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


TBR=dsinclair@chromium.org

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

Call it as appropriate in pdf_extension_test.cc

Split off from https://chromium-review.googlesource.com/c/chromium/src/+/922727
so as to get a baseline before making further changes.

Bug: 809614
Change-Id: I85e947230fd4f87547dac169e2271c2510c41b29
Reviewed-on: https://chromium-review.googlesource.com/953712
Commit-Queue: Tom Sepez <tsepez@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541866}

The current code includes chromecast/base, but doesn't have a GN
dependency on it.

I didn't catch this earlier because I missed turning on ENABLE_GN_CHECK
while testing locally. I wonder if that should be on by default..?

BUG=internal 73746352
TEST=Build libcast_media_1.0_avsync with ENABLE_GN_CHECK

Change-Id: I89b0103156c50f83056a5b3be5526396e0f26cd4
Reviewed-on: https://chromium-review.googlesource.com/956228
Commit-Queue: Mina Almasry <almasrymina@chromium.org>
Commit-Queue: Kenneth MacKay <kmackay@chromium.org>
Reviewed-by: Sergey Volk <servolk@chromium.org>
Reviewed-by: Kenneth MacKay <kmackay@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541865}

This patch fixes list marker positioning when the first child of
the list item is block-level, and the child does not produce a
baseline. Before this patch, list marker is positioned at the
synthesized baseline. This is not well-defined, but 3 browsers
positions the list marker at the first child that has a baseline.
This is filed to CSS WG at
https://github.com/w3c/csswg-drafts/issues/2417.

By doing so, a new case appears where there are no children that
has a baseline. This case is also not well-defined and non-
interoperable. Blink/Edge/WebKit creates an empty line box in
this case, but this isn't easy as we have to insert an empty
line box before the children we have already laid out. This
patch follows Gecko behavior to position the list marker at the
top of the list item.

Also, whether list marker should affect block size or not is not
defined and not interoperable. For now, this patch includes the
list marker block size into list item's block size because it
looks more reasonable to me, and Blink/Edge/WebKit do so. This
is filed as:
https://github.com/w3c/csswg-drafts/issues/2418

SetListMarkerPosition() is a left over in the last patch and
therefore this patch removed it.

Some tests turn to good, though they need to rebaseline due to
list marker image differences.

Bug: 725277
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: If47ab7daea214c0593a917a0c8f505274dae5ca2
Reviewed-on: https://chromium-review.googlesource.com/952843
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541864}

Now that we aren't crashing when destroying the compositor, crashes in
RWHVMac::Hide are cropping up.

Also check for shut-down during occlusion and un-occlusion (those are
not in the crash logs, but it's hard to prove that they couldn't be
called).

Bug: 805726
Change-Id: I2a45db2a86aa09e9bfc8b01fee4018dfbdf257ed
Reviewed-on: https://chromium-review.googlesource.com/954061Reviewed-by: Trent Apted <tapted@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541863}

Bug: 710660
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I2a43c8a51c6702d2e79e05b72162133d18f82041
Reviewed-on: https://chromium-review.googlesource.com/949419
Commit-Queue: Esmael El-Moslimany <aee@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541862}

Simple file move, no functional changes

BUG=803135

Change-Id: I023c36ebc58adf2e623e2a75eabb3c033aadbd63
Reviewed-on: https://chromium-review.googlesource.com/952276
Commit-Queue: Min Qin <qinmin@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541861}

Test: manual
Bug: 818373
Change-Id: I05efc0528fbee5d088947fc2893267d4a601ba93
Reviewed-on: https://chromium-review.googlesource.com/951633Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541860}

Bug: 804559
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I6af3cfb03402cb9099902f87abe5ebf0948d9ec0
Reviewed-on: https://chromium-review.googlesource.com/955344
Commit-Queue: edchin <edchin@chromium.org>
Reviewed-by: edchin <edchin@chromium.org>
Reviewed-by: Mark Cogan <marq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541859}

Previously, BidiCharacterRun used LayoutPartition, which is not thread
safe. GIven that now OffscreenCanvas can render text in a thread, those
runs need to be allocated/deleted from different threads.

Tested performance was neutral.

Bug: 799362
Change-Id: Id8766e23d4be1a41effeeb8956fa1b3e06dc49a3
Reviewed-on: https://chromium-review.googlesource.com/953331
Commit-Queue: Fernando Serboncini <fserb@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541858}

This change is to make the generate_buildbot_json script work for
downstream jsons.

Bug: 803245
Change-Id: I63180304d8bb0fe0b4061565e3ce925d02901a70
Reviewed-on: https://chromium-review.googlesource.com/938315Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Zhiling Huang <hzl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541857}

A comment in video_decode_accelerator.h had an unneeded backslash.
Remove it.

Bug: 819294

Change-Id: I89065637311795b420474d2722330c3fe687d99a
Reviewed-on: https://chromium-review.googlesource.com/944410
Commit-Queue: Dan Sanders <sandersd@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541856}

When a user clicks "Never save password" no username/password should be recorded. Due to a bug when the page prefills some values there were stored. Now let's iterate the blacklisted credentials and clean those values.

Bug: 817754
Change-Id: I68d811ef26d7d17ffd99031897bb01750b86f14b
Reviewed-on: https://chromium-review.googlesource.com/951607
Commit-Queue: Vasilii Sukhanov <vasilii@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541855}

This CL replaces anonymous classes with lambdas in
FirstRunIntegrationTest without any changes to the behavior.

Bug: None
Change-Id: I0ab8e9bc38f6c1dec82c65480b2ccf71eda5538a
Reviewed-on: https://chromium-review.googlesource.com/955563Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: Boris Sazonov <bsazonov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541854}

742 failures started since the build #4133. Among that, 278 are
text-only failures.

This patch rebaselines text-only failures that have matched images
using the same process as CL:945184.

TBR=eae@chromium.org
NOTRY=true

Bug: 591099
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I0f79a7e2f3b02d6de56d36b9691ae46caa4fb3c5
Reviewed-on: https://chromium-review.googlesource.com/956202
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541853}

We sometimes need FrameTokens associated with a CompositorFrame submission.
However on a given frame there may be multiple sources requesting a token. This
change creates FrameTokenAllocator which only provides one incrementation to the
FrameToken per frame submission.

Bug: 775103
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: I161bee7f4bf0641ebd658cd0e0e7ca707d55f015
Reviewed-on: https://chromium-review.googlesource.com/931992Reviewed-by: Jonathan Ross <jonross@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Reviewed-by: Saman Sami <samans@chromium.org>
Commit-Queue: Jonathan Ross <jonross@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541852}

In interactive ui tests we generate events using
RemoteEventDispatcher. When there is capture we need to ensure the
location matches what happens on device, otherwise we won't find the
right target.

BUG=817112
TEST=covered by tests

Change-Id: Ic47b316058282db85d83b348f3b346f2132cd9a1
Reviewed-on: https://chromium-review.googlesource.com/955925
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541851}

This removes all dependencies on ash and moves the code to
ash/components/fast_ink.

Minor changes needed to accomplish this:

- Remove ash switch that could be used to set estimated
  presentation time. This was never actually used and can be
  restored in the future if needed.

- Always use unverified sync tokens. Unlikely to have a
  performance impact as fast ink doesn't rely on GL compositing
  for low-latency.

- Minor refactor to code that detects if input event is in the
  stylus tools area.

Bug: 814908
Test: ash_unittests --gtest_filter=FastInk*
Change-Id: I2a668b92d92726025510e1bf636c20b334c78500
Reviewed-on: https://chromium-review.googlesource.com/932626
Commit-Queue: David Reveman <reveman@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Vladislav Kaznacheev <kaznacheev@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541850}