Re: raising hgroup as an issue

On 04/07/2011 05:38 AM, Maciej Stachowiak wrote:
>
> It looks like two of those bugs (11731, 11828) are resolved, you are
> certainly free to escalate them at any time if you are dissatisfied with
> the outcome.
>
> 11737 is indeed still open. I would personally advise waiting on that
> one. We're currently asking the editor to prioritize applying WG
> decisions. Once the bulk of that work is complete and we are on track to
> Last Call, we will ask editors to look at LC bugs; there is quite a
> large backlog. In the meantime, I would personally prefer not to
> distract Ian from work on applying decisions by asking him to jump on
> specific LC bugs.

It has been over three months.  I don't fault the editor for not looking 
at this one, but if he hasn't looked at this one yet there is no reason 
to stop others from proceeding in parallel.

> Regards,
> Maciej

- Sam Ruby

> On Apr 7, 2011, at 2:03 AM, Steve Faulkner wrote:
>
>> Hi Maciej,
>>
>> on february 1st you wrote:
>>
>> "so far, the editor hasn't resolved the bug yet, and it's been less
>> than 30 days. If the bug gets rejected, or if it sits unaddressed for
>> an overly long time, it would be fine to escalate it to an issue."
>>
>> its now april 7th and there has been no action by the editor, so would
>> like to raise it as a last call issue, any objections?
>>
>> Lars Gunther provides a good summation of where we are at in regards
>> to hgroup [1]
>>
>> I for one think that hgroup is something worth discussing sooner
>> rather than later, as I believe there is a good chance that further
>> discussion and review will lead to a substantive change. Having hgroup
>> as is, in the HTML5 spec, if indeed it is removed or modified, does no
>> one any favours especially developers who may use the element.
>>
>> bugs [2] relating to hgroup
>>
>> [1] http://lists.w3.org/Archives/Public/public-html/2011Jan/0256.html
>> [2] 11731 <http://www.w3.org/Bugs/Public/show_bug.cgi?id=11731> ,
>> 11737 <http://www.w3.org/Bugs/Public/show_bug.cgi?id=11737> , 11828
>> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=11828>
>>
>>
>> regards
>> stevef
>>
>> On 1 February 2011 19:27, Maciej Stachowiak <mjs@apple.com
>> <mailto:mjs@apple.com>> wrote:
>>
>>
>>     On Feb 1, 2011, at 11:16 AM, John Foliot wrote:
>>
>>     > Maciej Stachowiak wrote:
>>     >>
>>     >> That's definitely the case, and we intent to apply the decision
>>     policy
>>     >> as usual. If the bug report on this ends up escalated to a tracker
>>     >> issue, we will treat it as a Last Call issue. All I'm saying is
>>     that
>>     >> we do not intend to do anything special outside the bounds of
>>     the usual
>>     >> process.
>>     >
>>     > Given the scope of the topic being discussed (should <hgroup>
>>     remain) it
>>     > seems that this is beyond just a simple bug, and so it needs to be
>>     > escalated as an issue, then sit back and wait for it to be
>>     addressed in
>>     > due course - is that correct Maciej?
>>     >
>>     > Steve, do you care to do the honors?
>>
>>     So far, the editor hasn't resolved the bug yet, and it's been less
>>     than 30 days. If the bug gets rejected, or if it sits unaddressed
>>     for an overly long time, it would be fine to escalate it to an issue.
>>
>>     Regards,
>>     Maciej
>>
>>
>>
>>
>> --
>> with regards
>>
>> Steve Faulkner
>> Technical Director - TPG
>>
>> www.paciellogroup.com <http://www.paciellogroup.com/> |
>> www.HTML5accessibility.com <http://www.HTML5accessibility.com/> |
>> www.twitter.com/stevefaulkner <http://www.twitter.com/stevefaulkner>
>> HTML5: Techniques for providing useful text alternatives -
>> dev.w3.org/html5/alt-techniques/ <http://dev.w3.org/html5/alt-techniques/>
>> Web Accessibility Toolbar -
>> www.paciellogroup.com/resources/wat-ie-about.html
>> <http://www.paciellogroup.com/resources/wat-ie-about.html>
>

Received on Thursday, 7 April 2011 09:58:30 UTC