Re: Media Fragments Working Group: Agenda 06 April, Telecon *0900 UTC*

Hi Silvia,

> I have registered 3 new bugs. The issues listed in the email are thus
> addressed as follows:
>
> 1. Interpretation of temporal media fragment URI in browser navigation:
> This bug is already present and didn't need separate submission
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=10723
>
> 2. User interface of temporal media fragment URI in browser navigation:
> Is a User Agent only issue, so I didn't know where that would go.
> Instead, I have merged it with 3.
>
> 3. User interface of temporal media fragment URI in @src of video element:
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=12425
>
> 4. Effect when @src of video element contains temporal media fragment
> URI and @loop
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=12426
>
> 5. User interface of spatial media fragment URI in<img>  or<video>
> resource, or in browser navigation
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=12427
>
> 6. User interface of track media fragment URI in<audio>  or<video>
> resource, or in browser navigation
> I have not registered a bug on this since the track media fragment
> URIs now have examples in the spec and seem to have been introduced in
> this way. I still wonder if it is necessary to explicitly state in the
> HTML5 spec that only the named tracks will be displayed when used in a
> media element's @src, but I think the HTML5 spec is referring to our
> spec for this, so it's not necessary.

Thanks a lot! I will also keep track of those 4 bugs and this certainly 
closes your ACTION-213.

   Raphaël

-- 
Raphaël Troncy
EURECOM, Multimedia Communications Department
2229, route des Crêtes, 06560 Sophia Antipolis, France.
e-mail: raphael.troncy@eurecom.fr & raphael.troncy@gmail.com
Tel: +33 (0)4 - 9300 8242
Fax: +33 (0)4 - 9000 8200
Web: http://www.eurecom.fr/~troncy/

Received on Wednesday, 6 April 2011 07:31:35 UTC