GitLab

In webview, frames with no damage sometimes call AbortDraw to prevent
draws. These aborts should not set did_draw_in_last_frame_ or the
scheduler will request new BeginFrames when it doesn't need to.

This CL stops setting did_draw_in_last_frame_ in AbortDraw while still
setting it in WillDraw.

Bug: 687695
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: I84c39a5e06d578ea92558d81ce2fad5dc423cf75
Reviewed-on: https://chromium-review.googlesource.com/933292
Commit-Queue: James Wallace-Lee <jamwalla@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542229}

Change-Id: Id06be3a64b74d8453fd79cfa5915b4490e943d7c
Reviewed-on: https://chromium-review.googlesource.com/956876Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542228}

changes in this cl:
- For clamshell devices, which we should not turn screen off by tapping the
  power button. Starts the menu animation immediately as press the power button.

- Make the initial opacity in the menu animation not fixed, use the value in
  previous animation.

- Still delay the power menu animation if we should turn screen off by tapping
  the power button. And differeniate the timer fire time according to the initial
  scrern state.

Bug: 799524
Change-Id: Icad6c4e66be2ec41978456862c337ff494bfac00
Reviewed-on: https://chromium-review.googlesource.com/953374Reviewed-by: Dan Erat <derat@chromium.org>
Reviewed-by: Qiang Xu <warx@google.com>
Commit-Queue: min c <minch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542227}

Supports both Oculus Touch (6DoF) and the Oculus Remote (3DoF).
Automatically switches between them as each form of input becomes
active.

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

Currently fails on the libc++ bot with

../../chrome/browser/task_manager/sampling/shared_sampler_win_unittest.cc(144):
    error: Expected: (physical_bytes()) >= (initial_value + allocated_size),
             actual: 15224832 vs 19419136

The reason seems to be that memory use is only counted if the memory is
referenced, and with libc++ the compiler is apparently able to optimize away
the memory's initialization.  Add some reading code to make sure the
memory references remain.

Bug: 801780
Change-Id: I8edef2eda4be8b4344ebc934768ecd58ee39496b
Reviewed-on: https://chromium-review.googlesource.com/956571
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Hans Wennborg <hans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542225}

With this change, a user may both resize and reposition the content
quad when in "repositioning" mode.

Bug: 799270
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_vr;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I86aed8d83db82998c64e982922e21298c6a243ec
Reviewed-on: https://chromium-review.googlesource.com/956499
Commit-Queue: Ian Vollick <vollick@chromium.org>
Reviewed-by: Christopher Grant <cjgrant@chromium.org>
Reviewed-by: Biao She <bshe@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542224}

TrayAccessibilityTest.CheckMenuVisibilityOnDetailMenu was disabled for
flake. The most likely cause is test-only race conditions in sending
session state from the browser to ash.

It does not need to be a browser test. Move it to ash_unittests to
avoid the race conditions and re-enable it.

Bug: 819987
Test: ash_unittests
Change-Id: Iecf37fbb9d0115c5d1f9299e729fb66d193f7048
Reviewed-on: https://chromium-review.googlesource.com/957308Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542223}

Add new histograms to capture per-task-type task duration for different
renderer visibility states separately.

BUG=820494
R=rkaplow@chromium.org
CC=panicker@chromium.org

Change-Id: Icce8e262cc87a4d3f73809abdbcda34a124a1bb9
Reviewed-on: https://chromium-review.googlesource.com/955855Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Commit-Queue: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542222}

These tests are failing on Waterfall for Android Chromium build bot.
Disabling tests.

Bug: chromedriver:2286
Change-Id: I26b53ee52beaa5d942957ed8271b3aa6e3c42ddc
Reviewed-on: https://chromium-review.googlesource.com/956547Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org>
Commit-Queue: Artur Khachatryan <khachatryan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542221}

Bug: 809298
Change-Id: I7d8b5e5e9a792b689129937c912bc16e6ef2e053
Reviewed-on: https://chromium-review.googlesource.com/950139Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Xiaoqian Dai <xdai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542220}

Bug: 819834
Change-Id: I624029d327940f86be4852fbebe7f5a525d72a30
Reviewed-on: https://chromium-review.googlesource.com/953976Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Commit-Queue: Sorin Jianu <sorin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542219}

TBR=nektar@chromium.org

Bug: None
Change-Id: Ie0078dadf64e05ab8c0b9ff53549c4b8a726ad18
Reviewed-on: https://chromium-review.googlesource.com/956295Reviewed-by: Aaron Leventhal <aleventhal@chromium.org>
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542218}

Bug: 758632
Change-Id: I7fc16ec27f1e24978c85c0b4a58970b19ffc5045
Reviewed-on: https://chromium-review.googlesource.com/955924Reviewed-by: Ashley Enstad <ashleymarie@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Emily Hanley <eyaich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542217}

active_tree_needs_first_draw_ was set to false on invalidate so that it
wouldn't block commits. Instead, fallback tick handling guarantees that
every activated frame has a draw. This CL removes the change along with
its associated test (introduced in crrev.com/1092123005).

Bug: 819430
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: Ibf6008512638943b7caa771f7ca6a953851607d6
Reviewed-on: https://chromium-review.googlesource.com/953208Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
Commit-Queue: James Wallace-Lee <jamwalla@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542216}

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

TBR=rockot@chromium.org

No-Tree-Checks: true
No-Try: true
Bug: 820407
Change-Id: Ib10cd0c33aa8ad1725c22e180aa679352cd8883d
Reviewed-on: https://chromium-review.googlesource.com/957462
Commit-Queue: John Budorick <jbudorick@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542214}

A series of tests across viz_browser_tests, viz_content_browsertests, and
viz_content_unittests have been fixed. This change re-enables them.

At the same time it updates the ordering of the filter files to reflect some
recent triaging. Grouping together similar root-cause issues.

TBR=kylechar@chromium.org

Bug: 760181
Change-Id: Ib7040cd995cfdd7d92f3c3e677b87ebcaf920bc5
Reviewed-on: https://chromium-review.googlesource.com/957319
Commit-Queue: Jonathan Ross <jonross@chromium.org>
Reviewed-by: Jonathan Ross <jonross@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542213}

ServiceManager may need to launch child processes before a BrowserMainLoop
has been created, and therefore before any BrowserThreads exists. We
therefore replace the BrowserThread::PROCESS_LAUNCHER with a global
TaskScheduler sequence, created on-demand when the ServiceManager or
ChildProcessLauncherHelper first need it.

Under Windows we must use a single-thread TaskRunner, while on other
platforms we are able to use a normal TaskScheduler sequence. File
crbug.com/820200 to track that.

Bug: 815225
Change-Id: Ia0f46461fb9cc92fddacf81ee96b764de8477d11
Reviewed-on: https://chromium-review.googlesource.com/941264
Commit-Queue: Xi Han <hanxi@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542212}

Animated images may change before invalidation. For example, an
image with SVG animation gets ImageChanged notification
periodically but a paint triggered by some other change may not
just follow an invalidation of the animated image.

Bug: 819683
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I5acb3eedc0ac714a600ac6df752dc22245bf3d1d
Reviewed-on: https://chromium-review.googlesource.com/956303
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542211}

https://pdfium.googlesource.com/pdfium.git/+log/3baef5c6daf5..69da36c5f841

$ git log 3baef5c6d..69da36c5f --date=short --no-merges --format='%ad %ae %s'
2018-03-09 rharrison Explicitly mark helper methods that only operate on ASCII ranges

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: I111e9f1393101c60788b1cf62523606b3d233a42
Reviewed-on: https://chromium-review.googlesource.com/957313
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@{#542210}

Bug: 820419
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: Ibd95ec218a700b7a9a6e34336f4ddee5442f8b02
Reviewed-on: https://chromium-review.googlesource.com/956116Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Luc Ferron <lucferron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542209}

Bug: 820373
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I992efd466f5bcb7f20c0b4045be91b9d0f3704c8
Reviewed-on: https://chromium-review.googlesource.com/956699
Commit-Queue: Katie Dektar <katie@chromium.org>
Reviewed-by: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542208}

This cl revises some Keyboard Shortcut Viewer (KSV) strings based on the
feedback from TC.

Bug: b/74114276, b/74085777, b/74086686, b/74114046
Test: Wait TC to verify.
Change-Id: Idb1a6a3695af135ed6a146c58f7048abfbcc4618
Reviewed-on: https://chromium-review.googlesource.com/956607Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Commit-Queue: Tao Wu <wutao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542207}

https://chromium.googlesource.com/catapult.git/+log/b90b97cf8dec..e490e96cd7f3

$ git log b90b97cf8..e490e96cd --date=short --no-merges --format='%ad %ae %s'
2018-03-08 dtu [dashboard] Add api_auth.Email() function.
2018-03-08 dtu [pinpoint] Delete extraneous patch argument when trying a patch.

Created with:
  roll-dep src/third_party/catapult


The AutoRoll server is located here: https://catapult-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=sullivan@chromium.org

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

Changes:
OnDisplayConfigurationChanged could not distinguish the case of
swapping primary display. We now bind a callback in OnDisplayAdded (
it is called on reconnecting, leaving dock mode, exiting mirror mode)
and run the callback in OnDisplayConfigurationChanged.

Bug: 805046
Test: tested on device and added test coverage
Change-Id: I332c9d368e9df4fc5630317902f2776eab5dc983
Reviewed-on: https://chromium-review.googlesource.com/956928Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Commit-Queue: Qiang Xu <warx@google.com>
Cr-Commit-Position: refs/heads/master@{#542205}

Bug: None
Change-Id: I18438a934cecdb22a4586aee0ccd92db55ff08de
Reviewed-on: https://chromium-review.googlesource.com/947746Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Charlie Harrison <csharrison@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542204}

Many webpages use window.print() immediately followed by window.close()
in JS. This means that the renderer and web contents are torn down
while the PDF is still being converted for the printer on Windows.
However, the web contents are not needed if the full PDF document has
already been rendered, so the PrintViewManager should just release the
query and allow conversion and spooling to complete instead of
cancelling the job.

The CL to send the Print Preview PDF directly to the PrintViewManager
broke this for users that use Print Preview because we no longer store an
extra copy of the web contents in the BackgroundPrintingManager. This has
been broken if using the system dialog since M64 or earlier.

Bug: 820105
Change-Id: I308adba43b3604509275f6c0f2946545b94dd1d5
Reviewed-on: https://chromium-review.googlesource.com/956257
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Reviewed-by: Wei Li <weili@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542203}

The bounding box highlighted by assistive technology
like ZoomText is wrong if the display resolution is not
set to 100%.

BUG=812892,820298

Change-Id: Id488583666c5e01e7aaed5ade7a5a3faeff900cd
Reviewed-on: https://chromium-review.googlesource.com/955545
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542202}

I have a series of CLs in progress to allow StackLayout to support more than two
tab stacks. This CL contains the necessary updates to the geometry logic. After
this CL (and the preceding ones), the only thing keeping StackLayout from
displaying more than two tab stacks is that a lot of the logic is hard coded to
always show all normal tabs in one stack and all incognito tabs in another. I
will split much of StackLayout into a base class in a future CL to allow
creating variants with different behavior.

When we display two tab stacks, we use asymmetric margins: we put one tab stack
up against the edge of the screen (with a small border added by the Stack
itself), and show the edge of the other tab stack on the other side. This CL
does not change the behavior for this case. For three or more stacks, the
behavior I'm going with for now is to make the margins symmetric. So no matter
which stack is focused, we show the current tab centered, with the edge of a
neighboring tab showing on either side if present, or a blank margin on that
side otherwise.

Bug: 648314
Change-Id: I383d9601f521a2eec47263f219027bc23818b3e2
Reviewed-on: https://chromium-review.googlesource.com/940613
Commit-Queue: Ryan Landay <rlanday@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542201}

This CL adds 2 things to JEA interface.

1. Exif. Currently HW JEA only encodes the image with APP0 JFIF segment.
After this CL, it accepts Exif buffer and would insert the APP1 segment
if Exif buffer is provided.

2. IPC compatibility.
IPC from ChromeOS side relies on the buffer ID to identify the encoded
results. The ID of VideoFrame is generated randomly at Chromium side
which ChromeOS doesn't know. The CL changes JEA interface to use output
buffer ID to identify each encode attemp.

BUG=819847
TEST=Verified that JEA can be used from ChromeOS side with Exif buffer.

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: I87f13a435f9875999ca79dd5769fb925a9c59fb8
Reviewed-on: https://chromium-review.googlesource.com/954411
Commit-Queue: Sheng-hao Tsao <shenghao@google.com>
Reviewed-by: Ricky Liang <jcliang@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542200}

This feature is currently defined in content/.
This Cl moves it to components/download to remove download dependency on content/.

BUG=803135

Change-Id: Iabbc34eff56554722d4aa7bde1f461135984ac74
Reviewed-on: https://chromium-review.googlesource.com/955899
Commit-Queue: Min Qin <qinmin@chromium.org>
Reviewed-by: Xing Liu <xingliu@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542199}

Since ArcAppDialg is no longer parented to AppList anymore, remove
checks for parent widget. Also remove related test expectations.

Bug: 820293
Test: Pass browser_test
Change-Id: Iea0732ea329e6552ddb30c557dcc9575821a0394
Reviewed-on: https://chromium-review.googlesource.com/956666
Commit-Queue: Long Cheng <lgcheng@google.com>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542198}

Rename the method to PositionEmptyChildWithParentBfc(), and make it a
const method. Also get rid of unused and unimplemented
PositionWithBfcOffset(const NGBfcOffset&).

Also some fixes in comments and parameter names, and added some comments
on my own.

Moved a DCHECK(is_empty_block) to also hit when
PositionEmptyChildWithParentBfc(), just to be clear about the fact that
the block has to be empty at this point.

Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I7d171aa40d3f3a5705f7a0126725a7905d37c504
Reviewed-on: https://chromium-review.googlesource.com/955645Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542197}

memory_instrumentation is the source of truth for memory metrics. It provides
private_memory_footprint, a cross-platform consistent memory metric.

The previous implementation exposed working_set and committed - Windows specific
measurements, and phys_footprint - a macOS specific measurement.

This CL replaces those metrics with private_memory_footprint. The only place
these numbers are used is to generate a log string, used by the feedback system
and the OOM reporting system.

Change-Id: If39c626605f70e18e6044c7f1d2f0f1a8ce5562a
Bug: 819289
Reviewed-on: https://chromium-review.googlesource.com/951754Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542196}

This is a reland of 65478d12 with
Aura-specific tests moved to a subclass and #ifdef.

Original change's description:
> AppShell: Support reloading
>
> Implement reloading in ExtensionLoader. Uses keep-alives while apps are
> reloading. A future CL will observe these keep-alives to keep app_shell open
> during reload.
>
> Bug: 762642
> Change-Id: Ia20b81378d1aeab4ace119d9d2a8b44c2461fdcf
> Reviewed-on: https://chromium-review.googlesource.com/912694
> Commit-Queue: Michael Giuffrida <michaelpg@chromium.org>
> Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#540079}

Bug: 762642
Change-Id: I6c516c4736ca2327965e034d10717341e23303dc
Reviewed-on: https://chromium-review.googlesource.com/950342
Commit-Queue: Michael Giuffrida <michaelpg@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542195}

BUG=805267

Change-Id: I39a7b31ad3f796cd059bafece3fa851da3e25049
Reviewed-on: https://chromium-review.googlesource.com/954066
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542194}

TBR=sky@chromium.org

Bug: 820390
Change-Id: I78d8234c0fe394fbe2bfe5bb424d0b2b30f87b9e
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/957362Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542193}

https://webrtc.googlesource.com/src.git/+log/5a98049f6abe..a5aa68b73f1d

$ git log 5a98049f6..a5aa68b73 --date=short --no-merges --format='%ad %ae %s'

Created with:
  roll-dep src/third_party/webrtc
BUG=None


The AutoRoll server is located here: https://webrtc-chromium-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.


CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng;master.tryserver.chromium.win:win-msvc-dbg
TBR=webrtc-chromium-sheriffs-robots@google.com

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

The typemap defines this as nullable_is_same_type, but without a SetToNull
method that will result in runtime failures if null is actually passed.

Bug: none
Change-Id: Ife6427121c9f424ab8a2a0c52798f1806b650880
Reviewed-on: https://chromium-review.googlesource.com/956418Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542191}

If an event from libevdev includes a MSC_TIMESTAMP field, send that
timestamp to the gesture library. This field will be used by the gesture
library because it has more accurate time deltas than CLOCK_MONOTONIC.

BUG=b:65041115
TEST=Tested manually on lux and eve, using CL:742488 and CL:938751.
MSC_TIMESTAMP is passed to gesture library if available.

Change-Id: I05e5a6615e10d33bd0e290b6bb8ff11c2f05f2fc
Reviewed-on: https://chromium-review.googlesource.com/817979Reviewed-by: Michael Spang <spang@chromium.org>
Commit-Queue: Sean O'Brien <seobrien@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542190}