- From: SelenIT via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Jul 2017 14:35:27 +0000
- To: public-css-archive@w3.org
IMO, the remaining part of the 2nd bullet point implies that any anonymous fixup doesn't occur after recursion (the formatting step comes immediately after reparenting). In general, it seems that the spec intents to assure that in any situation the run-in box ends up being the first inline descendant of the block (after `::marker`, if it's present and is inline). So the logic is "if there is a block right after `run-in`, put it there, if not, create it and put it there". But it misses the situation where `run-in` _is already inside a block in the correct position,_ I suppose there should be one more bullet point before point 2, like "If a run-in sequence is direct children of a block box [...], then do nothing". So I'd expect both your examples to be rendered in the same line. I don't see any need in anonymous wrapper creation in the first example. Usually, line breaks don't occur in CSS because of literally nothing. -- GitHub Notification of comment by SelenIT Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1640#issuecomment-317017881 using your GitHub account
Received on Friday, 21 July 2017 14:35:30 UTC