RESOLVED WONTFIX 22202
Would like “disabled” attribute to work on non-form elements 
https://bugs.webkit.org/show_bug.cgi?id=22202
Summary Would like “disabled” attribute to work on non-form elements
Johan Lund
Reported 2008-11-12 02:42:24 PST
I have 2 divs with tabIndex=1 and one of them is disabled. If I tab to the disabled element it displays a focus outline. This is not the case in e.g. Firefox.
Attachments
Simple html illustrating outline shown on disabled elements (110 bytes, text/html)
2008-11-12 02:46 PST, Johan Lund 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Johan Lund
Comment 1 2008-11-12 02:46:07 PST
Created attachment 25093 [details] Simple html illustrating outline shown on disabled elements
Antaryami Pandia (apandia)
Comment 2 2012-02-13 02:45:00 PST
Adding some webkit reviewers. The main issues is that webkit focuses element, even if its disabled. I modified the attached test case to verify it:- <html><head> <script type="text/javascript"> function setStyle() { document.getElementById("div1").style.background="yellow"; } function setStyle1() { document.getElementById("div2").style.background="red"; } </script></head> <body> <div id="div1" tabIndex="1" onfocus="setStyle()">123456</div > <div id="div2" tabIndex="1" disabled="true" onfocus="setStyle1()">abcdefg</div > </body></html> Currently the disabled attribute is supported only for form control elements. It seems firefox supports "disabled" attributes for all html tags. 1. Is the current webkit behavior is inteded one? 2. Should we support "disabled" attribute for elements other than form controls? Please provide feedback.
Antaryami Pandia (apandia)
Comment 3 2012-02-16 02:53:42 PST
Please provide some feedback.
Eric Seidel (no email)
Comment 4 2012-02-16 08:06:42 PST
http://www.whatwg.org/specs/web-apps/current-work/#attr-fe-disabled disabled only appears to affect form elements.
Darin Adler
Comment 5 2012-02-16 09:34:17 PST
If disabling is applied to other types of elements by Firefox, then that’s an extension, not something from the current HTML standards. If we think that’s a desirable feature I suggest we bring it with other folks working on the HTML standard at W3C. I don’t think this is a feature that’s so compelling that we’d want to do it without first discussing it with the others.
Antaryami Pandia (apandia)
Comment 6 2012-02-16 21:55:51 PST
Thanks Eric, Darin for the feedback. I was of the same opinion, since disabled attribute affects only form control elements. Actually the issue was logged as an outline issue, but I found that the issue is with disabled attribute being used with a non-form control element (darin has also updated the title of the issue). Thats the precise reason I asked the feedback of yours, as its not according to spec and also a feature which may not be of that much interest to a web developer.
Ryosuke Niwa
Comment 7 2012-02-16 22:42:51 PST
Also, can we instead talk with Mozilla folks and see they can drop "disabled" content attribute support on non-from-control elements?
Antaryami Pandia (apandia)
Comment 8 2012-02-16 22:59:20 PST
(In reply to comment #7) > Also, can we instead talk with Mozilla folks and see they can drop "disabled" content attribute support on non-from-control elements? So should I log a bug at Mozilla bugzilla or talk on Mozilla dev channel.What would you recommend.
Ryosuke Niwa
Comment 9 2012-02-16 23:04:29 PST
(In reply to comment #8) > (In reply to comment #7) > > Also, can we instead talk with Mozilla folks and see they can drop "disabled" content attribute support on non-from-control elements? > > So should I log a bug at Mozilla bugzilla or talk on Mozilla dev channel.What would you recommend. Asking on #developer might work.
Antaryami Pandia (apandia)
Comment 10 2012-02-22 22:28:31 PST
I had sent a mail to mozila dev forum and as suggested logged a bug in firefox. https://bugzilla.mozilla.org/show_bug.cgi?id=729845 Also I think we can close this issue as this is the expected behavior.
Mounir Lamouri
Comment 11 2012-03-08 07:35:35 PST
(In reply to comment #0) > I have 2 divs with tabIndex=1 and one of them is disabled. > If I tab to the disabled element it displays a focus outline. > This is not the case in e.g. Firefox. This is a bug in Gecko/Firefox and we going to fix that. I guess this bug could be marked as WONTFIX.
Antaryami Pandia (apandia)
Comment 12 2012-03-11 22:49:19 PDT
It seems I can't close this issue. Request someone with the privilege to close the issue.
Ryosuke Niwa
Comment 13 2012-03-11 23:24:13 PDT
Gecko no longer supports disabled attribute on non-form control elements. Closing the bug as wontfix.
Note You need to log in before you can comment on or make changes to this bug.