GitLab

Equivalent functionality can be achieved by adding a bool without any
additional locking in the IncomingTaskQueue::PostPendingTask path.

One fewer lock is required if there is no need to schedule work.

BUG=749312,758721

Change-Id: I812db615ef2d1772c077266240d3a1927c97565c
Reviewed-on: https://chromium-review.googlesource.com/639158
Commit-Queue: Robert Liao <robliao@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Reviewed-by: Francois Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501441}

Imported because of https://github.com/w3c/web-platform-tests/pull/7312,
so the old names are removed from W3CImportExpectations.

Change-Id: I15db60386e3cc4db04c6816a0dc9e5f670744e17
Reviewed-on: https://chromium-review.googlesource.com/663833
Commit-Queue: Philip Jägenstedt <foolip@chromium.org>
Commit-Queue: Emil A Eklund <eae@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501440}

1. Adds browser tests for heap profiling with pseudo and no stack mode.
2. TraceLog does not dcheck if filters are added multiple times.
Reason: The EnableHeapProfiling() mojo message from browser to renderer
is sent before OnBeginTracing IPC message. The tracing is being
converted to service and maybe we will have better fix in future.
3. Whitelist heap profiling overhead dumps for background mode.

BUG=700245

Change-Id: I73289e4f7ec5de1421ac44e87e7c30d363869b5b
Reviewed-on: https://chromium-review.googlesource.com/653782
Commit-Queue: Siddhartha S <ssid@chromium.org>
Reviewed-by: Primiano Tucci <primiano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501439}

GpuProcessTransportFactory should not be created when running with mus.

BUG=none

Change-Id: I888455b68b9fad81d9e7bbb9b16b683df2abd5a5
Reviewed-on: https://chromium-review.googlesource.com/661337Reviewed-by: kylechar <kylechar@chromium.org>
Reviewed-by: Yuri Wiitala <miu@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501438}

scroll-boundary-behavior is a shorthand containing
scroll-boundary-behavior-x and scroll-boundary-behavior-y.

If only one value is specified, the second value defaults
to the same value.

Spec:
https://wicg.github.io/scroll-boundary-behavior/#scroll-boundary-behavior-properties

BUG=672921

Change-Id: Ib924802ac441f0ddbe9d1f360c7d9d91ff5b80c6
Reviewed-on: https://chromium-review.googlesource.com/662480Reviewed-by: Majid Valipour <majidvp@chromium.org>
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501437}

Bug: 760288
Change-Id: I79e0c682394236aa4a7d2dcd421680e09abef082
Reviewed-on: https://chromium-review.googlesource.com/663793Reviewed-by: Derek Cheng <imcheng@chromium.org>
Commit-Queue: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501436}

This CL fixes several issues in our app metadata that may get us into
trouble passing the Apple review process.

Bug: 756208
Change-Id: I426fce8453bc22059235d77f631ceaf0b7e8642e
Reviewed-on: https://chromium-review.googlesource.com/664058Reviewed-by: Scott Nichols <nicholss@chromium.org>
Commit-Queue: Yuwei Huang <yuweih@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501435}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/a3ef78d9..ec37390b

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: Ia404312eefdd8ae50ec4be4d6f20883322c6ce9e
Reviewed-on: https://chromium-review.googlesource.com/663412Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501434}

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/7370e9da6e0c..49fbcfa16b5d

$ git log 7370e9da6..49fbcfa16 --date=short --no-merges --format='%ad %ae %s'
2017-09-12 eakuefner Add add_reserved_diagnostics script

Created with:
  roll-dep src/third_party/catapult


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.chromium.android:android_optional_gpu_tests_rel
TBR=sullivan@chromium.org

Change-Id: I1759f9998edb55257f75e8d5296473ec24a2a197
Reviewed-on: https://chromium-review.googlesource.com/663843
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501433}

https://pdfium.googlesource.com/pdfium.git/+log/8ac74971a335..5b2092a1ec59

$ git log 8ac74971a..5b2092a1e --date=short --no-merges --format='%ad %ae %s'
2017-09-12 rharrison Don't attempt to decrypt AES streams that are too short

Created with:
  roll-dep src/third_party/pdfium
BUG=763585


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: Idbe0456179d244337dba103a3b55254b920a1b33
Reviewed-on: https://chromium-review.googlesource.com/663943
Reviewed-by: <pdfium-deps-roller@chromium.org>
Commit-Queue: <pdfium-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501432}

Bug: 764428
Change-Id: I051fc470ae57a15c6250aa14657239467852578f
Reviewed-on: https://chromium-review.googlesource.com/663422Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Jacob Dufault <jdufault@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501431}

BUG=753386

Change-Id: I66193175816295ed064689cb74a0f6fd0287a001
Reviewed-on: https://chromium-review.googlesource.com/660721
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501430}

Bug: 754704
Bug: 756668
Change-Id: I8475a6060c3f5de8be5f39c1e8d1ddf4f8c62993
Reviewed-on: https://chromium-review.googlesource.com/651553
Commit-Queue: Randy Smith <rdsmith@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501429}

https://skia.googlesource.com/skia.git/+log/a640c49b7ecf..db91c6e7fbfc

$ git log a640c49b7..db91c6e7f --date=short --no-merges --format='%ad %ae %s'
2017-09-08 csmartdalton Improve heuristics for when to use ccpr

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=stephana@chromium.org

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

When a renderer-initiated navigation is aborted by the browser process
in PlzNavigate, we currently send a FrameMsg_Stop IPC to the renderer
process, in order for the renderer process to know that there is no
longer a pending navigation being processed by the browser. This is
wrong, as it also cancels any ongoing load in the current page. Instead,
this CL introduces a new IPC that will only cancel the dummy provisional
DocumentLoader that was created when the navigation was sent to the
browser.

Continuation of patch:
 * https://codereview.chromium.org/2768813002/ by clamy@.
 * https://chromium-review.googlesource.com/c/chromium/src/+/565261 by
   @ahemery.

This CL adds a test for: https://crbug.com/762945. This bug happens when
a navigation is aborted but keeps the current document alive. All the
pending loads for the current document were canceled when it should not.

Bug:576261,762945

Cq-Include-Trybots: master.tryserver.chromium.linux:linux_site_isolation
Change-Id: I210c5f9132945d81d0c5d7d62fff974597648f20
Reviewed-on: https://chromium-review.googlesource.com/663140Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Camille Lamy <clamy@chromium.org>
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501427}

The removed code is dead and unreachable since the tanper
detection experiment is no longer enabled, and there are no plans
to reenable that experiment.

Bug: 675761
Change-Id: I70465d498111d15e01f6ea8fce784cd28cc8902f
Reviewed-on: https://chromium-review.googlesource.com/663847
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501426}

Bug: 726520
Change-Id: I1aa22fc3617f21a492219681b281e85dfa9d7e3a
Reviewed-on: https://chromium-review.googlesource.com/664079Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Aleks Totic <atotic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501425}

R=sky@chromium.org

Bug: 667892
Change-Id: Ia354d4cc615983d0ac6650a98a70903484e5ecb8
Reviewed-on: https://chromium-review.googlesource.com/657807
Commit-Queue: Gabriel Charette <gab@chromium.org>
Reviewed-by: Brett Wilson <brettw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501424}

94c367a Exclude UTF-16 encoding for automatic detection

BUG=630113
Test=gclient sync, make
TBR=brettw@chromium.org

Change-Id: I8457204afbeb489a8259bda34314b1dca30135fe
Reviewed-on: https://chromium-review.googlesource.com/662082Reviewed-by: Jinsuk Kim <jinsukkim@chromium.org>
Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501423}

Previously MessageLoopHelper was starting a periodic timer that quits 
a run loop. It kept that timer running even after
WaitUntilCacheIoFinished() returns and used QuitCurrentWhenIdleDeprecated().
As result MessageLoopHelper::TimerExpired() would sometimes quit a RunLoop
that's not owned by MessageLoopHelper. This made DiskCache*AsyncIO* tests
flaky on Fuchsia. This change fixes both problems: the timer is stopped
after WaitUntilCacheIoFinished() returns and TimerExpired() uses
RunLoop::Quit(), so it won't quit a wrong RunLoop.

Bug: 731302
Change-Id: Ie7f7444c7f1bb662c1de511cae3de0a9efc46349
Reviewed-on: https://chromium-review.googlesource.com/661357Reviewed-by: Eric Roman <eroman@chromium.org>
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501422}

This will be used to work around Android Bluetooth bugs.

Bug: 764386, 672263
Change-Id: I0e13a94c50c9c91e9f6957917f595ed30a76b7d1
Reviewed-on: https://chromium-review.googlesource.com/663206Reviewed-by: Tim Song <tengs@chromium.org>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501421}

Bug: 734230
Change-Id: I721e6db444b685f56d4cc884995cba3cbddf84ba
Reviewed-on: https://chromium-review.googlesource.com/663844
Commit-Queue: Scott Graham <scottmg@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501420}

This patch fixes not to break before <br> tag, preserved newline and
tabulation characters.

The break-before-space behavior of LazyLineBreakIterator is designed
for strings before whitespace collapsing. Since LayoutNG uses it after
whitespace collapsing was processed, it needs to follow normal break-
after-space behavior for newline and tabulation characters.

This patch adds the 3rd mode, break-before-space for whtiespace
collapsed strings.

Tried to switch to break-after-space mode completely in LayoutNG, but
there are some more work to do the switch, and its performance
implication isn't well understood yet.

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

There are several steps of the Bluetooth connection flow which call into
Bluetooth APIs and wait for an asynchronous response. These asynchronous
callbacks *should* be getting invoked in a timely manner by Bluetooth,
but this is not happening in practice. This CL adds timeouts for each
step of the connection process in which we wait for an asynchronous
reply.

Bug: 763176, 672263
Change-Id: Ia7a538e0de8280346a3c113c7dccd5c18cc7086d
Reviewed-on: https://chromium-review.googlesource.com/657811
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Tim Song <tengs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501418}

Chrome is unconditionally installed in "Program Files (x86)".

BUG=763606

Change-Id: I5c4d81c34a166f61969e0698536636e5bcb6bbf9
Reviewed-on: https://chromium-review.googlesource.com/663257
Commit-Queue: Gabriel Charette <gab@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501417}

This reverts commit d5840e2a.

Reason for revert: CrOS eve is slow to update because eve-release builder hasn't got green for a week, and haven't got the Harfbuzz update yet.

Revert this for now, we'll reland when CrOS is updated. Tracking in crbug.com/763981

Original change's description:
> Implement safe-to-break for ShapingLineBreaker
> 
> Compute offsets where line breaks may occur without requiring re-shaping
> of the two sides by checking the HarfBuzz UNSAFE_TO_BREAK flag and store
> all such suitable offsets in the new safe_to_break vector on the RunInfo
> struct for each run in a ShapeResult.
> 
> This allows for faster and higher quality line breaking as only suitable
> breaking positions are considered candidates for line breaking if at all
> possible. Only re-shapes if a line has no suitable safe-to-break offset.
> 
> Change-Id: Iaa43079152e3c9b42662877f9821c5c125f7bafe
> Reviewed-on: https://chromium-review.googlesource.com/614766
> Commit-Queue: Emil A Eklund <eae@chromium.org>
> Reviewed-by: Koji Ishii <kojii@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#500741}

TBR=eae@chromium.org,kojii@chromium.org

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

Bug: 763981
Change-Id: I0e2ccb3c0ffa469fcda59e56d42b0606fbed8b15
Reviewed-on: https://chromium-review.googlesource.com/663917
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501416}

Bug: 760412
Change-Id: I636562f761b0574369b40b64c0e9f180a1eed1e5
Reviewed-on: https://chromium-review.googlesource.com/663675Reviewed-by: Ryan Sleevi <rsleevi@chromium.org>
Commit-Queue: Eric Roman <eroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501415}

https://boringssl.googlesource.com/boringssl/+log/e3bb51cb2360fca5b87d559fc263b2763bd14739..683ffbbe57de2163b24993e0d03650cf393bc640

BUG=none

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

https://chromium.googlesource.com/angle/angle.git/+log/9d81537..9df395c

BUG=762377,chromium:764036

TBR=cwallez@chromium.org

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: Ifb7bc5b6ea8c4a1495e17269e23ed74d3e36d705
Reviewed-on: https://chromium-review.googlesource.com/664078Reviewed-by: Geoff Lang <geofflang@chromium.org>
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501413}

This reverts commit 3b6c1aa7.

Reason for revert: SUMMARY: AddressSanitizer: heap-use-after-free chromeos/network/network_state.h:56:33 in visible

Original change's description:
> NetworkStateHandler: Add EnsureCellularNetwork
> 
> This CL provide support for Cellular devices with no service:
> * Cellular networks all use the same specifier so that the guid
>   remains consistent (we only support one Cellular Service)
> * Assume a SIM may be present unless Cellular.NetworkTechnology
>   is CDMA so that the SIM UI shows up even if NetworkTechnology
>   is unset (e.g. because there is no Service).
> * Create a dummy Cellular NetworkState when none exists so that
>   Cellular Device properties are translated and passed to the UI.
>   This also allows Cellular network UI to be shown so that
>   Device properties can be viewed and SIM and FoundNetworks may
>   be selected.
> 
> Bug: 717063
> Change-Id: I1e23e7ba48821124ad219bb67fea2ca86e2d6ccd
> Reviewed-on: https://chromium-review.googlesource.com/653723
> Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
> Reviewed-by: Ben Chan <benchan@chromium.org>
> Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#501337}

TBR=stevenjb@chromium.org,benchan@chromium.org,khorimoto@chromium.org

Change-Id: I073a95d8160812923cbcc192f0afe934db672a40
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 717063
Reviewed-on: https://chromium-review.googlesource.com/662958Reviewed-by: Bruce Dawson <brucedawson@chromium.org>
Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501412}

Process for this was to look at the bot currently running
blink_perf.owp_storage, and see if the bot had time. This is fairly
manual right now; in the future we'll make this much more automated.

Bug: 762468
Change-Id: I259a72919f113e99cf0dea8f3881059401271f79
Reviewed-on: https://chromium-review.googlesource.com/663837Reviewed-by: Ned Nguyen <nednguyen@google.com>
Reviewed-by: Emily Hanley <eyaich@chromium.org>
Commit-Queue: Stephen Martinis <martiniss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501411}

Currently we mark targets as 'other' based on WebContents being present
in TabStripModel, which is timing-dependent. This patch marks everything
not quialified for other types as 'page', making target type consistent.

Bug: 759783
Change-Id: I0b26ee12474b004121e3e0083d67eb809b4eba11
Reviewed-on: https://chromium-review.googlesource.com/639024Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Commit-Queue: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501410}

Bug=713655

Change-Id: I0f5d91caf5568bfd2048c4895b45c9ab58067380
Reviewed-on: https://chromium-review.googlesource.com/651549
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501409}

Add a feature flag ("OverflowIconsForMediaControls") to
hide/show icons on the overflow menu displayed on the
native media controls.

BUG=763301

Change-Id: I719e46b690ca52d5bfdd3619c18cbd1f1d9ebd2b
Reviewed-on: https://chromium-review.googlesource.com/659917Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Commit-Queue: Becca Hughes <beccahughes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501408}

cert_verify_proc_builtin.cc, cert_verify_proc_android.cc, cert_issuer_source_aia.cc

Bug: 
Change-Id: I94988d1de99cb8395701b4ce50c302cb504a51d3
Reviewed-on: https://chromium-review.googlesource.com/662157Reviewed-by: Eric Roman <eroman@chromium.org>
Commit-Queue: Matt Mueller <mattm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501407}

Revert changes to gl_tests that worked around the missing default
framebuffer.

BUG=665521

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: I8d7f69790eba8a8a13c240708e3143b726c7e05c
Reviewed-on: https://chromium-review.googlesource.com/639193Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501406}

This CL removes SDCH code from src/chrome/.

This CL is one of the CLs to remove SDCH from Chromium.

SDCH has been disabled in Chrome since M59. For more details please see
Issue 690070 and blink-dev@ thread linked below.

Bug: 762686
Change-Id: If9dbf8ce17aa026f9b0f2ce631669756f4be1e28
Reviewed-on: https://chromium-review.googlesource.com/663621
Commit-Queue: Helen Li <xunjieli@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501405}

In my previous attempt to fix Japanese keyboard behavior
(https://chromium-review.googlesource.com/636107),
I was finishing composition text *after* restoring deleted text.
This works on most Japanese keyboards, but Google Japanese keyboard
behaves weirdly, as it calls setComposingText([text], 1) again which
moves the cursor position.

This can be fixed by finishing composition first, and then restoring
text.

BUG=758443

Change-Id: I1f3f4b64e1fa6aa6bdec198f4693be919e50681e
Reviewed-on: https://chromium-review.googlesource.com/663202Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Changwan Ryu <changwan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501404}

UDPSocketTest.PartialRecv depends on MSG_TRUNC, which wasn't supported
in older versions of SDK. The test needs to be disabled temporarily
because the recent SDK roll had to be reverted.

TBR=scottmg@chromium.org
NOTRY=true

Bug: 731302
Change-Id: I5b4ec03ccabb60d1719ce2088831183a8a54c045
Reviewed-on: https://chromium-review.googlesource.com/662881
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Scott Graham <scottmg@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501403}

This patch removes the gaming seat implementation for evdev. All the
gamepad support will use ozone implementation.

This patch also removes the dummy interface for gaming_input_v1 in Wayland
server. The dummy interface was there to make sure the system is robust
when we moved the protocol to v2.

Bug: 717246
Change-Id: I70b29d3c6a81761d1e15c502f78fd0615bf768fe
Reviewed-on: https://chromium-review.googlesource.com/661100
Commit-Queue: Jingkui Wang <jkwang@google.com>
Reviewed-by: David Reveman <reveman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501402}