W3C home > Mailing lists > Public > public-css-archive@w3.org > April 2019

Re: [csswg-drafts] [css-lists] Interaction of ::marker with other pseudo-elements. (#3826)

From: Mats Palmgren via GitHub <sysbot+gh@w3.org>
Date: Sat, 20 Apr 2019 18:25:49 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-485149112-1555784748-sysbot+gh@w3.org>
Right, as I've said [before](https://github.com/w3c/csswg-drafts/issues/3809#issuecomment-480862184), I'm opposed to introducing arbitrary unnecessary styling restrictions on `::marker`. It's much simpler for everyone (spec authors, implementors, authors) if it behaves the same as `::before/::after`.

There are still some uncertainty about the exact layout model for outside markers (#3771), so feel free to add an ISSUE note about that in the spec, but my gut feeling is that we can allow pretty much  all of CSS on those too. We definitely should allow `display:none` to suppress the box.

I don't see a reason treat `content`/non-`content` markers differently. (Gecko _currently_ has two code paths, where the non-`content` legacy code path has some restrictions, but I consider that to be a temporary implementation bug that we'll fix soon.) Given that `::marker` is relatively new, I don't see any web-compat concerns that could justify introducing styling restrictions.

GitHub Notification of comment by MatsPalmgren
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3826#issuecomment-485149112 using your GitHub account
Received on Saturday, 20 April 2019 18:25:50 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:46 UTC