You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@myfaces.apache.org by ar...@apache.org on 2013/12/17 17:43:47 UTC
svn commit: r1551615 -
/myfaces/trinidad/trunk/src/site/xdoc/devguide/skinning.xml
Author: arobinson74
Date: Tue Dec 17 16:43:46 2013
New Revision: 1551615
URL: http://svn.apache.org/r1551615
Log:
TRINIDAD-2437
Commit the patch. Thanks to Anand
Modified:
myfaces/trinidad/trunk/src/site/xdoc/devguide/skinning.xml
Modified: myfaces/trinidad/trunk/src/site/xdoc/devguide/skinning.xml
URL: http://svn.apache.org/viewvc/myfaces/trinidad/trunk/src/site/xdoc/devguide/skinning.xml?rev=1551615&r1=1551614&r2=1551615&view=diff
==============================================================================
--- myfaces/trinidad/trunk/src/site/xdoc/devguide/skinning.xml (original)
+++ myfaces/trinidad/trunk/src/site/xdoc/devguide/skinning.xml Tue Dec 17 16:43:46 2013
@@ -1268,14 +1268,19 @@ af|navigationPane::tabs-active af|naviga
<P>
If you use any rule which is not listed in either server side at-rules or client side at-rules, it will be
rendered as client side rule similar to @media or @document.
- <b>Note:</b>
- Styles inside client side at-rules cannot be used with tr-rules. This is because, in server side, we do not
- know if the referred style will be rendered.
- On the contrary, tr-rules can be used inside client side at-rules to refer styles or properties define outside
- client rules.
-
- Some example usages:
</P>
+ <p>
+ <b>Notes:</b>
+ <ul>
+ <li>Styles inside client side at-rules cannot be used with tr-rules. This is
+ because, in server side, we do not know if the referred style will be rendered.
+ On the contrary, tr-rules can be used inside client side at-rules to refer styles
+ or properties define outside client rules.</li>
+ <li>Aliases cannot be specified inside client rules. Aliases are evaluated at the
+ server side, and thus we cannot pick aliases based on client rules.</li>
+ </ul>
+ Some example usages:
+ </p>
<source>
af|document {