Hello all, I raised that issue a while back, but now it's a bit more important since I'm trying to finalize ADFFACES-49 issue. What selector synthax do you prefer for states: 1.1. <component>::<subPart>:<state> 1.2. <component>:<state>::<subPart>.
I prefer the former and it's easier to implement. However, we already have some :disabled that use the latter synthax. Secondly, there's also the issue raised by Jeanne, how should we manage which states are intercepted and which should pass through and be copied in the final CSS: 2.1. Use a component specific list, so that :disabled could pass through for some components but get intercepted for some others? If that solution is selected, how/where should we configure that list, in the faces-config's metadata? 2.2. Use a list of pseudo-classes passing through for all components. Such list would have to be based on W3C, but as Jeanne observed, such list would break our :disabled that we're intercepting currently and could lead to som.e problems if more pseudo-classes are added in future version of CSS. 2.3. Use a static list of pseudo-classes to intercept used by all components? If so, where should we place it? This solution probably has the same flaws as 2.2 if a new pseudo-classes i nthe CSS specification matches a name defined in the intercept list. 2.4. Use a prefix for intercepted pseudo-classes like the -ora- used for properties? My votes are: +1 for 1.1 +1 for 2.2, but I would not place states resolvable during rendering in that list, so that disabled is still intercepted.
