Details
Bug
Description
The ContentMenuItem renderer is rendering the argument 'parent' for the js call using the value of the contentNavBar. But this doesn't seemed to be used in the script. We should remove it if it's not needed.
StringBuilder sb = new StringBuilder("mobi.layoutMenu.showContent('").append(stackClientId);
sb.append("', event");
sb.append(",{ selectedId: '").append(item.getValue()).append("'");
sb.append(",singleSubmit: ").append(item.isSingleSubmit());
sb.append(", parent: '").append(navBar.getClientId(facesContext)).append("'");
Issue Links
- is duplicated by
-
MOBI-672
Client side api for contentStack using core rendering for JSP as well as JSF implementation
-
- Open
-
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
once client side api is provided for contentStack, there will be no js for contentStackMenu, making this redundant
Show
Judy Guglielmin
added a comment - once client side api is provided for contentStack, there will be no js for contentStackMenu, making this redundant
Revision: 38344
Author: philip.breau
Date: October-02-13 8:49:25 PM
Message:
MOBI-485 ContentMenuItem rendering 'parent' js argument which isn't used in layoutmenu.js
Modified : /icemobile/trunk/icemobile/jsf/components/component/src/org/icefaces/mobi/component/contentmenuitem/ContentMenuItemRenderer.java
Show
Philip Breau
added a comment - Revision: 38344
Author: philip.breau
Date: October-02-13 8:49:25 PM
Message:
MOBI-485 ContentMenuItem rendering 'parent' js argument which isn't used in layoutmenu.js
Modified : /icemobile/trunk/icemobile/jsf/components/component/src/org/icefaces/mobi/component/contentmenuitem/ContentMenuItemRenderer.java
This component is getting totally overhauled for 1.4 Beta with use of mobi:transition and client side api for contentSTack.
Once that has been completed (see link) this jira will no longer be relevant