18358 2008-04-08 03:27:32 -0700 Feature request / bug - change the way click on disabled option in selects work 2013-11-02 11:05:14 -0700 1 1 1 Unclassified WebKit Forms 525.x (Safari 3.1) PC Windows XP RESOLVED DUPLICATE 122774 InRadar, PlatformOnly P2 Normal --- 1 krudtaa webkit-unassigned ap browserbugs2 eoconnor jonlee mitz webkit-bug-importer oldest_to_newest 76593 0 krudtaa 2008-04-08 03:27:32 -0700 Hi. Current implementation of select lists in Safari can be improved a lot. If you have a select with some option tags and some of the option tags are DISABLED then when you click on a disabled option, then the last highlighted option in the select will be selected. This is very counter intuitive for end-user. For normal users (non-developers) of a web-application, it might not be obvious at first, that when an option is not getting highlighted when moving the mouse pointer over the options in select, it means that it should not be clicked. So the user might want to try clicking a disabled option. If you do this in Firefox, then nothing happens and the select (dropdown list) will stay open, with no change in what is selected in the list. If you click on a disabled option in a select in Safari, then the last highlighted option in the select will be selected and the dropdown list will close. (when I say last highlighted option it will depend on from where you are moving the mousepointer toward the disabled option.... if from above in the dropdown, then the last highlighted option will be the last non-disabled option above the disabled option in question, likewise for options below the disabled option in question) I would like to see a select in safari work same way as in Firefox. If this is implemented then it will be harder for an enduser to make a wrong selection. 88161 1 browserbugs2 2008-08-09 18:44:54 -0700 > I would like to see a select in safari work same way as in Firefox. I agree and I'm voting for this bug. A testcase: http://www.gtalbot.org/BrowserBugsSection/MSIE7Bugs/OptionDisabledSupport.html 88162 2 browserbugs2 2008-08-09 18:47:13 -0700 Tore, In all fairness, I don't think this should be a feature request but a normal bug to fix. A disabled <option> should be dimmed out, grayed out, it should be unfocusable and it should be unselectable. 88163 3 browserbugs2 2008-08-09 19:03:08 -0700 According to Robin Lionheart http://www.robinlionheart.com/stds/html4/results Safari 1.3.2 did not support <option disabled>. So chances are he would also give a no, a red X for support of <option disabled> in Safari 3.1.x. 88170 4 mitz 2008-08-09 23:51:25 -0700 I think this is just a bug that needs to be fixed. 88171 5 mitz 2008-08-09 23:52:00 -0700 <rdar://problem/6138855> 459042 6 jonlee 2011-08-30 11:31:49 -0700 (In reply to comment #0) > If you click on a disabled option in a select in Safari, then the last highlighted option in the select will be selected and the dropdown list will close. (when I say last highlighted option it will depend on from where you are moving the mousepointer toward the disabled option.... if from above in the dropdown, then the last highlighted option will be the last non-disabled option above the disabled option in question, likewise for options below the disabled option in question) This part of the bug has since been fixed. Hovering over a disabled option removes the highlighted state from the last option. Clicking on a disabled option, then, closes the menu but retains the last known selection of the select widget. This is the same behavior as with native apps on OS X, so from a user perspective it should be expected behavior. I think we can mark this bug as fixed. 459044 7 jonlee 2011-08-30 11:34:17 -0700 I'm sorry, I completely missed the Windows XP platform part. :-/ Reopening. 946250 8 mitz 2013-11-02 11:05:14 -0700 Looks like bug 122774 was used to fix this. *** This bug has been marked as a duplicate of bug 122774 ***