Search and Top Navigation
#9450 closed bug (duplicate)
Opened July 23, 2013 08:41PM UTC
Closed July 23, 2013 09:01PM UTC
first tab is considered "special" by design - it's a bug.
| Reported by: | PawelRoman | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | none |
| Component: | ui.tabs | Version: | 1.10.3 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
When user clicks on a tab beforeActivate event is fired for the tab.
When tab "clicks itself" only because it HAPPENS to be the first tab - the event is not fired. The only way to do something is to use create() event. Why are there 2 events to do the same thing? Only because some <li> HAPPENS to be first - it should not be handled specifically. What if I change order of tabs and some other tab becomes first tab - my code will stop working.
Attachments (0)
Change History (1)
Changed July 23, 2013 09:01PM UTC by comment:1
| resolution: | → duplicate |
|---|---|
| status: | new → closed |
Duplicate of #8735.Please don't intentionally file duplicate tickets. What you're saying about your code suddenly not working is false. Please ask for help on the forums if you're actually having an issue with some code you wrote.