Removed android scrolling fake mouse moves and device_supports_mouse

Removed android scrolling fake mouse moves and device_supports_mouse

When a user scrolls we need to generate fake mouse moves since the cursor is moving
relative to the page (for example you might scroll over an element that has an
mouseover event listener). Currently Android and blink have separate code-paths for
generating these fake mouse moves. This CL removes the Android specific code-path
and makes Android use the Blink code-path.

In order to make the Blink codepath activate on Android, delete the deviceSupportsMouse
websetting which was exclusively used to disable this fake-mouse-move codepath.
It's sufficient to rely on mousePositionUnknown instead, which disables the
codepath if no mousemove event was ever received.

BUG=492738
Committed: https://crrev.com/83fa786d1e7ee06d2771b7026da0041c9f68c702
Cr-Commit-Position: refs/heads/master@{#438691}

[amaralp, 2016-11-30 00:16:42]

The CQ bit was checked by amaralp@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-11-30 00:17:57]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-11-30 02:20:39]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-11-30 02:20:39]

Dry run: Try jobs failed on following builders:
  blimp_linux_dbg on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build
URL)
  cast_shell_linux on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build
URL)
  chromeos_amd64-generic_chromium_compile_only_ng on
master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL)
  chromeos_daisy_chromium_compile_only_ng on master.tryserver.chromium.linux
(JOB_TIMED_OUT, no build URL)
  chromeos_x86-generic_chromium_compile_only_ng on
master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL)
  linux_chromium_chromeos_compile_dbg_ng on master.tryserver.chromium.linux
(JOB_TIMED_OUT, no build URL)
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_TIMED_OUT, no build URL)
  linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux
(JOB_TIMED_OUT, no build URL)
  linux_chromium_clobber_rel_ng on master.tryserver.chromium.linux
(JOB_TIMED_OUT, no build URL)
  linux_chromium_compile_dbg_ng on master.tryserver.chromium.linux
(JOB_TIMED_OUT, no build URL)

[amaralp, 2016-12-01 19:24:33]

The CQ bit was checked by amaralp@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-12-01 19:25:19]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[amaralp, 2016-12-01 19:33:18]

Description was changed from

==========
Removed android scrolling and device_supports_mouse

BUG=492738
==========

to

==========
When a user scrolls we need to generate fake mouse moves since the cursor is
moving relative to the page (for example you might scroll over an element that
has an mouseover event listener). Currently Android and blink have separate
code-paths for generating these fake mouse moves. This CL removes the Android
specific code-path and makes Android use the blink code-path.

BUG=492738
==========

[amaralp, 2016-12-01 19:33:19]

amaralp@chromium.org changed reviewers:
+ aelias@chromium.org

[amaralp, 2016-12-01 19:33:35]

Description was changed from

==========
When a user scrolls we need to generate fake mouse moves since the cursor is
moving relative to the page (for example you might scroll over an element that
has an mouseover event listener). Currently Android and blink have separate
code-paths for generating these fake mouse moves. This CL removes the Android
specific code-path and makes Android use the blink code-path.

BUG=492738
==========

to

==========
When a user scrolls we need to generate fake mouse moves since the cursor is
moving
relative to the page (for example you might scroll over an element that has an
mouseover event listener). Currently Android and blink have separate code-paths
for
generating these fake mouse moves. This CL removes the Android specific
code-path
and makes Android use the blink code-path.

BUG=492738
==========

[amaralp, 2016-12-01 19:45:00]

The CQ bit was checked by amaralp@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-12-01 19:45:37]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[amaralp, 2016-12-01 20:25:32]

PTAL

[commit-bot: I haz the power, 2016-12-01 21:43:42]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-01 21:43:43]

Dry run: This issue passed the CQ dry run.

[aelias_OOO_until_Jul13, 2016-12-02 05:21:22]

Description was changed from

==========
When a user scrolls we need to generate fake mouse moves since the cursor is
moving
relative to the page (for example you might scroll over an element that has an
mouseover event listener). Currently Android and blink have separate code-paths
for
generating these fake mouse moves. This CL removes the Android specific
code-path
and makes Android use the blink code-path.

BUG=492738
==========

to

==========
Removed android scrolling fake mouse moves and device_supports_mouse

When a user scrolls we need to generate fake mouse moves since the cursor is
moving
relative to the page (for example you might scroll over an element that has an
mouseover event listener). Currently Android and blink have separate code-paths
for
generating these fake mouse moves. This CL removes the Android specific
code-path
and makes Android use the blink code-path.

BUG=492738
==========

[aelias_OOO_until_Jul13, 2016-12-02 05:27:48]

Description was changed from

==========
Removed android scrolling fake mouse moves and device_supports_mouse

When a user scrolls we need to generate fake mouse moves since the cursor is
moving
relative to the page (for example you might scroll over an element that has an
mouseover event listener). Currently Android and blink have separate code-paths
for
generating these fake mouse moves. This CL removes the Android specific
code-path
and makes Android use the blink code-path.

BUG=492738
==========

to

==========
Removed android scrolling fake mouse moves and device_supports_mouse

When a user scrolls we need to generate fake mouse moves since the cursor is
moving
relative to the page (for example you might scroll over an element that has an
mouseover event listener). Currently Android and blink have separate code-paths
for
generating these fake mouse moves. This CL removes the Android specific
code-path
and makes Android use the Blink code-path.

In order to make the Blink codepath activate on Android, delete the
deviceSupportsMouse
websetting which was exclusively used to disable this fake-mouse-move codepath.
It's sufficient to rely on mousePositionUnknown instead, which disables the
codepath if no mousemove event was ever received.

BUG=492738
==========

[aelias_OOO_until_Jul13, 2016-12-02 05:32:50]

aelias@chromium.org changed reviewers:
+ avi@chromium.org, bokan@chromium.org

[aelias_OOO_until_Jul13, 2016-12-02 05:33:14]

lgtm, adding more OWNERS:

avi@ for trivial content/public/common removal
bokan@ for Source/core

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
File third_party/WebKit/Source/web/WebSettingsImpl.h (right):

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/web/WebSettingsImpl.h:83: // FIXME: Replace these two
with pointer/hover queries? crbug.com/441813
"Replace this"

[Avi (use Gerrit), 2016-12-02 15:32:48]

lgtm

Nuke away.

[bokan, 2016-12-02 18:04:05]

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Layo...
File
third_party/WebKit/LayoutTests/fast/events/touch/scroll-without-mouse-lacks-mousemove-events.html
(right):

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Layo...
third_party/WebKit/LayoutTests/fast/events/touch/scroll-without-mouse-lacks-mousemove-events.html:15:
window.addEventListener("mousemove", listener, false);
Is there a converse test? That scrolling after moving the mouse causes
mousemoves?

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
File third_party/WebKit/Source/core/dom/Document.cpp (right):

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/core/dom/Document.cpp:3833: if (frame() &&
!frame()->eventHandler().isMousePositionUnknown())
Move this into scheduleHoverStateUpdate.

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
File third_party/WebKit/Source/core/input/EventHandler.cpp (left):

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/core/input/EventHandler.cpp:364: if
(m_mouseEventManager->isMousePositionUnknown())
This can still get called after layout and style changes and some other places.
I think this should still be left in. Or DCHECK that the mouse position is known
and make sure we can never queue this task if it's unknown.

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
File third_party/WebKit/Source/web/DevToolsEmulator.cpp (left):

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/web/DevToolsEmulator.cpp:461:
m_webViewImpl->page()->settings().setDeviceSupportsMouse(
We should probably clear the last known mouse location here to prevent
dispatching the fake mouse moves when emulating Android.

[amaralp, 2016-12-02 23:00:36]

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Layo...
File
third_party/WebKit/LayoutTests/fast/events/touch/scroll-without-mouse-lacks-mousemove-events.html
(right):

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Layo...
third_party/WebKit/LayoutTests/fast/events/touch/scroll-without-mouse-lacks-mousemove-events.html:15:
window.addEventListener("mousemove", listener, false);
On 2016/12/02 at 18:04:04, bokan wrote:
> Is there a converse test? That scrolling after moving the mouse causes
mousemoves?

Yes,
https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/fast/even....

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
File third_party/WebKit/Source/core/dom/Document.cpp (right):

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/core/dom/Document.cpp:3833: if (frame() &&
!frame()->eventHandler().isMousePositionUnknown())
On 2016/12/02 at 18:04:05, bokan wrote:
> Move this into scheduleHoverStateUpdate.

Done.

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
File third_party/WebKit/Source/core/input/EventHandler.cpp (left):

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/core/input/EventHandler.cpp:364: if
(m_mouseEventManager->isMousePositionUnknown())
On 2016/12/02 at 18:04:05, bokan wrote:
> This can still get called after layout and style changes and some other
places. I think this should still be left in. Or DCHECK that the mouse position
is known and make sure we can never queue this task if it's unknown.

The next if statement already does this check through
FrameView::shouldSetCursor().

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
File third_party/WebKit/Source/web/DevToolsEmulator.cpp (left):

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/web/DevToolsEmulator.cpp:461:
m_webViewImpl->page()->settings().setDeviceSupportsMouse(
On 2016/12/02 at 18:04:05, bokan wrote:
> We should probably clear the last known mouse location here to prevent
dispatching the fake mouse moves when emulating Android.

 I checked locally and no fake mouse moves are dispatched during emulation even
without the clearing.

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
File third_party/WebKit/Source/web/WebSettingsImpl.h (right):

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/web/WebSettingsImpl.h:83: // FIXME: Replace these two
with pointer/hover queries? crbug.com/441813
On 2016/12/02 at 05:33:14, aelias_OOO_until_Dec1 wrote:
> "Replace this"

Done.

[bokan, 2016-12-07 00:09:53]

Sorry for delay, feel free to ping me if it takes more than 24h to review.

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Layo...
File
third_party/WebKit/LayoutTests/fast/events/touch/scroll-without-mouse-lacks-mousemove-events.html
(right):

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Layo...
third_party/WebKit/LayoutTests/fast/events/touch/scroll-without-mouse-lacks-mousemove-events.html:15:
window.addEventListener("mousemove", listener, false);
On 2016/12/02 23:00:35, amaralp wrote:
> On 2016/12/02 at 18:04:04, bokan wrote:
> > Is there a converse test? That scrolling after moving the mouse causes
> mousemoves?
> 
> Yes,
>
https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/fast/even....

Acknowledged.

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
File third_party/WebKit/Source/core/input/EventHandler.cpp (left):

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/core/input/EventHandler.cpp:364: if
(m_mouseEventManager->isMousePositionUnknown())
On 2016/12/02 23:00:35, amaralp wrote:
> On 2016/12/02 at 18:04:05, bokan wrote:
> > This can still get called after layout and style changes and some other
> places. I think this should still be left in. Or DCHECK that the mouse
position
> is known and make sure we can never queue this task if it's unknown.
> 
> The next if statement already does this check through
> FrameView::shouldSetCursor().

Thanks, missed that.

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
File third_party/WebKit/Source/web/DevToolsEmulator.cpp (left):

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/web/DevToolsEmulator.cpp:461:
m_webViewImpl->page()->settings().setDeviceSupportsMouse(
On 2016/12/02 23:00:36, amaralp wrote:
> On 2016/12/02 at 18:04:05, bokan wrote:
> > We should probably clear the last known mouse location here to prevent
> dispatching the fake mouse moves when emulating Android.
> 
>  I checked locally and no fake mouse moves are dispatched during emulation
even
> without the clearing.

Could you find out why? As far as I can tell, if the mouse moved at all on the
page before we enter emulation then we should be dispatching these. The only
place we clear the mouse location is from MouseEventManager::clear but I don't
see how we might be calling that from here.

This is actually important since devs often use emulation to build for mobile so
its important we don't break emulation.

[amaralp, 2016-12-08 22:29:35]

The CQ bit was checked by amaralp@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-12-08 22:30:07]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-09 00:27:22]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-09 00:27:23]

Dry run: This issue passed the CQ dry run.

[amaralp, 2016-12-09 00:42:40]

The CQ bit was checked by amaralp@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-12-09 00:43:14]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-09 02:21:04]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-09 02:21:05]

Dry run: This issue passed the CQ dry run.

[amaralp, 2016-12-12 19:35:59]

The CQ bit was checked by amaralp@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-12-12 19:36:50]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-12 22:36:05]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-12 22:36:05]

Dry run: This issue passed the CQ dry run.

[amaralp, 2016-12-13 01:09:14]

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
File third_party/WebKit/Source/web/DevToolsEmulator.cpp (left):

https://codereview.chromium.org/2536723007/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/web/DevToolsEmulator.cpp:461:
m_webViewImpl->page()->settings().setDeviceSupportsMouse(
On 2016/12/07 at 00:09:53, bokan wrote:
> On 2016/12/02 23:00:36, amaralp wrote:
> > On 2016/12/02 at 18:04:05, bokan wrote:
> > > We should probably clear the last known mouse location here to prevent
> > dispatching the fake mouse moves when emulating Android.
> > 
> >  I checked locally and no fake mouse moves are dispatched during emulation
even
> > without the clearing.
> 
> Could you find out why? As far as I can tell, if the mouse moved at all on the
page before we enter emulation then we should be dispatching these. The only
place we clear the mouse location is from MouseEventManager::clear but I don't
see how we might be calling that from here.
> 
> This is actually important since devs often use emulation to build for mobile
so its important we don't break emulation.

I'm adding a clear just in case, but from what I can tell the fake mouse event
is created but never dispatched all the way down to javascript.

[bokan, 2016-12-13 12:07:50]

thanks, lgtm

[amaralp, 2016-12-13 18:50:59]

The CQ bit was checked by amaralp@chromium.org

[amaralp, 2016-12-13 18:50:59]

The patchset sent to the CQ was uploaded after l-g-t-m from aelias@chromium.org,
avi@chromium.org
Link to the patchset: https://codereview.chromium.org/2536723007/#ps120001
(title: "rebase")

[commit-bot: I haz the power, 2016-12-13 18:51:45]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-13 19:00:51]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-13 19:00:54]

Try jobs failed on following builders:
  chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[aelias_OOO_until_Jul13, 2016-12-13 19:44:50]

The CQ bit was checked by aelias@chromium.org

[commit-bot: I haz the power, 2016-12-13 19:45:52]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-13 19:48:44]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-13 19:48:46]

Try jobs failed on following builders:
  ios-device on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)
  ios-device-xcode-clang on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device-xcode-...)
  ios-simulator on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/bui...)
  ios-simulator-xcode-clang on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator-xco...)

[amaralp, 2016-12-13 20:10:00]

The CQ bit was checked by amaralp@chromium.org

[amaralp, 2016-12-13 20:10:00]

The patchset sent to the CQ was uploaded after l-g-t-m from bokan@chromium.org,
aelias@chromium.org, avi@chromium.org
Link to the patchset: https://codereview.chromium.org/2536723007/#ps140001
(title: "rebase")

[commit-bot: I haz the power, 2016-12-13 20:10:36]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-13 20:19:46]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-13 20:19:49]

Try jobs failed on following builders:
  chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[amaralp, 2016-12-13 23:53:45]

amaralp@chromium.org changed reviewers:
+ dcheng@chromium.org

[amaralp, 2016-12-13 23:55:06]

Adding dcheng@ for SECURITY_OWNERS for
content/public/common/common_param_traits.h

[dcheng, 2016-12-14 23:09:20]

ipc lgtm

[amaralp, 2016-12-14 23:10:23]

The CQ bit was checked by amaralp@chromium.org

[commit-bot: I haz the power, 2016-12-14 23:11:22]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-14 23:14:12]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-14 23:14:13]

Try jobs failed on following builders:
  ios-device on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)
  ios-device-xcode-clang on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device-xcode-...)
  ios-simulator on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/bui...)
  ios-simulator-xcode-clang on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator-xco...)

[amaralp, 2016-12-14 23:18:02]

The CQ bit was checked by amaralp@chromium.org

[amaralp, 2016-12-14 23:18:02]

The patchset sent to the CQ was uploaded after l-g-t-m from bokan@chromium.org,
aelias@chromium.org, avi@chromium.org, dcheng@chromium.org
Link to the patchset: https://codereview.chromium.org/2536723007/#ps160001
(title: "rebase")

[commit-bot: I haz the power, 2016-12-14 23:18:52]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-15 01:07:38]

CQ is committing da patch.

Bot data: {"patchset_id": 160001, "attempt_start_ts": 1481757482444890,
"parent_rev": "908785cc7f323e882d87d29d2e6067bc9f7a90a1", "commit_rev":
"ac739f243671d657e9fb1deb3bb011ce5cb70a6d"}

[commit-bot: I haz the power, 2016-12-15 01:09:11]

Description was changed from

==========
Removed android scrolling fake mouse moves and device_supports_mouse

When a user scrolls we need to generate fake mouse moves since the cursor is
moving
relative to the page (for example you might scroll over an element that has an
mouseover event listener). Currently Android and blink have separate code-paths
for
generating these fake mouse moves. This CL removes the Android specific
code-path
and makes Android use the Blink code-path.

In order to make the Blink codepath activate on Android, delete the
deviceSupportsMouse
websetting which was exclusively used to disable this fake-mouse-move codepath.
It's sufficient to rely on mousePositionUnknown instead, which disables the
codepath if no mousemove event was ever received.

BUG=492738
==========

to

==========
Removed android scrolling fake mouse moves and device_supports_mouse

When a user scrolls we need to generate fake mouse moves since the cursor is
moving
relative to the page (for example you might scroll over an element that has an
mouseover event listener). Currently Android and blink have separate code-paths
for
generating these fake mouse moves. This CL removes the Android specific
code-path
and makes Android use the Blink code-path.

In order to make the Blink codepath activate on Android, delete the
deviceSupportsMouse
websetting which was exclusively used to disable this fake-mouse-move codepath.
It's sufficient to rely on mousePositionUnknown instead, which disables the
codepath if no mousemove event was ever received.

BUG=492738

Review-Url: https://codereview.chromium.org/2536723007
==========

[commit-bot: I haz the power, 2016-12-15 01:09:12]

Committed patchset #9 (id:160001)

[commit-bot: I haz the power, 2016-12-15 01:15:15]

Description was changed from

==========
Removed android scrolling fake mouse moves and device_supports_mouse

When a user scrolls we need to generate fake mouse moves since the cursor is
moving
relative to the page (for example you might scroll over an element that has an
mouseover event listener). Currently Android and blink have separate code-paths
for
generating these fake mouse moves. This CL removes the Android specific
code-path
and makes Android use the Blink code-path.

In order to make the Blink codepath activate on Android, delete the
deviceSupportsMouse
websetting which was exclusively used to disable this fake-mouse-move codepath.
It's sufficient to rely on mousePositionUnknown instead, which disables the
codepath if no mousemove event was ever received.

BUG=492738

Review-Url: https://codereview.chromium.org/2536723007
==========

to

==========
Removed android scrolling fake mouse moves and device_supports_mouse

When a user scrolls we need to generate fake mouse moves since the cursor is
moving
relative to the page (for example you might scroll over an element that has an
mouseover event listener). Currently Android and blink have separate code-paths
for
generating these fake mouse moves. This CL removes the Android specific
code-path
and makes Android use the Blink code-path.

In order to make the Blink codepath activate on Android, delete the
deviceSupportsMouse
websetting which was exclusively used to disable this fake-mouse-move codepath.
It's sufficient to rely on mousePositionUnknown instead, which disables the
codepath if no mousemove event was ever received.

BUG=492738

Committed: https://crrev.com/83fa786d1e7ee06d2771b7026da0041c9f68c702
Cr-Commit-Position: refs/heads/master@{#438691}
==========

[commit-bot: I haz the power, 2016-12-15 01:15:17]

Patchset 9 (id:??) landed as
https://crrev.com/83fa786d1e7ee06d2771b7026da0041c9f68c702
Cr-Commit-Position: refs/heads/master@{#438691}