Opened 14 years ago
Closed 14 years ago
#3925 closed enhancement (wontfix)
conflict between location.hash and class=ui-tabs-selected
Reported by: | roywb | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 1.7 |
Component: | ui.tabs | Version: | 1.6rc5 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
If I am using location.hash for another purpose (history/state or as an actual anchor) and I have selected the second tab by setting the class to ui-tabs-selected, the first tab will be selected because the code will try to set the tab using the hash (without success) and skip the code that looks for ui-tabs-selected among the <li>s.
Maybe an option should exist to turn off location hash checking or vise versa.
Change History (2)
comment:1 Changed 14 years ago by
Priority: | major → minor |
---|---|
Type: | bug → enhancement |
comment:2 Changed 14 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
There is an option already: selected has highest priority