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: fantasai via GitHub <sysbot+gh@w3.org>
Date: Wed, 19 Apr 2017 02:42:49 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-295047183-1492569767-sysbot+gh@w3.org>
"Parent box" is the parent in the box tree, as usual. It's not necessarily the containing block. So for a float inside a SPAN, it's the SPAN, not the P that contains the SPAN. This is fine; this clause doesn't apply to out-of-flows, it only applies to in-flow `display: inline` boxes.

> Um... I don't follow. If I absolutely position a thing that's display:inline, its inner display had better change. That's how it's been specced forever, how it's implemented in all browsers, and websites depend on it. Am I just missing something about the change you just made to css-display and how it relates to this case?

There are a number of cases (e.g. `overflow`, `float`, `position`) where the inner display type behaves as `flow-root`, even when its `display` value is `flow`. This is called out in https://www.w3.org/TR/css-display-3/#valdef-display-flow There's no need for the `display` value to change here, hence I deleted the sentence that implied that.

GitHub Notification of comment by fantasai
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1212#issuecomment-295047183 using your GitHub account
Received on Wednesday, 19 April 2017 02:42:55 UTC

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