[email protected] wrote:
You need this for all protocols, not just HTTP, so you can't leverage
the application cache stuff, right?
I'm not so sure. Why would I need anything else but HTTP/HTTPS?
You don't plan to support loading mhtml via file:// ?
Or if the idea is to use MHTML for "save as" (which I think is a
wonderful idea), you don't plan to support saving ftp:// pages? Or
pages from various extension protocols?
Basically, there's nothing special about http in this regard, so we
shouldn't be special-casing it.
What javascript actually breaks, and why, if you go the URI-rewriting route?
Any Javascript that rewrites some URIs itself.
OK, granted. Is this common?
This would end up fetching some resources from the network instead of from the
archive.
Then again, I assume MHTML won't work well with very dynamic content
or AJAX anyway.
Yes.
It might be that the URI-rewriting route is the only feasible
solution, even if I'm not very fond of it.
Well, it's the simplest one without somewhat widespread changes, I
think.... That doesn't make it the only feasible one, nor necessarily
the most desirable. Maybe the right thing to do is to make those
widespread changes.
-Boris
_______________________________________________
dev-tech-network mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-network
