On Tuesday 2010-05-04 09:37 -0700, Thierry Koblentz wrote:
> > > > display: block.
> > > > http://www.w3.org/TR/CSS21/visuren.html#dis-pos-flo
> > 
> > > That table is about "computed value", what I quoted was related to a
> > > "declaration" (at least that's the way I read it):
> > 
> > > In my rule, the float is styled with "display:inline" and I expect it
> > to be
> > > a flow Root.
> > > Is the above assumption correct or wrong?
> > 
> > The point is that you can't have something that is both floated and
> > inline.  Since your element is floated, that over-rules the
> > display:inline and it has display: block in spite of you.
> > 
> > So it would be able to be a flow root since it's display isn't inline.
> 
> As I said earlier, my issue is about how it is *worded*, not about how
> things work.
> One more time:
> 
> "Note that an element with 'display: inline' therefore cannot be a flow
> Root..."
> 
> English is not my native language so it may be the problem here, but the way
> I read the above is that if you apply "display:inline" to an element, it
> cannot be a flow Root. 
> Forget the fact that it is "over-ruled", that the computed value is
> something else, just look at that sentence and tells me what should be
> people's expectation.

The sentence should perhaps refer to the computed value being
'display: inline'.  But, in general, any part of the CSS specs
that's describing the effects of properties is talking about the
effects of their computed values, unless explicitly stated
otherwise.

-David

-- 
L. David Baron                                 http://dbaron.org/
Mozilla Corporation                       http://www.mozilla.com/
______________________________________________________________________
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Reply via email to