Re: [Trinidad] avoiding style class aliasing

[Renzo Tomaselli]

Thanks, Simon. Disabling compression makes things working like they did previously. Btw, the reason why it used to work with previous versions was that until some versions ago (1.0.1) we could disable compression on: org.apache.myfaces.trinidadinternal.DISABLE_CONTENT_COMPRESSION while now it's org.apache.myfaces.trinidad. Moreover, the best solution would be to compress only Trinidad classes - leaving custom classes as they are, but I gues this is impossible if  translation occurs after css merging. -- Renzo Simon Lessard wrote: Hmmm, sounds like a bug. In compression mode, only .xe0 should be generated. You can try to disable content compression for now using <context-param> <param-name>org.apache.myfaces.trinidad.DISABLE_CONTENT_COMPRESSION </param-name> <param-value>true</param-value> </context-param> Regards, ~ Simon On Nov 14, 2007 3:55 AM, Renzo Tomaselli < [EMAIL PROTECTED]> wrote: Hi, I noticed an unpleasant effect due to Trinidad class compression/aliasing. If I define my own class such as: .invisible {    display: none;    visibility: hidden; } then the generated css contains: .invisible,.xe0 {display:none;visibility:hidden} The rendered html page contains always *both* classes, even in places where xhtml source specified just .invisible. The final result is that any js code looking for .invisible fails. I'm using Trinidad 1.0.3. Till 1.0.1 these things were running properly. Even adding dummy attributes to my classes seems not working: an alias is generated anyway, and used in html (in place of original class name). Should I disable alisasing - leaving original class names ? Is that possible at all ? -- Renzo