-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose user preferences for text tracks to JS #292
Comments
While there is a user preference in Blink with the values "default", "captions" and "subtitles", there's also a heuristic that takes the language into account, which calculates a score for each track. |
Another thought. If one could register a callback that is handed a |
I don't follow. Elaborate? |
OK, so this would be a rather big undertaking. As it is, the |
Ooh, OK. Yeah that seems like a big project but little benefit. It seems it's fine to overlay the video, we just need to address the user-preference thing. |
I would say that the ability to implement WebVTT entirely using such extension points and thus also allowing any other format to be implemented with scripts on equal footing is a rather big benefit, but yes, it's still a big project. I'm rather reluctant to have |
WFM. Should |
Something about that seems unusual, but I don't see why it would be a problem, and it is the perfect attribute name for this. 👍 |
See http://www.w3.org/2015/10/28-htmlcue-minutes.html
When using a metadata track and render the payload with JS for things that are actually subtitles or captions (just with a different cue text format), we should expose the user preferences to JS so it can enable the right metadata track.
This information is already available because the JS gets to know which subtitle or caption track gets enabled, which depends on user preference.
An alternative idea (we could do both) is to let user preference signal somehow metadata tracks as if they were subtitle or caption tracks, with a separate attribute.
steps 1-3 in https://html.spec.whatwg.org/multipage/embedded-content.html#honor-user-preferences-for-automatic-text-track-selection would also apply to metadata tracks with the appropriate actualkind and
set a flag on the track that the user wants it showing (e.g. set text track mode to "showing" which I think is equivalent to "hidden" for metadata tracks).[I misremembered how metadata tracks get enabled. I thought they were all set tohidden
, but it's just the ones that have adefault
attribute that get set tohidden
. So then it would make more sense to have the metadata tracks withactualkind
be set tohidden
per user-pref for theactualkind
, and the rest are left disabled.]The text was updated successfully, but these errors were encountered: