On 3/12/15 6:37 PM, Seth Fowler wrote:
They made main resources that use multipart/x-mixed-replace trigger downloads instead of being displayed.
So what gets downloaded is the entire mixed stream, right?
The observation that multipart/x-mixed-replace support introduces a lot of complexity is absolutely true for us as well.
Does this really introduce a lot of complexity in the loader? There's the actual stream converter, and the fact that people have to worry about headers on part channels, but apart from that I don't recall much complexity.
so removing it has not resulted in a disaster for Chrome. With so few people using multipart/x-mixed-replace
We should use a use counter here, because as far as I know sites decide via server-side sniffing whether to do this. :(
-Boris _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
