- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Apr 2020 00:13:39 +0000
- To: public-css-archive@w3.org
General consensus was that (2) was bad because it was hacky, (1) was probably bad both due to compat and because whitespace at the beginning of an element generally shouldn't have an effect, and (3) would actually be fine (notably, we didn't feel Oriol's concern was realistic, so no circularity would ever arise). We didn't have to literally specify that (3) was achieved thru pseudo-classes; rather we could just say that UAs could magically distinguish, but note that this is amenable to pseudo-classes should we ever wish to expose it to authors.
However, a better variant of (2) was presented after the close of the meeting, which is to specify [`::marker { text-space-trim: discard-after; }`](https://drafts.csswg.org/css-text-4/#white-space-trim), which would magically eat any collapsible whitespace after the marker and before the start of the element's content. This property isn't implemented anywhere yet, but it does exactly what we want and has wider use-cases as well, so it sounds like a pretty attractive option.
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4891#issuecomment-607550890 using your GitHub account
Received on Thursday, 2 April 2020 00:13:44 UTC