Details
Bug
Major
Description
There is application specific styles in the icemobilespring demo that help style the tabs. When these are removed the tabs look broken. All necessary styling for the components should be in the themes and automatically applied without the need for application-level styling.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
to modify the classes is really just a stop gap. Upon reviewing this component, the tabs positioned at the top or the bottom is done strictly in css. The tabs are always rendered first.
To use a core rendering, it would be best to render them in the flow of where they should be (also, then maybe any browser re-renders with flow may not have the shaking of the buttons?).
Will patch for now, but when this is done with core renderer so JSP has same ability to put tab headers at bottom, will redo so the tab headers also render at the bottom.
Show
Judy Guglielmin
added a comment - - edited to modify the classes is really just a stop gap. Upon reviewing this component, the tabs positioned at the top or the bottom is done strictly in css. The tabs are always rendered first.
To use a core rendering, it would be best to render them in the flow of where they should be (also, then maybe any browser re-renders with flow may not have the shaking of the buttons?).
Will patch for now, but when this is done with core renderer so JSP has same ability to put tab headers at bottom, will redo so the tab headers also render at the bottom.
done for now. with header top being assumed until redo of JSF and JSP tabSet components such that the tabs are rendered in a correct place and don't rely on css to place them above or below the tabset page contents.