Click and touch events do not fire after using scroll CSS
Will Quast
iOS 5.
After using "-webkit-overflow-scrolling: touch", then clear out and
replace the html, there is a "dead zone" at the top of the screen.
I have created a single file demo of this bug. I would be great if
someone that knows about the internals of webview could take a look at
it and see what is wrong, or at least tell me im not crazy.
The index file is located at http://pastebin.com/JwL412fy
Just start a new PhoneGap 1.2 project and drop this in as the
index.html file.
David Lewis
I'm working on a PhoneGap project and finding a similar problem to
you, dead zones on the page after using CSS for scrolling.
To help solve my problem, I've been working with your code as it's a
neat way to trigger the issue. One thing I've found is that removing
all the calls to console.log seems to improve the reliability of the
touch events.
In my test I found that any call to console.log that is triggered from
the callback associated with deviceready will make the touch events
unreliable (this includes functions that are called from within this
callback).
This seems completely insane, so I'd love to know if you have success
in doing this.
Fingers crossed,
David
On Nov 24, 10:59 am, Will Quast <w...@bohemian.cc> wrote:
> I think I have run into a bug in the new CSS scrolling introduced in
> iOS 5.
> After using "-webkit-overflow-scrolling: touch", then clear out and
> replace the html, there is a "dead zone" at the top of the screen.
> I have created a single file demo of this bug. I would be great if
> someone that knows about the internals of webview could take a look at
> it and see what is wrong, or at least tell me im not crazy.
>
> The index file is located athttp://pastebin.com/JwL412fy
Alex Grande
that it is call native apis through phonegap. I have found that every
time I make a call to phonegap, use -webkit-overflow-scrolling, and
use css3 animations, the problem occurs.
On Nov 30 2011, 1:53 pm, David Lewis <m...@david-lewis.com> wrote:
> Hi Will,
>
> I'm working on a PhoneGap project and finding a similar problem to
> you, dead zones on the page after using CSS forscrolling.
>
> To help solve my problem, I've been working with your code as it's a
> neat way to trigger the issue. One thing I've found is that removing
> all the calls to console.log seems to improve the reliability of the
> touch events.
>
> In my test I found that any call to console.log that is triggered from
> the callback associated with deviceready will make the touch events
> unreliable (this includes functions that are called from within this
> callback).
>
> This seems completely insane, so I'd love to know if you have success
> in doing this.
>
> Fingers crossed,
> David
>
> On Nov 24, 10:59 am, Will Quast <w...@bohemian.cc> wrote:
>
>
>
>
>
>
>
relluf
> I believe the reason for console.log contributing to the problem is
> that it is call native apis through phonegap. I have found that every
> time I make a call to phonegap, use -webkit-overflow-scrolling, and
> use css3 animations, the problem occurs.
use of CSS transitions causes dead zones, I am pretty sure they don't.
The use of -webkit-overflow-scrolling *and* the use of PhoneGap.exec
(callback to native code) seems to be enough to cause dead zones.
This issue (or at least its manifestation in my project) has been
driving me mad for the last 2 weeks. I am glad that I have finally
found some "partners in crime". :-)
Ralph
Kerri Shotts
Generesque
Ralph Kazemier
PhoneGap frame" as suggested by TimW:
http://groups.google.com/group/phonegap/msg/7beee231774af8c9
I can report that my app is working just fine now. Plugins/callbacks
to native code are working correctly. I am not quite sure (yet) what
the side effects of "disabling the internal PhoneGap frame" might be,
just wanted to post here ASAP.
Ralph
> --
> You received this message because you are subscribed to the Google
> Groups "phonegap" group.
> To post to this group, send email to phon...@googlegroups.com
> To unsubscribe from this group, send email to
> phonegap+u...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/phonegap?hl=en?hl=en
>
> For more info on PhoneGap or to download the code go to www.phonegap.com
kate
Thanks in advance!
On Sunday, April 1, 2012 4:27:50 AM UTC-7, relluf wrote:
I am now using version 1.5.0 (Cordova) and "disabled the internal
PhoneGap frame" as suggested by TimW:
http://groups.google.com/group/phonegap/msg/7beee231774af8c9I can report that my app is working just fine now. Plugins/callbacks
to native code are working correctly. I am not quite sure (yet) what
the side effects of "disabling the internal PhoneGap frame" might be,
just wanted to post here ASAP.Ralph
On Wed, Feb 8, 2012 at 5:35 AM, Kerri Shotts <kerri...@gmail.com> wrote:
> Doesn't solve the real issue, but you might go for iScroll instead if you
> have to get something out. Of course, it has its own share of problems, but
> doesn't have this particular issue.
>
> I tried the overflow-scrolling in my app as well and found that it didn't
> work as needed. Too many things went entirely wonky. Switched back to
> iScroll.
>
> --
> You received this message because you are subscribed to the Google
> Groups "phonegap" group.
> To post to this group, send email to phon...@googlegroups.com
> To unsubscribe from this group, send email to
Amir
I have file a bug request here. Please vote to get someone at PhoneGap
look into this issue.
https://issues.apache.org/jira/browse/CB-593
Thanks!
