Changes between Initial Version and Version 1 of Ticket #10665, comment 4


Ignore:
Timestamp:
Oct 28, 2014, 11:24:54 AM (8 years ago)
Author:
Simen Bekkhus
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #10665, comment 4

    initial v1  
    88Even though W3C might in the future discourage use of ```tabindex```, I still think Selectmenu should mirror whatever the markup for the element is. If someone has set a ```tabindex``` on the ```select```-element, they've probably put it on surrounding elements as well. Then when using Selectmenu, the tabbing gets messed up.
    99
    10 How about printing a warning of some sort in the console, maybe when using jQuery Migrate or something?
     10It seems weird that Selectmenu should be so opinionated. We use it (mainly) to be able to style our ```select```s, not for it to impose a suggestion still in draft form from W3C that removes (maybe wrong word) functionality that's been in the browser forever.
     11
     12
     13How about printing a warning of some sort in the console instead, maybe when using jQuery Migrate or something?
     14
     15Again, I completely agree with the reasoning, but I'm currently working on an application with thousands of lines of code, a lot of it (infested) with ```tabindex```es, and for jQuery UI Selectmenu to require quite a massive refactoring before working properly with regards to ```tabindex``` (without modifying/extending the source, which we currently do) seems wrong to me.