(In reply to Anne (:annevk) from comment #7) > 1. Jake's fundamental fix is essentially not allowing mixing of non-opaque and opaque responses in media elements. That alone is not going to resolve the issue here as the length is already exposed to the ServiceWorker when the media element makes the additional range request (which later happens to respond with 416), so I've split this off into bug 1762068. > Arguably one problem here is that the cross-origin request is still made. It seems like it should be possible to network error earlier when we detect a cross-origin request after we've started using same-origin responses. Filed bug 1762078 for that, addressing which would require going off spec. This and bug 1762068 can be addressed without requiring any spec change that has not yet been agreed.
Bug 1735923 Comment 12 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Anne (:annevk) from comment #7) > 1. Jake's fundamental fix is essentially not allowing mixing of non-opaque and opaque responses in media elements. ~~That alone is not going to resolve the issue here as the length is already exposed to the ServiceWorker when the media element makes the additional range request~~ (which later happens to respond with 416), so I've split this off into bug 1762068. > Arguably one problem here is that the cross-origin request is still made. It seems like it should be possible to network error earlier when we detect a cross-origin request after we've started using same-origin responses. Filed bug 1762078 for that, addressing which would require going off spec. This and bug 1762068 can be addressed without requiring any spec change that has not yet been agreed.