W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2011

[whatwg] Autofocus readonly Input Elements

From: Kaustubh Atrawalkar <kaustubh@motorola.com>
Date: Sun, 25 Sep 2011 22:29:54 +0530
Message-ID: <CANw-Mg8oPgUOdF-Q4qQj7zgJqm=WQFLqRupuFbfa9TXVORcjgA@mail.gmail.com>
>
>  Right. The question is whether read-only/disabled/hidden inputs should be
>>>> focusable.
>>>>
>>>
>>> Readonly elements are focusable both in IE and WebKit.
>>>
>>
>> Agree, then they can be autofocus-able as well as per algorithm.
>>
>
> No, I don't necessarily conclude that. Backward compatibility is more
> important than the spec. The spec should reflect the reality of the Web if
> any.
>
>
Yes, true and accepted. Specs should reflect the user benefit and
compliances rather than just one decided algorithm.


>  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.
>>>
>>> Unless user gives a readonly element autofocus attribute this wont be
>> triggered. And when user explicitly add autofocus he expects it to be
>> focused. But still, the question remains with which behavior we should
>> comply.
>>
>
> Having said that, I agree with you. If the author explicitly adds autofocus
> attribute, it seems more natural to think the element should be
> auto-focusable.
>
>
In this case there would be issue if there any sites which have readonly
elements made autofocus but still not expecting to be focused on page load
which would be very rare scenario. We can conclude to have readonly elements
respecting autofocus attribute ?
Received on Sunday, 25 September 2011 09:59:54 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:36 UTC