Opened 13 years ago
Closed 13 years ago
#4211 closed defect (fixed)
TabContainer - retains hover state class
Reported by: | dante | Owned by: | bill |
---|---|---|---|
Priority: | high | Milestone: | 1.0 |
Component: | Dijit | Version: | 0.9 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description (last modified by )
seen in themeTester.html
- select "Closable" tab
- hover CloseNode? (the [x])
- select another tab
- the "closable" tab still looks selected
Attachments (2)
Change History (9)
comment:1 Changed 13 years ago by
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Changed 13 years ago by
Attachment: | Picture 5.png added |
---|
Screenshot of your TabContainer? test showing the problem
comment:2 Changed 13 years ago by
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
I am currently working on the latest code (trunk). I still have problems with the hover status class. Summarizing:
- I select a tab which is closable
- I go hover the close icon
- I select another tab
- The previously selected tab is still displaying the same color even if it is not selected anymore
- It goes back to the right color if I move the mouse hover its close icon again
(see attached pic) Paolo
Changed 13 years ago by
Attachment: | stackcontainer.patch added |
---|
comment:3 Changed 13 years ago by
I added the stackcontainer.patch This issue was the dijitTabCloseButton not updating its status when the child switched if the style was "Checked" This patch updates the status of the button.
Email I submitted a CLA is [email protected]…
comment:4 Changed 13 years ago by
Component: | General → Dijit |
---|---|
Description: | modified (diff) |
Milestone: | → 1.0 |
Owner: | anonymous deleted |
Status: | reopened → new |
Updating description as per your previous comment. Thanks for the patch, although I think this demonstrates a problem with _setStateClass() and baseClass that needs to be fixed.
comment:5 Changed 13 years ago by
Hi there, I'm not one that submitted the patch (not the bug submitter). I agree with you bill, as I was trying to find the problem I noticed that both the tab and the close buttons were using the same div node for baseClass so the node was getting the dijitTabCloseButton and dijitTab classes applied to it. Then in the _setStateClass() function it didn't update the child baseClass on the checked status change. My first attempt at making a patch was trying to accomplish changing it in _setStateClass(), but I couldn't figure out how to find child baseClass(es) so I made a quick patch to update the child baseClass on tab change.
-Sathallrin
comment:6 Changed 13 years ago by
Owner: | set to bill |
---|
comment:7 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
(In [10706]) Refactor setStateClass() related code so that:
- baseClass is always specified in javascript, in this.baseClass, not on the dom node
- If you need different CSS classes based on (for example) hovering over the tab label vs. the tab close button, set stateModifier="CloseButton?" on the tab close button node (which must also have dojoAttachEvent="onmouseenter: _onMouse, onmouseleave: _onMouse"
Fixes #4609, #4211, and I suppose it also allows the user to affect styling by specifying baseClass=foo in markup. Well, that was working before for most of the form widgets but I guess now it works for all of them.
something fixed this. no longer seeing it.