Bug 154241 - WebVTT cue positions should be exposed as element attributes
Summary: WebVTT cue positions should be exposed as element attributes
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Media (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-15 05:29 PST by Ryan Govostes
Modified: 2017-01-19 03:48 PST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Govostes 2016-02-15 05:29:19 PST 
Positions of overlapping WebVTT cues are resolved in RenderVTTCue. The ultimate coordinate at which the cue is rendered is not expressed as an attribute of the <cue> element.

This would presumably make it easier to test whether cues are being rendered correctly, which would make it possible to catch issues like bug 154240 and bug 136627.
Comment 1 Eric Carlson 2016-02-15 20:16:51 PST 
Presumably this is not a WebKit-specific issue. You should file a bug against the WebVTT spec if you think this is a useful change.
Comment 2 Ryan Govostes 2016-02-18 04:38:00 PST 
Ok, I filed https://github.com/w3c/webvtt/issues/285
Comment 3 Simon Pieters 2017-01-19 03:48:13 PST 
<cue> element is not a concept the spec has, so the spec can't set attributes on it. If it's not exposed to author JS or author CSS (e.g. video::cue(cue[top]) should never match) then this would be an implementation detail.