You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Anand V Nath (JIRA)" <de...@myfaces.apache.org> on 2013/10/03 06:28:42 UTC
[jira] [Updated] (TRINIDAD-2399) support css client side rules in
skinning framework
[ https://issues.apache.org/jira/browse/TRINIDAD-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anand V Nath updated TRINIDAD-2399:
-----------------------------------
Status: Patch Available (was: Reopened)
> support css client side rules in skinning framework
> ---------------------------------------------------
>
> Key: TRINIDAD-2399
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2399
> Project: MyFaces Trinidad
> Issue Type: New Feature
> Components: Skinning
> Affects Versions: 2.1.0-core
> Reporter: Anand V Nath
> Assignee: Scott O'Bryan
> Fix For: 2.1.0-core
>
> Attachments: jira-2399-bug-fix.patch, jira-2399.patch
>
>
> This ER is for introducing client side css rule support in skinning framework.
> Here's a list of known CSS at-rules:
> @document - uses nested selectors that need to be resolved
> @font-face - probably safe to blindly pass through
> @keyframes - probably safe to blindly pass through
> @media - uses nested selectors that need to be resolved
> @page - probably safe to blindly pass through
> @supports - uses nested selectors that need to be resolved
> These rules can be split into two based on its usage:
> @document, @keyframes, @media, @support uses following syntax:
> @rule {
> selector
> {
> property : value;
> property : value;
> property : value;
> }
> }
> @font-face and @page uses following syntax:
> @rule {
> property : value;
> property : value;
> property : value;
> }
--
This message was sent by Atlassian JIRA
(v6.1#6144)