- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Mar 2020 17:19:13 +0000
- To: public-css-archive@w3.org
<details> <summary>There was some additional relevant IRC conversation at https://log.csswg.org/irc.w3.org/css/2020-03-18/#e1297586</summary> ``` # | dholbert TabAtkins, RE unioning vs. "first layout box" - note that Chrome does seem to union for a scenario of an inline element that's fragmented via explicit breaks: https://jsfiddle.net/dholbert/hpxo4g2r/ | 10:04:30 PDT # | TabAtkins dholbert: Yeah, that's all still within one layout box. | 10:06:28 PDT # | TabAtkins (we were throwing around "fragment" casually, but the spec doesn't say fragment, it's about layout boxes) | 10:06:43 PDT # | dholbert hmm, https://drafts.csswg.org/cssom-view/#css-layout-box Issue 1:"The terms CSS layout box and SVG layout box are not currently defined by CSS or SVG." :D | 10:08:21 PDT # | dholbert maybe that's part of the problem | 10:08:41 PDT # | TabAtkins lol | 10:09:24 PDT # | fantasai "fragment" is a CSS3 term, CSS2 just called them boxes... | 10:09:26 PDT # | TabAtkins yeah, css2 mixed "box" and "fragment". But if we read CSSOM-View literally, as referring to boxes, then that a-with-breaks is one box, and the a-with-div is three sibling boxes. ``` </details> -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4541#issuecomment-600759060 using your GitHub account
Received on Wednesday, 18 March 2020 17:19:15 UTC