- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Oct 2020 16:48:23 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Existence of ::marker::marker`, and agreed to the following: * `RESOLVED: ::marker::marker is invalid` * `RESOLVED: accept proposal above` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: Existence of ::marker::marker<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/1793<br> <fantasai> https://github.com/w3c/csswg-drafts/issues/1793#issuecomment-708072107<br> <RRSAgent> I have made the request to generate https://www.w3.org/2020/10/23-css-minutes.html fantasai<br> <florian_irc> scribenick: Florian<br> <florian_irc> fantasai: This is a follow to previous decisions on ::marker<br> <florian_irc> fantasai: we didn't want to have infinite markers<br> <florian_irc> fantasai: so you cannot have ::marker::marker<br> <florian_irc> fantasai: right now ::marker doesn't accept the display property<br> <florian_irc> fantasai: so, is ::marker::marker invalid?<br> <florian_irc> fantasai: and, in the future, if we want to allow that<br> <fantasai> s/that/display on ::marker/<br> <florian_irc> fantasai: then, do we force it to compute display so that it loses its list item<br> <florian_irc> Rossen_: so, taking things one at a time, should we allow ::marker::marker<br> <florian_irc> fantasai: I'd like to make it invalid<br> <florian_irc> TabAtkins: browsers don't support it<br> <tantek> +1 on no ::marker::marker<br> <florian_irc> oriol: implementations are behind flags, so not too relevant<br> <florian_irc> oriol: in firefox, no nested pseudos<br> <florian_irc> oriol: in chrome ::before::marker and ::after::marker work, but ::marker::marker doesn't<br> <florian_irc> oriol: but then the styles don't quite work anyway<br> <florian_irc> oriol: so I'd prefer to keep it invalid<br> <florian_irc> Rossen_: any objection to ::marker::marker being invalid<br> <florian_irc> RESOLVED: ::marker::marker is invalid<br> <florian_irc> fantasai: in the future, when display applies to ::marker, should it lose the list itemness<br> <florian_irc> oriol: seems reasonable<br> <florian_irc> Rossen_: me too<br> <florian_irc> RESOLVED: accept proposal above<br> <TabAtkins> ScribeNick: TabAtkins<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1793#issuecomment-715455489 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 October 2020 16:48:25 UTC