We've added several new XCSS files for standard controls skinning. They're auto negotiated based on user-agent header, but I'm afraid that won't work well in portal environment. I've created JIRA entry for that: http://jira.jboss.com/jira/browse/RF-2921
They're auto negotiated based on user-agent header
can you, please, give some more explaination of that (is it a new magic technologie...;-)
I guess that adding all the files in the portal page header, won't work ?
even if this do not allow to optimize the needs of css depending on which page is served...
anyway about that, most of the browser put the css files in cache, so even if there is 7 of them, that won't waste the network resources...
may be link the jira with the PortletBridge project ?
No, that's not a new technology.
We've deleloped skinning for controls based on the fact that Safari & Opera browsers apply rich controls styling that we shouldn't touch. Their controls looks just fine and our skinning makes it just worse, so we've decided to apply that for browsers that aren't Safari or Opera.
Adding skin.xcss file in the portal page header won't work as we thought, but if you're not going to use standrad controls skinning then it's ok.
I have not read yet the skinning part of the doc.
I will soon.
right now, I am on making things run.
I will look at this css mechanism and how we may configure in a portal environnement.
any explanation on how the whole thing works is welcome ;-)
particularly about these multiple new xcss files...
I guess this will be added in the doc, later ?
(if not yet)
make a Jira about that, not to forget it ?