Hey Mark.

> Mariano Kamp wrote:
> > OMG. That is such a blow. I didn't read anything like that in the
> > WebView documentation.
>
> I didn't say "WebView". I said "Browser". Browser != WebView.
>
Sorry, I know, I didn't want to imply otherwise.

> Any idea how to work around that?
>
> Writing a ContentProvider to serve your content appears to be the
> standard answer. I haven't used that technique myself as yet, though.
>
> I don't see how that should work?
Wouldn't that be the same as the FileContentProvider? How would WebView
learn about this provider.

Anyway, thanks for taking the time to think answer my question.

Cheers,
Mariano

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to