Re: Chrome removed support for multipart/x-mixed-replace documents. We should too.
On 12/03/15 16:04, Seth Fowler wrote: It looks like it doesn’t anymore, because it works fine in Chrome. It does; it browser-sniffs. Gerv ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Chrome removed support for multipart/x-mixed-replace documents. We should too.
Chrome removed support for multipart/x-mixed-replace main resources in this issue: https://code.google.com/p/chromium/issues/detail?id=249132 https://code.google.com/p/chromium/issues/detail?id=249132 Here’s their explanation: This feature is extremely rarely used by web sites and is the source of a lot of complexity and security bugs in the loader. UseCounter stats from the stable channel indicate that the feature is used for less than 0.1% of page loads. They made main resources that use multipart/x-mixed-replace trigger downloads instead of being displayed. The observation that multipart/x-mixed-replace support introduces a lot of complexity is absolutely true for us as well. It’s a huge mess. Looks like this patch landed in Chromium on June 13, 2013 and has stuck since then, so removing it has not resulted in a disaster for Chrome. With so few people using multipart/x-mixed-replace, and since now both IE and Chrome do not support it, I suggest that we remove support for it from the docloader as well. - Seth ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Chrome removed support for multipart/x-mixed-replace documents. We should too.
I've been meaning to rip out the putative support for this from XHR (and all of the complexity that it introduces) for months now. This would be great. - Kyle On Thu, Mar 12, 2015 at 3:37 PM, Seth Fowler s...@mozilla.com wrote: Chrome removed support for multipart/x-mixed-replace main resources in this issue: https://code.google.com/p/chromium/issues/detail?id=249132 https://code.google.com/p/chromium/issues/detail?id=249132 Here’s their explanation: This feature is extremely rarely used by web sites and is the source of a lot of complexity and security bugs in the loader. UseCounter stats from the stable channel indicate that the feature is used for less than 0.1% of page loads. They made main resources that use multipart/x-mixed-replace trigger downloads instead of being displayed. The observation that multipart/x-mixed-replace support introduces a lot of complexity is absolutely true for us as well. It’s a huge mess. Looks like this patch landed in Chromium on June 13, 2013 and has stuck since then, so removing it has not resulted in a disaster for Chrome. With so few people using multipart/x-mixed-replace, and since now both IE and Chrome do not support it, I suggest that we remove support for it from the docloader as well. - Seth ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Chrome removed support for multipart/x-mixed-replace documents. We should too.
On 3/12/15 7:04 PM, Seth Fowler wrote: It looks like it doesn’t anymore, because it works fine in Chrome. Iirc, bugzilla sniffs server-side and sends different things to different browsers. Worth testing in Firefox with multipart/x-mixed support disabled. -Boris ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Chrome removed support for multipart/x-mixed-replace documents. We should too.
On 2015-03-12 6:54 PM, Kyle Huey wrote: I've been meaning to rip out the putative support for this from XHR (and all of the complexity that it introduces) for months now. This would be great. Henri beat you by two years. ;-) https://bugzilla.mozilla.org/show_bug.cgi?id=843508 ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Chrome removed support for multipart/x-mixed-replace documents. We should too.
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 dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
