You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The explainer currently allows only a subset of HTML elements to be used in cue fragments. Is this a good idea? In general, I'm pretty skeptical of features which subset other parts of the platform.
The text was updated successfully, but these errors were encountered:
hober
added
the
text tracks
TextTrackCue enhancements for programmatic subtitle and caption presentation
label
Jan 16, 2020
VTT defines a subset, this allows more than WebVTT. I thought a "generic" cue API would likely need a bigger subset, so I chose the list of nodes required by imsc.js. We talked about modifying it, e.g. dropping , and proposing whatever we end with as the WebVTT subset.
The explainer currently allows only a subset of HTML elements to be used in cue fragments. Is this a good idea? In general, I'm pretty skeptical of features which subset other parts of the platform.
The text was updated successfully, but these errors were encountered: