On Fri, Apr 23, 2010 at 8:52 PM, Sean Hayes <Sean.Hayes@microsoft.com>wrote: > Given that the page author will have access to the video timeline, they > will of course be able to superimpose anything they like; and turning on and > off the caption stream is fine. What I want to avoid is inadvertent leakage, > especially when they come from different source to the HTML. > OK, then I have no idea what you meant by "there will need to be a strong barrier between the HTML and the timed text environments ... in order that the video/caption author's intention is not undermined by the HTML page author." I totally agree that we need to prevent caption information from one origin leaking to the a containing page with a different origin. That would have interesting implications for certain kinds of solutions based on HTML and CSS ... for example, you wouldn't want the page author to be able to apply selectors that match on attribute values, because then captions with sensitive data in attribute values could leak that data to the page. It's not completely dissimilar to the :visited problem. Rob -- "He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]
Received on Friday, 23 April 2010 10:29:07 UTC