- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Tue, 03 Sep 2019 02:18:21 +0000
- To: public-css-archive@w3.org
1. * Because Mozilla's implementation gets it wrong, and stops doing the thing we're asking for if there is an inline box boundary. That made me think that the "**immediately** before or after" bit could be misleading, and wanting to clarify.
* There are other places inside white-space processing (and other places in this spec) where we do call it out explicitly (and found that we needed, for reasons similar to the previous point: when we don't, implementations get it wrong). In some of these places, we also state that out-of-flow elements also don't make a difference.
2. If it's clear that we're operating on the box tree, we may not need to say anything about `display:none`. But is it clear?
That said, I agree this applies to everything in this section, so instead of adding a clarification to each statement every time we notice a browser doing it wrong, we should go with a generic statement. How about adding something like this to 4.1:
> For the purpose of operations described in this section, any intervening inline box boundaries are ignored when considering whether characters are next to each other, at the beginning or end of the line, or similar considerations.
Should we say something about out of flow elements? In most of section 4.1, it seems that they should be ignored as well, although I am not so sure for the Segment Break Transformation Rules.
--
GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4259#issuecomment-527278337 using your GitHub account
Received on Tuesday, 3 September 2019 02:18:23 UTC