It's from a separate class (runJS does something like mWebView.loadUrl(javaScriptUrl);)
In my sample code, the *run *and *runJS *are usually executed on the main UI thread (that's why there the *await *call has a (short) timeout). The WebView's JavaScript execution's callback to Java (setValue in your example) is done on a separate thread (managed by the WebView, i suppose). If you use my code, does the call to 'latch.await' time-out? If so, this means that the WebView never properly loaded the url (code) in the loadUrl call. Look at your LogCat and see what may be the problem. Note that the WebView we use returns *false *for it's WebViewClient's shouldOverrideUrlLoading method. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
