FW: [whatwg] W3C Timed Text Working Group proposal for HTMLCue

Please note that a thread has now commenced on WHATWG which can be viewed
at
https://lists.w3.org/Archives/Public/public-whatwg-archive/2015Sep/0032.htm

l

This email is the first response in the thread:

On 11/09/2015 00:11, "Ian Hickson" <ian@hixie.ch> wrote:

>
>(Please don't cross-post to the WHATWG list -- either post to the WHATWG
>list, or post to other lists, but not both at the same time. It causes
>threads to fragment as people aren't on all the lists.)
>
>On Thu, 10 Sep 2015, Nigel Megitt wrote:
>>
>> We think an HTML cue as a variant of the third option is the best
>> solution.
>
>If you do this please make sure to define in detail how it should all
>work. For example, what happens if a script running inside a cue does
>"history.back()"? What happens if an auto-playing video element in a cue
>is given a URL that points to a resource that requires HTTP
>authentication? Is each cue a separate Document? What happens to media
>queries in a cue?
>
>These questions are but the tip of a very, very large iceberg.
>
>--
>Ian Hickson               U+1047E                )\._.,--....,'``.    fL
>http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
>Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'



-----------------------------
http://www.bbc.co.uk

This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
immediately.
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
this.
-----------------------------

Received on Thursday, 10 September 2015 22:25:04 UTC