Issue metadata
Sign in to add a comment
|
Support data: URLs in <track src>
Reported by
sim...@opera.com,
Aug 25 2017
|
||||||||||||||||||||||
Issue descriptionI could not find an open issue about exactly this. According to https://github.com/w3c/web-platform-tests/issues/4940#issuecomment-281391772 data: URL in <track src> should work, but results in an error event in Chromium. It works in Gecko and WebKit. Test: https://github.com/w3c/web-platform-tests/pull/7008
,
Aug 25 2017
Correction: it only works in WebKit when <video> doesn't have a crossorigin attribute. https://bugs.webkit.org/show_bug.cgi?id=175981
,
Aug 25 2017
https://html.spec.whatwg.org/#sourcing-out-of-band-text-tracks specifies how loading of <track> should work. https://html.spec.whatwg.org/#start-the-track-processing-model step 10.1 creates a request, 10.3 invokes fetch. https://fetch.spec.whatwg.org/#concept-main-fetch step 12 checks for "data" and is handled the same as same-origin.
,
Aug 25 2017
Right, it was the fetch step 12 I was thinking about (and that the <track> spec doesn't really override that in any way.)
,
Nov 15 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by f...@opera.com
, Aug 25 2017