Details
-
Type: Bug
-
Status: Closed
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 3.2, 3.3, 4.0.BETA
-
Fix Version/s: EE-3.3.0.GA, 4.0.BETA, 4.0
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ICEfaces3 trunk revision# 34552
-
Assignee Priority:P2
Description
When rendering a menuButton with disabled=true there is a div rendered in the top left corner. The div prevents the user from interacting with the page (in this example, I am unable to click the checkboxes).
To reproduce:
1) Build / deploy test app located at: http://server.ice:8888/svn/repo/qa/trunk/Regression-Icefaces2/Sparkle/Nightly/menuButton
2) Navigate to 'MenuButton Dynamic Attribute Test'
3) Click rendered to display the menuButton
4) Click disabled to disable the menuButton
Div is rendered when the menuButton is disabled.
To reproduce:
1) Build / deploy test app located at: http://server.ice:8888/svn/repo/qa/trunk/Regression-Icefaces2/Sparkle/Nightly/menuButton
2) Navigate to 'MenuButton Dynamic Attribute Test'
3) Click rendered to display the menuButton
4) Click disabled to disable the menuButton
Div is rendered when the menuButton is disabled.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Committed fox at revision 34600.
The wijmo menu widget has its own way to disable menus by creating a transparent div over the menu to prevent interaction. The script to do this copies the menu's coordinates and dimensions. In the case of the MenuButton, the menu is already hidden, and only the button itself needs to be disabled. So, we simply avoid passing the 'disabled' parameter to wijmo, since the menus are already hidden and the user can't interact with them.