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

ASF subversion and git services commented on CB-13124:
------------------------------------------------------

Commit b204d2747d6b3af1973d6509dfaa78f6d2a7009b in cordova-plugin-statusbar's 
branch refs/heads/master from Lu Wang
[ https://gitbox.apache.org/repos/asf?p=cordova-plugin-statusbar.git;h=b204d27 ]

Add preference for native scroll to top

- As described in https://issues.apache.org/jira/browse/CB-13124


> statusTap event is not triggered until momentum scrolling is complete
> ---------------------------------------------------------------------
>
>                 Key: CB-13124
>                 URL: https://issues.apache.org/jira/browse/CB-13124
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: cordova-plugin-statusbar
>    Affects Versions: cordova@7.0.0
>            Reporter: Lu Wang 
>            Priority: Minor
>
> The statusTap event isn't triggered until the momentum scrolling is complete. 
> To reproduce:
> 1. Create an app that has a natural scrolling body (*not* 100% height div 
> with overflow-x set to "auto" and -webkit-overflow-scrolling set to "touch"). 
> This means a standard WebView with body contents larger than one screen.
> 2. Flick the screen to scroll and notice that momentum/inertial scroll 
> triggers.
> 3. During momentum scrolling, tap the status bar
> 4. Note the statusTap event fired only after the scrolling has completely 
> stopped.
> There isn't a great way to fix this since the events are triggered in 
> cordova.js with a setTimeout. I have a PR available to fix this by adding a 
> config option to StatusBar that enables the native scroll-to-top behavior.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

Reply via email to