I created a wish bug to capture the ability to do this in the trindad skins without hacks:
https://issues.apache.org/jira/browse/TRINIDAD-799 On 11/5/07, Stephen Friedrich <[EMAIL PROTECTED]> wrote: > Thanks a LOT, Sven! > That is working fine. > > It is incredible how you have to twist and bend and find the right > combination of hacks > to make your pages look the way you want uniformly esp. if multi-browser > compatibility > is important. > HTML/CSS simply wasn't made for applications (as opposed to documents). > > Rottstock, Sven wrote: > > Hi, > > > > i had the same problem and i have fixed the problem with the star html > > hack. Here is a short code example: > > > > @agent ie > > { > > .myStyleClass { > > background-color:#ff0000; > > } > > /** CSS Hack (Star-HTML-Hack) especially for IE <= 6 **/ > > /** This is basically a nonsense selector as the html element never has > > a parent element **/ > > /** IE7 will know this and simply ignore the selector **/ > > /** IE6 considers this a valid selector and applies the associated > > styling **/ > > * html .myStyleClass { > > background-color:#00ff00; > > } > > } > > > > Hope, this will help... > > > > -----Ursprüngliche Nachricht----- > > Von: Andrew Robinson [mailto:[EMAIL PROTECTED] > > Gesendet: Montag, 5. November 2007 17:24 > > An: MyFaces Discussion > > Betreff: Re: Skinning for specific @agent _versions_ ? > > > > http://myfaces.apache.org/trinidad/devguide/skinning.html > > > > @agent has the ability to differentiate between IE and say firefox, but it > > seems to be lacking browser version support. > > > > On 11/4/07, Stephen Friedrich <[EMAIL PROTECTED]> wrote: > >> I have a hard time getting my pages look correctly on both IE 6 and and IE > >> 7. > >> In plain CSS this would be my workaround to use 18px on IE 6 and 22px on > >> IE 7: > >> height: 18px; > >> he\ight: 22px; > >> > >> When I try that in my skin, Trinidad recognizes both and removes the > >> first completely from the resulting CSS file. > >> > >> Unfortunately I have to put this property on generated html (by the > >> navigation pane component). > >> The only workaorund I can imagine currently is to switch of > >> compression, so that I can add the CSS in a separate CSS file using > >> the "long" (uncompressed) style name. > >> > >> Any better solution? > >> > >
