- From: Sam Ruby <rubys@intertwingly.net>
- Date: Tue, 25 Oct 2011 10:54:13 -0400
- To: HTMLWG WG <public-html@w3.org>
Just to prevent any misunderstandings: this bug is assigned to the CSS WG at this time, and is not being pursued in the HTML WG. It people believe that this is a bug that the HTML WG should pursue, please explain why at this time Detailed status: There have been some discussions about the priority of this bug, for example: http://www.w3.org/2011/10/04-a11y-bugs-minutes.html This bug was created in 2010 before the creation of a CSSOM bugzilla component: http://www.w3.org/Bugs/Public/show_bug.cgi?id=11329 Subsequently, it was moved to the CSSOM component in January: http://www.w3.org/Bugs/Public/show_activity.cgi?id=11329 In September, it became an issue in that WG:: http://www.w3.org/Style/CSS/Tracker/issues/109 PriorityRequest was established as a keyword intended to help with the setting of WG priorities in the August/September timeframe of this year: http://lists.w3.org/Archives/Public/public-html/2011Jun/0315.html The reason why I am mentioning that is that the PriorityRequest keyword was added to this bug in October. The HTML WG chairs would be willing to discuss such requests on a case by case basis, but don't intent to pursue it as long as this bug is not assigned to a component owned by this WG. - Sam Ruby
Received on Tuesday, 25 October 2011 14:56:34 UTC