W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2012

[whatwg] Autofocus readonly Input Elements

From: Ian Hickson <ian@hixie.ch>
Date: Thu, 26 Jan 2012 21:57:42 +0000 (UTC)
Message-ID: <Pine.LNX.4.64.1201262149010.16982@ps20323.dreamhostps.com>
On Fri, 23 Sep 2011, Ojan Vafai wrote:
> On Fri, Sep 23, 2011 at 11:49 AM, Ian Hickson <ian at hixie.ch> wrote:
> >
> > If they're focusable at all, I don't see why they wouldn't be 
> > autofocusable. Is there a use case for special-casing read-only ones?
> 
> Right. The question is whether read-only/disabled/hidden inputs should 
> be focusable. I don't personally see pros and cons in either direction, 
> but I wanted to make sure there was agreement here before changing 
> WebKit's behavior.

The intent is to match the behaviour of the native platform GUI, which 
generally speaking means readonly controls are focusable, and disabled and 
hidden ones are not.

There's nothing special about autofocus="" here. It's just like calling 
focus() on the element.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 26 January 2012 13:57:42 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:10 UTC