- From: Alice Wonder <alice@domblogger.net>
- Date: Sun, 12 Nov 2017 08:42:55 -0800
- To: public-texttracks@w3.org
On 11/12/2017 08:27 AM, Fredrik Söderquist wrote:
*snip*
>
>
> This is what should happen already per the "cue text parsing rules" [1].
> ("<a ...>" will be tokenized as a start tag 'a' with the annotation
> 'href="https://www.example.com"', and "</a>" as an end tag 'a'. Both
> tokens will then be ignored by the parsing steps in [1].)
> This can be verified quite easily by checking what VTTCue.getCueAsHTML()
> returns. (If implementation don't show the text at all it would seem
> they have a bug.)
>
https://w3c.github.io/webvtt/#types-of-webvtt-cue-payload
does not indicate <a> is valid in a cue, an no online WebVTT validator I
have used will validate a WebVTT file with an <a> in any of the cues.
Also, is VTTCue an API that is valid outside the scope of a browser page?
Received on Sunday, 12 November 2017 16:43:21 UTC