Re: Chrome removed support for multipart/x-mixed-replace documents. We should too.

2015-03-13 Thread Gervase Markham
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

Re: Chrome removed support for multipart/x-mixed-replace documents. We should too.

2015-03-13 Thread Kyle Huey
On Thu, Mar 12, 2015 at 4:43 PM, Ehsan Akhgari wrote: > 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.

Re: Chrome removed support for multipart/x-mixed-replace documents. We should too.

2015-03-12 Thread Seth Fowler
On Mar 12, 2015, at 4:42 PM, Boris Zbarsky wrote: > > 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? You know, that’s what the

Re: Chrome removed support for multipart/x-mixed-replace documents. We should too.

2015-03-12 Thread Boris Zbarsky
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 i

Re: Chrome removed support for multipart/x-mixed-replace documents. We should too.

2015-03-12 Thread Ehsan Akhgari
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 __

Re: Chrome removed support for multipart/x-mixed-replace documents. We should too.

2015-03-12 Thread Boris Zbarsky
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 __

Re: Chrome removed support for multipart/x-mixed-replace documents. We should too.

2015-03-12 Thread Seth Fowler
On Mar 12, 2015, at 3:52 PM, Ehsan Akhgari wrote: >> 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

Re: Chrome removed support for multipart/x-mixed-replace documents. We should too.

2015-03-12 Thread Kyle Huey
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 wrote: > Chrome removed support for multipart/x-mixed-replace main resources in > this iss

Re: Chrome removed support for multipart/x-mixed-replace documents. We should too.

2015-03-12 Thread Ehsan Akhgari
On 2015-03-12 6:37 PM, Seth Fowler wrote: Chrome removed support for multipart/x-mixed-replace main resources in this issue: https://code.google.com/p/chromium/issues/detail?id=249132 Here’s their explanation: This feature is extr

Chrome removed support for multipart/x-mixed-replace documents. We should too.

2015-03-12 Thread Seth Fowler
Chrome removed support for multipart/x-mixed-replace main resources in this issue: 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 s