Open
Bug 1395924
Opened 7 years ago
Updated 1 month ago
Support all of HTML's character entities in WebVTT
Categories
(Core :: Audio/Video: Playback, enhancement, P3)
Core
Audio/Video: Playback
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox57 | --- | affected |
People
(Reporter: zcorpan, Unassigned)
Details
(Keywords: parity-chrome, parity-safari)
Spec: https://w3c.github.io/webvtt/#consume-an-html-character-reference (Changed in https://github.com/w3c/webvtt/pull/253) Test: http://w3c-test.org/webvtt/parsing/cue-text-parsing/tests/entities.html
Updated•7 years ago
|
Priority: -- → P3
Comment 1•6 years ago
|
||
Can we re-review the priority on this and other WebVTT bugs, please? According to stats by encoding.com, 30% of all caption content that they transcode is in/for WebVTT (30% for SCC, 30% for CEA608, 1% for DFXP). WebVTT is the dominant Web caption and subtitle format now. WebVTT is now in CR and Web platform tests are failing in FF in many ways - see https://wpt.fyi/results/webvtt/parsing/cue-text-parsing/tests/entities.html?label=stable&aligned=true just for the HTML character entities. Source: https://github.com/web-platform-tests/wpt/blob/master/webvtt/parsing/cue-text-parsing/tests/entities.html
Comment 2•6 years ago
|
||
report is at https://www.encoding.com/resources/
Updated•2 years ago
|
Severity: normal → S3
Comment 3•5 months ago
|
||
It looks like WebKit just fixed, so Firefox will likely soon be the only one failing the WPT.
Updated•1 month ago
|
Keywords: parity-chrome,
parity-safari
You need to log in
before you can comment on or make changes to this bug.
Description
•