I agree. In ADF Faces we have a 'rule' where we put the style
af|component on the root dom element, so that it is consistent across
all components.
styleClass, inlineStyle, and the root style all go on the root dom element.
In Trinidad it's not so consistent, but it should be, as long as it
doesn't mess up existing skins. If it's just a placeholder right now (we
render class="af_table", but .af_table has no styles), then it won't
mess up existing skins.
Jeanne
Glauco P. Gomes wrote, On 2/13/2009 12:33 PM PT:
The documentation doesn't have the af|table selector, only
af|table::content, af|table::detail, af|table::*
In my skin I have the af|table selector and it isn't rendered (with
org.apache.myfaces.trinidad.DISABLE_CONTENT_COMPRESSION set to true),
only af_table_content, af_table_detail, af_table_* are rendered.
The table component has an outer DIV, and I think that the af|table
selector should be rendered in this tag to respect the actual
behavior, eg.: if I put styleClass="test" in the tr:table, the
rendered html is <div id="xxx" class="test"> ... </div>
What do you think about?
Glauco P. Gomes
Matthias Wessendorf escreveu:
not sure I understood the question.
See here the (incomplete) list of available selectors:
http://myfaces.apache.org/trinidad/skin-selectors.html
Also, it is possible that you have the default setting for skinning
where Trinidad compresses the css class names (like "xyz").
HTH,
Matthias
