All page content is loaded with HTTP. Strangely, this static content does load successfully if it is sourced in the iframe document, but not if it is sourced in the literal HTML. Even if there was a protocol difference, I can't understand why that would make a difference in the internal AppCache-fetching logic.
On Tuesday, July 10, 2012 3:22:47 PM UTC-7, Mark Murphy (a Commons Guy) wrote: > > On Tue, Jul 10, 2012 at 1:19 PM, Andy Erickson wrote: > > However, specifying this base URL allows the iframed HTML to load from > the > > AppCache, so it looks like some domain information is being extracted > from > > the URL. Is there any reason why the iframe element should load from > the > > AppCache while the other elements do not? > > Because the <iframe> was downloaded over HTTP(S), and the other > elements were not. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://github.com/commonsguy > http://commonsware.com/blog | http://twitter.com/commonsguy > > Android Training in NYC: http://marakana.com/training/android/ > -- 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
