Opened 10 years ago
Closed 10 years ago
#12762 closed defect (fixed)
TabContainer: checked tab loses checked CSS classes
| Reported by: | Shane O'Sullivan | Owned by: | Karl Tiedt |
|---|---|---|---|
| Priority: | high | Milestone: | 1.7 |
| Component: | Dijit - LnF | Version: | 1.6.0 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description (last modified by )
When a tab is checked, and is then clicked, it loses the dijitTabChecked and dijitChecked classes. This causes it to not be highlighted and can cause the tabs to become misaligned, leaving a number of empty pixels below them.
To replicate, load the themeTester with the Claro theme in Chrome, click the first tab a couple of times, and the tabs will move up and down, with the first tab alternating between appearing selected and unselected.
This is an ugly regression which would badly degrade the TabContainer look and feel
Change History (5)
comment:1 Changed 10 years ago by
| Description: | modified (diff) |
|---|---|
| Owner: | set to bill |
| Status: | new → assigned |
| Summary: | TabContainer checked tab loses checked CSS classes → [regression] TabContainer: checked tab loses checked CSS classes |
comment:2 Changed 10 years ago by
| Milestone: | 1.6.1 → 1.7 |
|---|---|
| severity: | major → normal |
| Summary: | [regression] TabContainer: checked tab loses checked CSS classes → TabContainer: checked tab loses checked CSS classes |
Oh, this is just happening on trunk, not in the 1.6.0 release or the 1.6/ branch.
comment:3 Changed 10 years ago by
| Owner: | changed from bill to Karl Tiedt |
|---|---|
| Status: | assigned → new |
comment:4 Changed 10 years ago by
Interesting, I looked for anything like this as to why the last time it was regressed back to not working and there were no related tickets :/ is it fixable w/o losing the disabling ability?
Ah, good catch, I'll fix.