Type: Feature Request
Status: Resolved (View Workflow)
Resolution: Won't Fix
Affects Version/s: 2.6.5 Final
Fix Version/s: None
Component/s: Portal Theme
Environment:Mac OS X
Similar Issues:Show 10 results
JBPORTAL-1105 <p:theme/> mangles HTML assets defined in portal-themes.xml JBPORTAL-1341 Style classes are not populated in TinyMCE JBPORTAL-1434 Change drop down style JBPORTAL-1317 Role Management Portlet: Create New Role Broken JBPORTAL-1694 Add styles to unselected path item for easier styling JBPORTAL-1846 Create Style Guide for renaissance theme and for global styles JBPORTAL-373 "jump to topic page" link has old nukes style JBPORTAL-532 Define CMS security JBPORTAL-2144 Let a portlet defines the browser title JBPORTAL-1701 Define in web module logout semantics
When rendering the <scripts>, <styles>, and <links> defined in *-themes.xml - the <p:theme /> tag appears to reorder the elements, specifically by placing all of the <link> tags after all of the script <tags>.
It appears as though the PortalThemeMetaDataFactory.addChild() methods pull all of the scripts and styles separately.
This is undesirable because theme authors should be able to control the order of their includes:
1) Often, the order that CSS rules are included will affect how the rules are applied.
3) Rendering all of the scripts before all of the link tags can be a performance problem (see: http://developer.yahoo.com/performance/rules.html#css_top)
This is related to: https://jira.jboss.org/jira/browse/JBPORTAL-1105