It has to reload the page every time, by default, because the default action for an activity dealing with a configuration (including orientation) change is for it to be destroyed and restarted. That can be overridden, though, by specifying an android:configChange attribute for the activity in your manifest file. My uses of WebView so far don't involve any forms where keyboard input would be required, so I've been able to specify "orientation|keyboardHidden" for that attribute without having to do anything special with config change notifications. The WebView widget handles re-wrapping text and images based on view size.
On Jun 16, 1:26 pm, Glenn <glenn.andr...@googlemail.com> wrote: > Hi, > > Just started working with the webview. The issue is performance > following rotation. The WebView has to reload the page, which can be a > bit tedious. > > What's the best of of handling an orientation change without reloading > the page from source each time? > > Thanks > > Glenn --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
