[Bug 23113] Deal with mode for TextTrackCues that are not VTTCues

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23113

--- Comment #9 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> ---
(In reply to Philip Jägenstedt from comment #8)
> 
> You're right, I didn't consider the implications of the interface changing.
> That makes it possible for a script to be pedantic and check the interface
> before handling a cue. A less pedantic script would still either end up with
> double rendering (if both interfaces have a .text property) or rendering
> "undefined" or similar (if they don't share the property name).

We should encourage JS devs to check the interface that in-band text track cues
return. Maybe we can add and example - that usually has good influence on best
practice.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 16 September 2013 11:35:48 UTC