W3C home > Mailing lists > Public > public-css-archive@w3.org > April 2017

Re: [csswg-drafts] [css-writing-modes] Question about implementability of the "different writing-mode value than its containing block" section of the spec

From: Boris Zbarsky via GitHub <sysbot+gh@w3.org>
Date: Wed, 19 Apr 2017 03:14:25 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-295055793-1492571663-sysbot+gh@w3.org>
> "Parent box" is the parent in the box tree, as usual

Where is this concept defined?  I think the use of "as usual" here is a bit odd, given again that I don't think this stuff is defined anywhere.

> This is fine; this clause doesn't apply to out-of-flows, it only applies to in-flow display: inline boxes.

Why?  What prevents CSS from adding a feature that makes something out-of-flow without blockifying?

If the intent is that this is only applied to in-flow inlines, that needs to be pretty explicitly stated.

> There's no need for the display value to change here

Ah, I see.  "flow" could mean "acts like a block on the inside" or it could mean "acts like an inline on the inside".  That's ... pretty odd for a inner display value behavior.  :(  I would have expected that things that act like inlines on the inside and things that act like blocks on the inside would have different display-inside values....  Anyway, this is getting a bit off-topic.  I filed https://github.com/w3c/csswg-drafts/issues/1246 on the other issue I see with this stuff that is even more off-topic for this discussion...

I would like to reiterate that I would like computed values to be defined without reference to the box tree.

-- 
GitHub Notification of comment by bzbarsky
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1212#issuecomment-295055793 using your GitHub account
Received on Wednesday, 19 April 2017 03:14:31 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:11 UTC