RE: W3C/WHATWG overlap going forward

Sam Ruby wrote:
"2) We have features that were initially marked "at risk" in HTML 5.0 and subsequently dropped with the expectation that these features ship at a later date.  We also have literally hundreds of pre-existing bug reports, a number of which are substantive.  We have a number of existing HTML WG participants, including at least two editors, who have an interest on addressing these items.  There also is an interest in limiting the observable differences between what the WHATWG HTML spec and the W3C HTML require of both content producers and user agents."

How is the backlog being handled? It may not work in this situation, but the HTML Accessibility TF had a bug triage team that monitored incoming bugs and attempted to manage outstanding ones.

It requires a small group of people with knowledge of the spec and the WG's capabilities, but from your note it sounds as though that might already be the case? The goal being to get a handle on what needs to be done, work on as much as possible, and find other people to help out with the rest.

Léonie.
Senior Accessibility Engineer, TPG
@LeonieWatson @PacielloGroup

Received on Wednesday, 12 November 2014 09:14:28 UTC