-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Original options order incorrect in Chrome #198
Comments
I can confirm incorrect behaviour when using this jsfiddle. In Chromium browser I always got options sorted like [7, 1, 3, 4, 5, 6, 2, 8, 9, 10, 11, 12], but in Firefox options are sorted from 1 to 12. |
I'm having a similar issue. Selectize doesn't use the order of my Array of Objects that is passed from my Web Service. Does anyone knows how to solve this issue? The filter option is not enabled btw. |
I had this problem with 0.7.7, but upgrading to 0.8.5 fixed it for me. |
I am experiencing this issue using 0.8.5. It's a fairly serious problem, as users kind of expect days of the month to be linear. The jsfiddle above is using 0.8.4 and exhibits the same behavior I see in 0.8.5. |
For any other lost pilgrims who have been fighting this issue... |
|
The problem is that ECMAScript standard does not guarantee Array.sort is a stable sort (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#Description). If you have a value you can sort by, you can always specify it as a sortField: Or you can add an |
Same issue here using |
I have the same issue; elements are totally out of order in Google Chrome 39 but are in order in Safari 8 beta. Using Selectize 0.11. The fix was to use |
It looks like this is still an issue. I've just forked the repo and get the same issue when remotely retrieving data. Options are placed into an associative array indexed by their id. This fundamentally reorders them. Applying no sortField or a sortField of [] doesn't work for me. What I've looked to do is re-assign the $order property that is the default sort property. This usually looks at non-dynamic data without ids (i.e. html option tags) and assigns it as an incremental index. I overwrite this for dynamic data and so if no sortField is specified it falls back to the $order property and works correctly |
I have a selectize dropdown with numeric entries from 1 to 31 (i.e. days in month) created from the original select element. Options are sorted correctly in Firefox but incorrectly in Chrome.
The text was updated successfully, but these errors were encountered: