You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Matt Cooper (JIRA)" <de...@myfaces.apache.org> on 2008/04/16 00:16:21 UTC
[jira] Commented: (TRINIDAD-1) Add @agent support for skin
properties
[ https://issues.apache.org/jira/browse/TRINIDAD-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589259#action_12589259 ]
Matt Cooper commented on TRINIDAD-1:
------------------------------------
I would like to see this supported on all @-rules, not just @agent.
> Add @agent support for skin properties
> --------------------------------------
>
> Key: TRINIDAD-1
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Components: Skinning
> Reporter: Matt Cooper
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.