- From: Giovanni Campagna <scampa.giovanni@gmail.com>
- Date: Sun, 10 May 2009 19:34:59 +0200
- To: Alexis Deveria <adeveria@gmail.com>
- Cc: www-style@w3.org
2009/5/7 Alexis Deveria <adeveria@gmail.com>: > Back with another question... > > [...] > > > ...it becomes less clear what the user agent should do. Since #nav is > a child of both body and #content, and both suggest the element is > flowed into their "a" slots, should it go into the #content template > (which is the nearest parent template element) or in the body template > (which is the latest rule to include the "a" slot) ?. Or are > template-positioned elements required to be defined after the template > element? This appears to be the case in all the spec examples, but I > don't see any wording that indicates that it is required. Cascading is on another level. First you find the computed values for every property in every element, then you start laying out. At that point, the order of rules (or their selector, !important or provenience) is lost. > Thanks, > > Alexis > > [1] http://www.w3.org/TR/2009/WD-css3-layout-20090402/#position0 > (somewhere under here) > >
Received on Sunday, 10 May 2009 17:35:40 UTC