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.00001% > 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
