Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.0.1, EE-3.0.0.GA
-
Fix Version/s: 3.1.0.RC1, 3.1, EE-3.0.0.GA_P01
-
Component/s: ACE-Components
-
Labels:None
-
Environment:Any
-
Assignee Priority:P1
Description
ace:menu, ace:menuButton and ace:contextMenu lose their styling after dynamic updates that change the structure of the menu (i.e. adding, removing or modifying a menu item or submenu). This is caused by having a client id in the root <ul> element, so when the structure of the menu changes the dom diff only sends an update starting from this <ul> element, and it doesn't send an update for the <script> tag that re-runs the initialization function that ultimately applies all the styling in the client. This is somehow related to ICE-7816. The problem was initially reported in ICE-7323.
Steps to reproduce:
1. Build and deploy the test application located at http://server.ice:8888/svn/repo/qa/trunk/Regression-Icefaces2/Sparkle/Nightly/menu/
2. Go to the menuDynAttribute.jsf test page
3. Checking the 'rendered' box first and then check the 'tiered' box
4. See how the menu loses all it styling and looks like a plain HTML list.
ICE-7323 also describes how to reproduce the problem using the menuDisable.xhtml test page of the same application..
Steps to reproduce:
1. Build and deploy the test application located at http://server.ice:8888/svn/repo/qa/trunk/Regression-Icefaces2/Sparkle/Nightly/menu/
2. Go to the menuDynAttribute.jsf test page
3. Checking the 'rendered' box first and then check the 'tiered' box
4. See how the menu loses all it styling and looks like a plain HTML list.
Issue Links
- blocks
-
ICE-7323 Add ability to disable/enable menuItems (and subMenus) via component attribute and JavaScript API.
- Closed
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion