I have the same behavior too, however, this is because i'm using a
ViewFlipper, which has two webviews, one on the front and one on the
background. The onPageFinished is called once for each of them. I don't
expect this behaviour too, but still can't find any good solution.
--
You received thi
I've done more research, and I think I understand everything that's going
on.
Here is my WebViewClient:
public class MyWebViewClient extends WebViewClient {
@Override
public void onPageStarted(WebView view, String url, Bitmap favicon) {
System.out.println("onPageStarted: " + url);
I just want to load a url into the WebView and be notified when it finishes
loading. If I don't implement shouldOverride and call WebView#load, my
redirect isn't getting followed. If I do implement shouldOverride this way,
my onPageFinished gets called twice gets
-Heath
On Feb 19, 2011 1:38 PM,
A and B are supposed to be URLs. I'm just trying to simplify the
conversation.
-Heath
On Feb 19, 2011 1:31 PM, "Mark Murphy" wrote:
On Sat, Feb 19, 2011 at 2:14 PM, Heath Borders
wrote:
> Here is what occur...
I have no idea what A and B are.
> If I don't implement shouldOverrideUrlLoading,
Doh, my bad that's what I get from using my memory. But yeah, if
you're handling your own loadUrl logic return 'true' not false.
So, to clarify if you're correctly return true and using your own
loadURL call then shoulOverride is !probably being caused by your ajax
calls. Again this is from memor
On Sat, Feb 19, 2011 at 2:43 PM, Mark Murphy wrote:
> On Sat, Feb 19, 2011 at 2:37 PM, Miguel Morales
> wrote:
>> If you're handling your own
>> loadURL in shouldOverride() you need to set return false so that the
>> webview doesn't attempt to load the page twice.
>
> No.
>
> "Returns: True if t
On Sat, Feb 19, 2011 at 2:37 PM, Miguel Morales wrote:
> If you're handling your own
> loadURL in shouldOverride() you need to set return false so that the
> webview doesn't attempt to load the page twice.
No.
"Returns: True if the host application wants to handle the key event
itself, otherwise
If I recall correctly, ajax requests can indeed call the webview client.
I'm not sure I understand what you're trying to implement, but the
onLoadResource() callback a bit useful. If you're handling your own
loadURL in shouldOverride() you need to set return false so that the
webview doesn't attem
On Sat, Feb 19, 2011 at 2:14 PM, Heath Borders wrote:
> Here is what occurs: (==>denotes a call I make, --> denotes a callback)
>
> ==>webView.loadUrl(A);
> -->webViewClient.shouldOverrideUrlLoading(B) {
> ==> webView.loadUrl(B);
> return true;
> }
> -->webViewClient.onPageFinished(B);
> -->web
Here is what occurs: (==>denotes a call I make, --> denotes a callback)
==>webView.loadUrl(A);
-->webViewClient.shouldOverrideUrlLoading(B) {
==> webView.loadUrl(B);
return true;
}
-->webViewClient.onPageFinished(B);
-->webViewClient.onPageFinished(B);
Notice that onPageFinished gets called t
On Sat, Feb 19, 2011 at 2:59 AM, Heath Borders wrote:
> When I call WebView#loadUrl I expect that I should only get a single
> WebViewClient#onPageFinished call and no
> WebViewClient#shouldOverrideUrlLoading call. However, I get
> a WebViewClient#shouldOverrideUrlLoading (which I implement by al
When I call WebView#loadUrl I expect that I should only get a single
WebViewClient#onPageFinished call and no WebViewClient#shouldOverrideUrlLoading
call. However, I get a WebViewClient#shouldOverrideUrlLoading (which I
implement by always calling WebView#loadUrl and returning true) and then
t
12 matches
Mail list logo
