- From: <bugzilla@jessica.w3.org>
- Date: Fri, 24 May 2013 00:40:40 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22137 Aaron Colwell <acolwell@google.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |acolwell@google.com --- Comment #2 from Aaron Colwell <acolwell@google.com> --- It is not that simple to relax these requirements. Please provide a detailed description of how the UA is supposed to determine what tracks map to eachother across these boundaries. Indicate how the UA is supposed to maintain and update the set of selected/enabled tracks when this happens keeping in mind that on every boundary the track IDs can be completely different. Here is an initial set of questions that I think need detailed answers before we can proceed: 1. What extra information is required to make this work? 2. Is this information mandated in all the current file formats the spec supports? If not, what are the fallback behaviors? 3. How can these transitions be achieved with minimal to no burden the web application? 4. What is acceptable fallback behavior for implementations that can't fully support these types of changes in track count? 5. What information in the UA is expected to guide selection of these extra tracks? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 24 May 2013 00:40:41 UTC