W3C home > Mailing lists > Public > public-html@w3.org > February 2012

Re: Process question re. autofocus bug status [was Re: autofocus on links is missing?]

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Fri, 24 Feb 2012 11:11:35 +0100
To: Danny Ayers <danny.ayers@gmail.com>
Cc: Ian Hickson <ian@hixie.ch>, HTML WG <public-html@w3.org>, Sam Ruby <rubys@intertwingly.net>
Message-ID: <20120224111135854808.b34c4a5f@xn--mlform-iua.no>
Danny Ayers, Fri, 24 Feb 2012 10:47:23 +0100:
> No further information on this has been forthcoming on list, so I'd
> like to ask the Editor directly regarding the following:
> 
>> Bug 13942 - Allow @autofocus on any element with @tabindex
>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=13942
> 
>> Status: Rejected
>> Change Description: no spec change
>> Rationale: Let's see how people do with autofocus on <input> before 
>> we start making it even easier to move focus around.
> 
> The implication is that the bug will be revisited at some point in the
> future.

That's how I interpret it too.

> So when will that be on the Milestone timeline?
> 
> If the intent is actually that the bug should be closed permanently
> within the scope of HTML5, then the rationale is unsatisfactory: the
> question of why further support for autofocus is not desirable isn't
> addressed, leaving the proposal standing unchallenged - for which the
> appropriate resolution isn't WONTFIX.

I don't know if there is formal border between HTML5 bugs and HTMLnext 
bugs, that way?
-- 
Leif Halvard Silli
Received on Friday, 24 February 2012 10:12:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:45 GMT