incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Grieve (JIRA)" <>
Subject [jira] [Commented] (CB-593) Click and touch events do not fire after using scroll CSS
Date Wed, 08 Aug 2012 00:51:10 GMT


Andrew Grieve commented on CB-593:

I did some experimentation today to see if using a registered URIProtocol to send messages
to the native side. It functions about twice as slow, but seems like it would be a good work-around
to this problem. What I'm thinking here is that we have a few options:

a) Always use a URIProtocol for communication and live with the slower bridge
b) Use an iframe for the first message, then use a URIProtocol for all messages for the next
500 milliseconds, then switch back to iframe.
c) Allow apps to choose between the two techniques at run-time/compile-time.

I think a) is probably the most preferable option, since although the bridge will be slower,
it is still probably fast enough. Opinions?

Demo branch at:
> Click and touch events do not fire after using scroll CSS
> ---------------------------------------------------------
>                 Key: CB-593
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CordovaJS, iOS
>    Affects Versions: 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.1
>         Environment: iOS 5 / 5.1 Device
>            Reporter: Amirudin Bin Mohamed Ghani
>            Assignee: Shazron Abdullah
>            Priority: Minor
>              Labels: -webkit-overflow-scrolling:touch, css
> Dear Shazron, devs
> After using "-webkit-overflow-scrolling: touch", then regenerate the html via DOM, there
is a "dead zone" at the top of the screen. Only happen on a device.
> Step to reproduce:
> 1. Download index.html at
> 2. Create app, install on a device.
> 3. Follow on-screen instruction.
> Refer original thread & complaint here:
> Please advice / assist.
> Thanks.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message