I have a followup question related to this thread.
Even from the example given here, if one simply wants to add a selector based on others in the skin shouldn't this just be a simple css addition?
For example, I already have a custom skin that works fine (just basic CSS tweaks).
I tried adding the following both to the custom skin's CSS and to a CSS that is in a skin addition (just for good measure before I read this thread):
af|teststyle
{
-tr-rule-ref: af|panelTabbed::tab;
}
.foo
{
-tr-rule-ref: af|panelTabbed::tab;
}
Note that I tried teststyle by itself as well. I see nothing of these two new styles in my stylesheet once it is generated. I am missing something obvious, I am sure.
Also, can someone make it a little more clear than in the docs why the component-specific selectors don't have the dot in front? I read the docs and the FAQ and am clear that they don't but I don't understand why and this has me wondering about how I'm going to define styles for custom (or existing non-Trinidad components).
Thanks in advance,
Christian
This message contains information from Equifax Inc. which may be confidential and privileged. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify by e-mail [EMAIL PROTECTED]
- Skin Additions for Custom Components Samba
- Re: Skin Additions for Custom Components Cristi Toth
- Re: Skin Additions for Custom Components Samba
- Re: Skin Additions for Custom Components Jeanne Waldman
- Re: Skin Additions for Custom Components Cristi Toth
- Re: Skin Additions for Custom Components Christian . Hall
- Re: Skin Additions for Custom Components Christian . Hall
- [Trinidad] Selector types clarification Christian . Hall

