- From: <bugzilla@jessica.w3.org>
- Date: Wed, 06 Apr 2011 22:11:29 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12425
Aryeh Gregor <Simetrical+w3cbug@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Simetrical+w3cbug@gmail.com
--- Comment #4 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-04-06 22:11:27 UTC ---
Any UI expectations for media fragments that apply to <video>/<audio> should
also apply to viewing the media file in its own tab, or indeed retrieving a
media file from a URL using a non-browser UA -- right? Why is the HTML spec
the right place to put this sort of thing?
I just opened the default movie player on Ubuntu and immediately found an "Open
Location..." option that would let me view media from a URL. The authors of
that application presumably would have no reason to care about HTML or <video>,
only about the semantics of media fragments. Why should they have to look in
the HTML spec to find out how they're expected to display URLs with media
fragments? This should be in the media fragment spec.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 6 April 2011 22:11:30 UTC