[ http://issues.apache.org/jira/browse/ADFFACES-206?page=comments#action_12439341 ] Jeanne Waldman commented on ADFFACES-206: -----------------------------------------
Simon, I was thinking of a way that is very similar to your #2. I rewrote your example to fit my idea. 2) Alter CSSGenerator to use a different path for MSIE so that composite selectors get reduced to a single selector by pair of two and add code to renderStyleClasses combine the classes accordingly to see if it was defined in the skin.Here's a little example of that solution: af|myComponent:state1:state2::subComponent CSS generator first split that into 3 selectors (current behavior): af|myComponent with states :state1 and state2 af|myComponent::subComponent Then sort them alphabetically (will improve performance in the end, especially in renderStyleClasses): af|myComponent:state1:state2 af|myComponent::subComponent Notice that you cannot reorder where the state pseudo-classes are in relation to the main selector/pseudo-elements. If you do, it totally changes the meaning of the style definition. In the shortened stylemap, we currently do not put pseudo-classes. So we'd put af|myComponent and af|myComponent::subComponent. We need a method similar to renderStyleClasses, but where you know which ones are the states, and which one is the main selector. So renderStyleClassWithStates(selector, states), and we render all the combinations of selector-state1 selector-state2 selector-state1-state2 (with the states being alphabetized.) If selector was shortened to x10, for example, it would be x10-state1, x10-state2, x10-state1-state2 that we would render > CSS 2 composite selector is not supported in MSIE 6 > --------------------------------------------------- > > Key: ADFFACES-206 > URL: http://issues.apache.org/jira/browse/ADFFACES-206 > Project: MyFaces ADF-Faces > Issue Type: Bug > Components: Skinning > Environment: Microsoft Internet Explorer 6 (and most likely older > versions as well) > Reporter: Simon Lessard > > Microsoft Internet Explorer 6 does not support CSS 2 composite selectors, > e.g. ".someClass.anotherClass". However, the skinning engine uses those for > states mainly. For example, af|component:myState will be parsed to > .af_component.p_AFMyState in the generated CSS and the renderer will add both > classes on the component. > MSIE 6 only evaluate the latest class in the classe list when evaluating > composite selector which has very bad results for some component. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
