[TRINIDAD-1] Add @agent support for skin properties

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.8-core, 1.2.8-core
• Component/s: Skinning
• Assignee: Jeanne Waldman
• Reporter: Matt Cooper
• Created: 11/May/07 20:23
• Updated: 27/Jan/10 08:44
• Resolved: 23/Apr/08 18:28

Description

We have @agent support for skin selectors where style entries that appear in the client-side generated CSS file, but not for skin properties (which are only present in the server-side skin).

It would be useful to have different property values for ie than for gecko.

af|someComponent {
-tr-my-property: my-default-value;
}
@agent ie {
af|someComponent

{ -tr-my-property: my-ie-value; }

}

What we have to do now is introduce properties with agent-specific names and reference them by agent name:

af|someComponent {
-tr-my-property: my-default-value;
-tr-my-property-for-ie: my-ie-value;
}

and then in the Renderer look up the value by name accordion to what agent is currently in use.