[jira] [Commented] (RIPPLE-15) Touch Events emulation: emulated 'touchend' event has touch in 'touches' field

["Alexander Ziborov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/RIPPLE-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13950522#comment-13950522 ] 

Alexander Ziborov commented on RIPPLE-15:
-----------------------------------------

When will a new version of chrome extension be released with this fix?
https://chrome.google.com/webstore/detail/ripple-emulator-beta/geelfhphabnejjhdalkjhgipohgpdnoc

> Touch Events emulation: emulated 'touchend' event has touch in 'touches' field
> ------------------------------------------------------------------------------
>
>                 Key: RIPPLE-15
>                 URL: https://issues.apache.org/jira/browse/RIPPLE-15
>             Project: Apache Ripple
>          Issue Type: Bug
>         Environment: Window 8 64bit;
> Chrome 26.0.1410.64 m;
> Ripple Emulator (Beta) 0.9.15
>            Reporter: Alexander Ziborov
>            Assignee: Dan Silivestru
>              Labels: events, javascript, simulation
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The 'touchend' event emulated by 'mouseup' should contain empty 'touches' and 'targetTouches' lists, but actually it has one touch.
> For example, Chrome mode "Emulate touch events" works as expected - 'touchend' event have no any touch in 'touches' and 'targetTouches'. Mobile devices so work also.
> Potential issue is in this part of the code, as I think: incubator-ripple-HEAD-24cae31\lib\client\touchEventEmulator.js
> function _simulateTouchEvent(type, mouseevent) {
>     ...
>         changedTouches: [touchObj],
>         targetTouches: [touchObj],
>         touches: [touchObj]
>     ...
> }
> As one of the potential solutions, I suggest to check for 'touchend' event type, something like this:
>   ...
>     targetTouches: type === "touchend" ? [] : [touchObj],
>     touches: type === "touchend" ? [] : [touchObj]
>   ....



--
This message was sent by Atlassian JIRA
(v6.2#6252)