In my JavaScript code I set 'onclick' handlers on HTML DOM elements.
In Froyo these handlers always 'fire' when their elements are clicked
w/i WebView, as expected.
In pre-Froyo, including 2.1 I am confronted by 'magic' :-(
Sometimes the handlers are activated and they successfully log to
console.info as well as call Java callbacks,
sometimes NOT. For instance, on 1st entry to an Activity that displays
an HTML+JS document,
the doc's elements react to clicks, then after playing with the app
some more and returning to the Activity
the handlers no longer respond. Obviously, the WebView/WebKit/etc.
combo is in a different state
then originally, but WHAT is going on? What stops the handlers from
running in the new state?

These phenomena are, luckily, absent in Froyo so something got fixed
but Froyo is not yet out there enough.

Has anybody experienced this nasty WebView/JS behavior with unstable
'onclick' functionality?

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to