Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.5
-
Component/s: ICE-Components
-
Labels:None
-
Environment:Operating System: Windows XP
Platform: PC
Description
Currently, the panelTabSet relies on a Form in order to handle the commandLinks
that are rendered in the panelTab headers (the Tabs). The commandLinks require
hidden input fields and these fields are rendered by the FormRenderer.
This issue has been brought up by developers, both internally and community,
several times most recently in the forum ->
http://www.icefaces.org/JForum/posts/list/2962.page#14347
that are rendered in the panelTab headers (the Tabs). The commandLinks require
hidden input fields and these fields are rendered by the FormRenderer.
This issue has been brought up by developers, both internally and community,
several times most recently in the forum ->
http://www.icefaces.org/JForum/posts/list/2962.page#14347
Issue Links
- depends on
-
ICE-329
Components must be contained within a form
-
- Closed
-
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
This is resolved. The new Sparkle TabSet component is now flexible enough to support the following combinations:
- TabSet and all tabPane's inside one form (consistent with the ice:panelTabSet)
- TabSet in one form and all tabPane's in another.
- TabSet in one form and each tabPane contains one or more forms of their own.
Show
Ken Fyten
added a comment - This is resolved. The new Sparkle TabSet component is now flexible enough to support the following combinations:
TabSet and all tabPane's inside one form (consistent with the ice:panelTabSet)
TabSet in one form and all tabPane's in another.
TabSet in one form and each tabPane contains one or more forms of their own.
Requires ability to have interactive components outside of a form component.