<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class="">I would like to suggest we remove support for 'multipart/x-mixed-replace’ main resources while keeping support for multipart images.</div><div class=""><br class=""></div><div class="">Based on Chrome usage data, this feature is extremely rarely used by Web sites (<span style="white-space: pre-wrap;" class="">less than 0.00001% of page loads</span>) [1]. This feature adds complexity to the loader and is a source of (security) bugs (e.g. [2] recently), current support also seems buggy.</div><div class=""><br class=""></div><div class="">Current support in Safari / WebKit:</div><div class="">- Support is not great is WebKit. If you load a Motion JPEG main resource for example, it will keep creating a new ImageDocument and all its DOM tree for every frame (tested on Safari / Mac).</div><div class="">- It looks like support is broken on Safari on iOS (I tried a Motion JPEG main resource on iOS8, I see the first frame then a blank page that never finishes loading).</div><div class=""><br class=""></div><div class="">Other browsers:</div><div class="">- Never supported by IE (including IE11) for any resource</div><div class="">- Chrome already dropped support for this (main resources only) almost 2 years ago [3].</div><div class="">- Firefox 37 still supports this based on local testing.</div><div class=""><br class=""></div><div class="">Again, I am only proposing dropping support for main resources. For e.g., having an <IMG> element in a page whose src attribute points to a Motion JPEG would still work as intended.</div><div class=""><br class=""></div><div class="">[1] <a href="https://code.google.com/p/chromium/issues/detail?id=249132" class="">https://code.google.com/p/chromium/issues/detail?id=249132</a></div><div class="">[2] <a href="https://bugs.webkit.org/show_bug.cgi?id=143979" class="">https://bugs.webkit.org/show_bug.cgi?id=143979</a></div><div class="">[3] <a href="http://src.chromium.org/viewvc/blink?view=revision&revision=152363" class="">http://src.chromium.org/viewvc/blink?view=revision&revision=152363</a></div><div class=""><br class=""></div><div class="">Kr,</div><div class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">--</div><div class=""><span style="font-size: 13px;" class=""> </span>Chris Dumez - Apple Inc. - Cupertino, CA</div><div class=""><br class=""></div></div></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br class=""></div></body></html>