myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Cooper (JIRA)" <...@myfaces.apache.org>
Subject [jira] Issue Comment Edited: (TRINIDAD-1) Add @agent support for skin properties
Date Tue, 15 Apr 2008 22:18:21 GMT

    [ https://issues.apache.org/jira/browse/TRINIDAD-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589259#action_12589259
] 

mattcooper edited comment on TRINIDAD-1 at 4/15/08 3:17 PM:
-------------------------------------------------------------

I would like to see this supported on all Trindad @-rules, not just @agent.  For example,
@accessibility-profile large-fonts {}.

      was (Author: mattcooper):
    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.


Mime
View raw message