[
https://issues.apache.org/jira/browse/CB-11560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philippe Wang reopened CB-11560:
--------------------------------
The proposed solution doesn't work, unfortunately it's only a poor workaround.
> Default behaviour for tap on status bar not accessible anymore
> --------------------------------------------------------------
>
> Key: CB-11560
> URL: https://issues.apache.org/jira/browse/CB-11560
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Statusbar
> Environment: iOS
> Reporter: Philippe Wang
> Assignee: Jesse MacFadyen
>
> Adding a JS event on status bar tap
> (https://issues.apache.org/jira/browse/CB-6626) is nice. But then the default
> behaviour is no longer available. So, in order to have the default behaviour
> back, I forked the plugin and reverted the patch
> (https://github.com/apache/cordova-plugin-statusbar/pull/4). I think it's a
> bad approach but for now I don't know what else I can do.
> I think there should be a configuration option to deactivate this. Or at
> least some documentation that explains how to have the default behaviour back.
> I do realise that the default behaviour is not perfect. Notably, it can only
> scroll the body of the page. For instance, if the page is a scrollable div
> (instead of a scrollable body), the default behaviour just doesn't work
> because the body will just eat the scroll directive without doing anything.
> So the JS event becomes a lot more relevant. However I have not managed to
> obtain the smooth default "tap on status bar" scroll up with a JS event
> listener.
> The scrollable div makes sense because of the sluggish scroll of body (even
> with `-webkit-overflow-scrolling: touch` it's still weirdly slow).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
