On Tue, Feb 14, 2012 at 1:56 PM, John Coryat <[email protected]> wrote: > The bottom line on webview apps is they are ok for simple, single screen > type apps that don't contain a lot of moving elements. Once you start to add > animations and other fancy things, they get slow and ponderous.
Yeah, anything really complex stands a good chance of making a WebView die. And worse, onReceivedError() doesn't get called when the WebView dying occurs. onReceivedError() basically only fires for me when there's a network error. Could probably benefit from a yourJsIsMuchTooExoticAndImDyingNow() interface. I'd really like a way to flip my FrameLayout contents on anything other than success, but I don't see where to hook in. onReceivedError() is not reliable. I'd also like to be able to load more than one webview at a time. I have this one activity where I have two WebViews, I have to stagger my second request for 200ms or it will sometimes kills the first WebView request. -- Greg Donald -- 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
