[jira] Updated: (ADFFACES-290) configure when we do NOT want a CSS-2 pseudo-class to pass to the generated css file.

["Matthias Weßendorf (JIRA)" <ad...@incubator.apache.org>]

     [ https://issues.apache.org/jira/browse/ADFFACES-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Weßendorf updated ADFFACES-290:
----------------------------------------

    Affects Version/s: 1.0.1-incubating-core-SNAPSHOT

> configure when we do NOT want a CSS-2 pseudo-class to pass to the generated css file.
> -------------------------------------------------------------------------------------
>
>                 Key: ADFFACES-290
>                 URL: https://issues.apache.org/jira/browse/ADFFACES-290
>             Project: MyFaces ADF-Faces
>          Issue Type: Improvement
>          Components: Skinning
>    Affects Versions: 1.0.1-incubating-core-SNAPSHOT
>            Reporter: Jeanne Waldman
>            Priority: Minor
>
> Right now, in CSSGenerationUtils.java, we have a list of pseudo-classes that we pass through to the generated css file when they are a part of a skinning selector. This is the list:
>   static
>   {
>     _BUILT_IN_PSEUDO_CLASSES.add(":first-child");
>     _BUILT_IN_PSEUDO_CLASSES.add(":link");
>     _BUILT_IN_PSEUDO_CLASSES.add(":visited");
>     _BUILT_IN_PSEUDO_CLASSES.add(":hover");
>     _BUILT_IN_PSEUDO_CLASSES.add(":active");
>     _BUILT_IN_PSEUDO_CLASSES.add(":focus");
>   }
> There could be a use case where the component developer has a skinning key with a state, like :visited, but he does not want :visited to be handled by the browser. Instead he wants to handle it himself. An example is the train component. It has a visited concept in that a train stop can be visited, but it isn't visited like a link is visited. 
> Instead of af|train::stop-link:visited{} we are using af|train::stop-link:trainVisited 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.