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.
Created attachment 25093 [details] Simple html illustrating outline shown on disabled elements
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.
Please provide some feedback.
http://www.whatwg.org/specs/web-apps/current-work/#attr-fe-disabled disabled only appears to affect form elements.
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.
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.
Also, can we instead talk with Mozilla folks and see they can drop "disabled" content attribute support on non-from-control elements?
(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.
(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.
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.
(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.
It seems I can't close this issue. Request someone with the privilege to close the issue.
Gecko no longer supports disabled attribute on non-form control elements. Closing the bug as wontfix.