Using manifest in standalone HTML5 in IFrame

I am working with html 5 application cache using firefox 3.6. My web application uses iframes to load another web application that conveys a request for the same origin. Unfortunately, the standalone application cache for the loaded iframe page does not work. In particular:

  • For the URL received through the iframe, I observe the application manifest and all resources listed inside it are downloaded from my web server.
  • When I load the iframe URL directly by typing it in my URL string, the application cache works.
  • When the page with the application cache is loaded through the iframe, the application cache does not work.
  • The only difference between the container url and the iframe src url is the web application context (for example, the container "https://www.example.com/cat", while the iframe source url is "https: // www. example.com/dog ').

I found some chatter in whatwg work group thread , discussing if the iframe should inherit the container manifest settings, which makes me think that this should work.

Am I doing something impracticable? Is firefox behind whatwg spec? Any ideas or pointers to a solution would be appreciated.

+3
source share
1 answer

I understood the problem and filed an error using firefox:

https://bugzilla.mozilla.org/show_bug.cgi?id=623996

+4
source

Source: https://habr.com/ru/post/1783947/


All Articles