- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Wed, 2 Oct 2013 13:26:36 +1000
- To: "Jerry Smith (WINDOWS)" <jdsmith@microsoft.com>
- Cc: Glenn Adams <glenn@skynav.com>, public-html <public-html@w3.org>
Hi Jerry, On Wed, Oct 2, 2013 at 2:55 AM, Jerry Smith (WINDOWS) <jdsmith@microsoft.com> wrote: > Can you comment specifically on the rationale for moving the text attribute and getCueAsHTML off the abstract TextTrackCue object? These at least serve a common need and are not format specific. What is the reason for moving them? There is a lengthy history of discussion behind this going back maybe 1-2 years. I don't want to rehash the arguments since we have now come to a majority supported position. For your advantage, here are some key reasons: * the .text attribute contains content marked up in a specific format that is interpreted according to rendering rules for that specific format. For WebVTT, the cue content is provided in .text and rendered according to WebVTT rendering rules. For other formats, .text contains different markup and is thus rendered according to different rendering rules. Therefore, this is format-specific and has no business sitting on an abstract base interface. * the .getCueAsHTML() function converts the content provided in the .text attribute to HTML format according to the rules of that format. Thus, again, this is format-specific and has no business sitting on an abstract base interface. * providing either of them as empty placeholders also makes no sense because some formats don't have text content, nor are they renderable as HTML by the browser, which has just been shown by the DataCue interface. HTH. Regards, Silvia.
Received on Wednesday, 2 October 2013 03:27:23 UTC