ACTION-108: Have bug triage subgroup review the bugs associated with HTML WG ISSUE-9 (bugs 5758, 8187, 8657, 8658, 8659, 8736)

http://www.w3.org/html/wg/tracker/issues/9
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5758
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8187
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8657
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8658
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8659
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8736

The bug-triage sub-team has received ACTION-108 during last week's TF call to review a couple of media bugs related to ISSUE-9 [1], here's our opinion:


Bug 5758 (http://www.w3.org/Bugs/Public/show_bug.cgi?id=5758):

Status is VERIFIED LATER. That's OK with me as comment 14
(http://www.w3.org/Bugs/Public/show_bug.cgi?id=5758#c14) points out that most of the issues can be addressed.

What's missing in this bug is a reference to the track element that was introduced later. I believe this element resolves the concerns. I'd suggest that the media sub-team adds such a reference.

I don't think any other action is required, LATER is just fine as the bug can't be closed until a text format is agreed upon.


Bug 8187 (http://www.w3.org/Bugs/Public/show_bug.cgi?id=8187):

VERIFIED FIXED. There are references to audio description tracks now.


Bug 8657 (http://www.w3.org/Bugs/Public/show_bug.cgi?id=8657):

John Foliot wrote in a private mail to the bug-triage team on
2011-01-11: "The media team believes that a video should not commence
playing if existing supporting assets are not completely available to
the end user. Eric Carlson is investigating this in more detail and is
reporting back to our team this week."

Alas the bug doesn't reflect the current state in any comment, so I
believe the media sub-team needs to address this.


Bug 8658 (http://www.w3.org/Bugs/Public/show_bug.cgi?id=8658):

VERIFIED FIXED. The editor adopted Gez' suggestion.


Bug 8659 (http://www.w3.org/Bugs/Public/show_bug.cgi?id=8659):

RESOLVED LATER. I'm not sure if the resolution is satisfying. It says
"we wait for the browser vendors to catch up before specifying an API".
If the API is imperative for accessibility, it needs to be specified
pre-Last Call. We suggest to discuss this in the TF telcon.


Bug 8736 (http://www.w3.org/Bugs/Public/show_bug.cgi?id=8736):

I believe we can set the status to CONFIRMED WORKSFORME as comment #1
suggests. It would be nice to find Philip's original bug ("a year ago")
and mark this bug as a duplicate.


[1] http://www.w3.org/html/wg/tracker/issues/9