27989 2015-02-10 04:29:24 +0000 Should audio and video tracks be exposed cross-origin? 2019-03-29 21:37:45 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other All RESOLVED MOVED https://html.spec.whatwg.org/#loading-the-media-resource P3 normal Unsorted 1 contributor ian annevk d ian mike philipj contributor oldest_to_newest 117777 0 contributor 2015-02-10 04:29:24 +0000 Specification: https://html.spec.whatwg.org/ Multipage: https://html.spec.whatwg.org/multipage/#loading-the-media-resource Complete: https://html.spec.whatwg.org/#loading-the-media-resource Referrer: Comment: Should audio and video tracks be exposed cross-origin? Posted from: 14.162.108.112 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.94 Safari/537.36 OPR/27.0.1689.66 117778 1 philipj 2015-02-10 04:30:55 +0000 In-band text tracks are not exposed cross-origin, with this spec note: "Cross-origin videos do not expose their subtitles, since that would allow attacks such as hostile sites reading subtitles from confidential videos on a user's intranet" The same is not true for in-band audio and video tracks. Is this an oversight or per design? The *Track objects expose a bunch of metadata... 118297 2 ian 2015-03-04 19:34:52 +0000 Yeah I guess the id/kind/label/language metadata should be blocked. 129703 3 d 2019-03-29 21:37:45 +0000 https://github.com/whatwg/html/issues/1735