- From: Sebastian Zartner <sebastianzartner@gmx.de>
- Date: Fri, 01 Jun 2012 13:59:22 +0200
- To: Simon Sapin <simon.sapin@kozea.fr>
- Cc: jackalmage@gmail.com, www-style@w3.org, florianr@opera.com, sylvaing@microsoft.com, shans@google.com, fremycompany_pub@yahoo.fr
>> As I understand the current model and pointed out earlier the current >> concept is limited to the element tree. People won't be able to put >> something into a variable that is not inside of it, i.e. @-rules >> defining font faces, counter styles, page styles etc. Please let me >> know if I am wrong in this point. > > I think that @page could contain variables. > > Many @-rules like @font-face or @counter-style contain *descriptors*. > Descriptors have the same "name: value;" syntax as properties, but > that’s it. They can not have !important and are not part of the cascade. That's the point. People might want to have variables available everywhere, not just in the cascade. > @page however contains real properties, as do margin rules inside > @page. > In fact, in recent css3-page drafts, @page inherits from the root > element and margin boxes inherit from @page. I have to say that this is confusing. I believe @-rules shouldn't be influenced by the cascade. But that's another topic. > In their current form, CSS variables can be used in any property values > but not in descriptors. The spec probably should mention that. Yes, it should definitely mention that. As François already telling in several posts, it will be hard for people to understand and accept what's the concept of CSS variables. So at least the spec should be clear about such things. Sebastian -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
Received on Friday, 1 June 2012 11:59:54 UTC