Weekly Resolved & Rejected Bugs Report

Hello Everyone,

Since the last report we have had:

1 WONTFIX bug.
1 WORKSFORME bug.
1 REOPENED bug.
1 LATER bug.
1 NEW/DUPLICATE a11y bug reported.
1 CLOSED bug.

Details are as follows.

1. WONTFIX BUGS:

1.1 Bug 11533: "clarify if specially focusable elements mean 'all
elements with defined valid tabindex' or 'elements with a tabindex
that allows sequential focusing.'" reported by contributor@whatwg.
Ian's Rationale: "No, it shouldn't be sequentially focusable. An
element without a tabindex="" attribute (e.g. <div>) isn't specially
focusable, for example. Don't confuse .tabIndex with tabindex=""."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11533#c3


2. WORKSFORME BUG:

2.1 Bug 11239: "Canvas support accessible caret tracking independent
of Focus Ring tracking" reported by Rich Schwerdtfeger.
Charles Pritchard  reopened this bug on February 2. Sam remarked it
"WORKSFORME" and commented "Charles: the status of issue 131 is that
it is awaiting proposals:
http://lists.w3.org/Archives/Public/public-html/2011Jan/0200.html
Please feel free to submit one. Meanwhile, please do NOT reopen bugs
that have already been escalated as an issue."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11239#c9


3. REOPENED BUG:

1.2 Bug 11593: "the <track> @kind attribute should include the all of
the identified accessibility content types" reported by John Foliot.
Ian closed bug 11593. John reopened it.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11593#c9
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11593#c10


4. LATER BUG:

4.1 Bug 11342: "TextMetrics should include distance from textBaseline
to each of the baselines in the text" reported by Rich Schwerdtfeger.
Ian's Comment "Since this is a new feature request, I'm marking this
LATER for the time being. This, as well as a number of other
TextMetric issues such as the proposal in bug 7798, are likely to be
the first things we add to the canvas API when we next add features to
the canvas API. In the meantime, we really need to wait for
implementations to catch up with what's been specified so far."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11342#c9


5. NEW/DUPLICATE BUG:

5.1 Bug 12002: "User agents should provide controls to enable or
disable the display of closed captions, audio description tracks, and
other additional data associated with the video stream, though such
features should, again, not interfere with the page's normal render"
reported by contributor@whatwg.
Martin resolved bug 12002 as a DUPLICATE of bug 9452.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12002#c2


6. CLOSED BUG:

6.1 Bug 11395: "Use media queries to select appropriate <track>
elements" reported by Frank Olivier. Assigned to John Foliot.
Status: CLOSED WONTFIX.
David Singer closed this bug. His comment: "I think that this is being
addressed in a different way so we should close it."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11395


7. RELATED REFERENCES:

Weekly Resolved and Rejected Bugs Reports Archive
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Weekly_Resolved_and_Rejected_Bugs_Reports

Backlog of Bugs Awaiting "A11yTF" Keyword Decision
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision

A11y Resolved Bug Comparisons:
http://www.d.umn.edu/~lcarlson/html5bugchart/

New Bug Snapshots
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/New_A11Y_Bug_Snapshot

Pre-Last Call 1 Bug Snapshots
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/SnapshotPLC1

"A11yTF" Keyword Criteria (Draft)
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/KeywordCriteria

Bug Status Table:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs#Bug_Status_Table

Escalating a Bug to an Issue:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Escalating_a_Bug_to_an_Issue

Accessibility Change Proposal Status Table:
http://www.w3.org/WAI/PF/HTML/wiki/Accessibility_Change_Proposal_Status

HTML Last Call Timeline and Action Plan
http://www.w3.org/html/wg/wiki/LastCallTimeline

Best Regards,
Laura

--
Laura L. Carlson

Received on Saturday, 12 February 2011 07:26:37 UTC