views:

66

answers:

3

For some reason the onPageFinished is firing before the WebView has finished loading - I can't figure out why...

public class WebViewClientTest extends Activity {
/** Called when the activity is first created. */
@Override
public void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.main);
    final WebView webview = (WebView) findViewById(R.id.webview);

    webview.setWebViewClient(new WebViewClient() {  
        @Override  
        public void onPageFinished(WebView view, String url) {
            super.onPageFinished(webview, url);
            webview.scrollTo(0, 500);
        }  
    });
    webview.loadUrl("http://www.google.co.uk/search?sourceid=chrome&ie=UTF-8&q=lala");

}
}
A: 

Hmm, well if I make my own private class, it works...

private class ViewStoryWebViewClient extends WebViewClient { 
    @Override  
    public void onPageFinished(WebView view, String url) {
        super.onPageFinished(webView, url);
        webView.scrollTo(0, 50);
    }  
} 
DaBeeeenster
A: 

OK, well it looks like this isn't fixed. I think there's a race condition going on when loading the page, but can't get a reproducible behaviour.

I'm storing the HTML content of a webpage in a SQLite database for viewing when offline. I reload the content into the WebView with:

webView.loadDataWithBaseURL("fake://fake.com/", htmlBody, "text/html", "utf-8", null);

It seems that sometimes when the WebView loads it fires the WebViewClient.onPageFinished() method correctly, and other times it does not. Sometimes it appears to fire before the page has finished loading, producing a contentHeight of 0 and ignoring any scrollTo calls.

Anyone have any experience with this?

DaBeeeenster
A: 

I'm getting the exact same thing with loadDataWithBaseURL(). Sometimes the contents don't show up and the contentHeight is 0. The odd thing is that clicking anywhere in the web view will cause the contents to show. Also, if you call zoomIn();zoomOut(); in the onPageFinished() method, the page will appear.

EDIT: The problem with my code is that the HTML content had a dummy window.location= assignment in the onload event, and this was causing the original content not to load at random times. Sorry, I don't think this is related to what you are seeing.

Bryan