- From: <bugzilla@jessica.w3.org>
- Date: Thu, 10 May 2012 16:24:21 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17000
Aaron Colwell <acolwell@chromium.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P2 |P3
--- Comment #2 from Aaron Colwell <acolwell@chromium.org> 2012-05-10 16:24:21 UTC ---
(In reply to comment #1)
> I'd consider the things in the list of limitations as bugs, or are there
> hardware limitations that would make it impossible to support some of these
> things correctly?
Many of these concerns are related to hardware implementations. Hardware
decoders may only allow particular types of parameter changes and still splice
seamlessly. It also isn't clear what sort of gap insertion & overlap behaviors
they support. I fully admit that this is a gray area right now and we need
more implementation experience to determine what is really necessary. This bug
is mainly a placeholder for a concern raised during the spec update process.
> http://lists.w3.org/Archives/Public/public-html/2011Apr/0213.html may be
> relevant here. I think that as far as possible, we should simply require that
> implementations follow the spec and file bugs when they don't.
I agree, but I am concerned that embedded implementations may not be able to
implement the full flexibility the spec provides. It seems like some sort of
profile or capability mechanism might help content authors detect this w/o
simply relying on the UA header.
For now I'm lowering the priority of this bug since the requirements aren't
fully fleshed out and we don't have direct experience with hardware limitations
yet.
--
Configure bugmail: https://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 Thursday, 10 May 2012 16:24:27 UTC