Bug 793945 (JBEPP-1016)

Summary: EPP52-EID_108: Priority for skin modules
Product: [JBoss] JBoss Enterprise Portal Platform 5 Reporter: Thomas Heute <theute>
Component: PortalAssignee: Matt Wringe <mwringe>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: mwringe, theute
Target Milestone: ---   
Target Release: 5.2.0.DEV03   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEPP-1016
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-18 17:00:58 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Thomas Heute 2011-07-19 06:19:44 UTC
project_key: JBEPP

Comment 1 Thomas Heute 2011-08-16 08:18:36 UTC
Link: Added: This issue is related to GTNPORTAL-1450


Comment 2 Matt Wringe 2011-08-18 17:00:58 UTC
Release Notes Text: Added: Add priority for skin module css loading


Comment 3 Thomas Heute 2011-09-22 06:59:01 UTC
Release Notes Docs Status: Added: Not Yet Documented


Comment 5 Jared MORGAN 2011-11-28 03:55:57 UTC
Release Notes Docs Status: Removed: Not Yet Documented Added: Needs More Info
Primary SME: Added: mwringe
NEEDINFO Due Date: Added: 30/Nov/11
NEEDINFO: Removed: Nobody Added: Subject Matter Expert


Comment 6 Thomas Heute 2011-11-28 09:32:58 UTC
Release Notes Docs Status: Removed: Needs More Info Added: Not Yet Documented
Release Notes Text: Removed: Add priority for skin module css loading Added: Starting with EPP 5.2.0 it is now possible to define the ordering of skins when presented to the end-user for choosing one.


Comment 7 Matt Wringe 2011-11-28 15:18:16 UTC
"Starting with EPP 5.2.0 it is now possible to define the ordering of skins when presented to the end-user for choosing one."

This is not what the issue is about, this issue has to do with the order of css which get loaded. By specifying the order, you can override the skin css elements (since the last element takes precedent). See the original jira https://issues.jboss.org/browse/GTNPORTAL-1450

Comment 8 Thomas Heute 2011-11-28 15:22:29 UTC
Busted, I did that too quickly ;)
Matt can you replace the text ? The previous one: "Add priority for skin module css loading" was not very detailed.

Comment 9 Thomas Heute 2011-11-28 15:22:46 UTC
Release Notes Docs Status: Removed: Not Yet Documented Added: Needs More Info
Release Notes Text: Removed: Starting with EPP 5.2.0 it is now possible to define the ordering of skins when presented to the end-user for choosing one. Added: Add priority for skin module css loading


Comment 10 Matt Wringe 2011-11-28 16:16:25 UTC
Release Notes Text: Removed: Add priority for skin module css loading Added: Priority for the loading of skin css files can now be specified in gatein-resources.xml using the css-priority xml element. This allows for the css elements to be loaded in a specific order, which can be useful for overriding existing css elements.


Comment 11 Matt Wringe 2011-11-28 16:16:57 UTC
Is the new release text ok? Or does it need more details?

Comment 12 Thomas Heute 2011-11-28 16:26:53 UTC
Release Notes Docs Status: Removed: Needs More Info Added: Not Yet Documented


Comment 13 Jared MORGAN 2011-11-30 01:57:17 UTC
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Feature Request
Release Notes Text: Removed: Priority for the loading of skin css files can now be specified in gatein-resources.xml using the css-priority xml element. This allows for the css elements to be loaded in a specific order, which can be useful for overriding existing css elements. Added: Priority for the loading of skin css files can now be specified in gatein-resources.xml using the css-priority xml element. This allows the css elements to be loaded in a specific order, which can be useful for overriding existing css elements.