- From: SelenIT via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 Jan 2017 12:57:38 +0000
- To: public-css-archive@w3.org
I don't see much need in renaming. Are authors really more familiar with Regions (which the Chrome team even [doesn't plan to support](https://www.chromestatus.com/feature/5655612935372800)) than with phrases like "absolutely positioned elements _are removed from the flow"_ (often used in many CSS articles for beginners) or with the "Flow content" concept from HTML5? Existing implementations also count against the renaming, IMHO. But if the renaming is absolutely necessary, I suppose it's important to highlight that the BFC-establishing element is 'self-contained', that nothing inside it overlaps anything outside it (leaving out special cases like negative margins). What about `display: enclosed-block`, or `separate-block`, or just `new-block` (since it establishes the _new_ BFC)? -- GitHub Notification of comment by SelenIT Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/964#issuecomment-274481540 using your GitHub account
Received on Monday, 23 January 2017 12:57:45 UTC