Does the track element really use "same-origin" as fallback?

[annevk]

Discussion in https://bugs.webkit.org/show_bug.cgi?id=205744 indicates it might be "cors" instead. This would suggest changing "create a potential-CORS request" as well as this is the only caller passing the same-origin fallback flag.

cc @whatwg/media

[annevk]

It seems we have some tests for this at https://wpt.fyi/results/html/semantics/embedded-content/media-elements/track/track-element/cors, but unfortunately they are not written in a way that makes them easy to understand.

@zcorpan how much work would it be to refactor these to be JSON + JS wrapper rather than using the <title> element as input?

[zcorpan]

@annevk I think it shouldn't be too much work, maybe a few days.

I wonder if it would make sense to have a reusable testing story for all things with CORS, like in web-platform-tests/wpt#25247

[annevk]

@youennf is taking another pass at aligning Safari with the specification: https://bugs.webkit.org/show_bug.cgi?id=239381.