Heya! Another day, another issue. I just helped one of my teammate debugging the af|inputText:required::content he's trying to implements and I found out some issues.
1) af|inputText:required::content got transformed to af_inputText:required_content instead of af_inputText_required_content because I assume single colon is kept to allow the skin to use CSS pseudo-classes. So I decided to test the various :disabled::label selectors already existing to find out those are working correctly. So I assume there's a list of "allowed" component states hidden somewhere. Anyone knows where that is? Also, shouldn't it be the other way around to make it simpler for skin users? That is keep the single colon in the resulting selector only if the pseudo-clas is a known CSS3 class as specified by W3C. This way, it will be easier for component developers to add new component with custom states supporting selectors using the :state synthax. 2) If you use a disabled inputText inside a panelForm and override the af|inputText:disabled::label selector with color property set to red, it won't have any effect because the style class applied to the cell containing the label will be set to "af|inputText:disabled::label af|panelForm::label-cell", giving priority to af|panelFoorm::label-cell that set color to black. I think the style classes should be either inverted so af|inputText:disabled::label get priority or af|inputText:disabled::label should be placed on the <label> element instead of the cell itself. Regards, Simon Lessard Fujitsu Consulting
