On Fri, Sep 23, 2011 at 1:27 PM, Ojan Vafai <o...@chromium.org> wrote:
> On Fri, Sep 23, 2011 at 11:49 AM, Ian Hickson <i...@hixie.ch> wrote: > > > There are no as such concrete use cases though, one use case can be if > > > user want to get the element in focus (may be by scrolling the page on > > > load). Currently, Firefox & Opera does focus the readonly elements on > > > autofocus whereas IE & Webkit does not. Need to clear the ambiguity. > > > > 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. Readonly elements are focusable both in IE and WebKit. > 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 question is whether or not there's any backward compatibility issue given the market share of IE and WebKit today. - Ryosuke
