#8245 closed defect (fixed)
TabContainer: TabButton loses hover effect after mouse has been over close icon
Reported by: | bill | Owned by: | |
---|---|---|---|
Priority: | high | Milestone: | 1.3 |
Component: | Dijit | Version: | 1.2.1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description (last modified by )
In test_TabContainer.html, move your mouse over a tab, then over the tab's close icon, and then back over the main part of the tab.
The tab loses it's dijitTabHover class, thus losing the coloring that should be there (since the mouse is still over the tab).
Change History (4)
comment:1 Changed 12 years ago by
Type: | task → defect |
---|
comment:2 Changed 12 years ago by
Description: | modified (diff) |
---|
comment:3 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
(In [16026]) Refactor TabButton? so that hovering over the close icon only affects the class of the closeButton node, not TabButton?.domNode. This fixes #8245: TabButton? loses hover effect after mouse has been over close icon.
Also removed unneeded CSS from dijit.css, and used JS set .closeNode-hover class name, rather than :hover, which doesn't work in IE except on an <a>.
!strict
comment:4 Changed 12 years ago by
Note: See
TracTickets for help on using
tickets.
Bug is that FormWidget._onMouse() is responding to the onmousleave event on the *close icon* and thinking that the entire tab has lost focus.
A complication from the stateModifier code that tries to affect the class of the widget's domNode in response to changes on inner nodes (in this case, the icon).