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

Re: [csswg-drafts] [css-pseudo-4] Should Element.pseudo("unknown") be an error or return null? (#3603)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 17 Apr 2019 16:09:17 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-484156093-1555517356-sysbot+gh@w3.org>
The CSS Working Group just discussed `Should Element.pseudo("unknown") be an error or return null?`, and agreed to the following:

* `RESOLVED: Do a css parse on parameter for element.pseudo()`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Should Element.pseudo("unknown") be an error or return null?<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/3603#issuecomment-467363388<br>
&lt;dael> astearns: There was additional conversation after we resolved. Is fantasai or TabAtkins on?<br>
&lt;dael> TabAtkins: Yes<br>
&lt;dael> TabAtkins: Question came up from Anna. Import is exactly how argument should be parsed. Direct string match or full css parse so you get escapes and that business?<br>
&lt;dael> TabAtkins: I usually prefer direct string but I believe this function will be extended to handle other pseudo elements with arguments. AS soon as you get past a single name string compare falls down. When we have css parsing there we shouldn't do custom<br>
&lt;dael> TabAtkins: I propose we do a css parse on the string and match against grammar of supported elements<br>
&lt;dael> astearns: Any discussion? Objections?<br>
&lt;dael> RESOLVED: Do a css parse on parameter for element.pseudo()<br>
&lt;dbaron> ok, I'm on now -- the problem seems to be that WebEx doesn't work in Nightly Firefox any more (across 2 machines) -- but it works in Chrome<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3603#issuecomment-484156093 using your GitHub account
Received on Wednesday, 17 April 2019 16:09:19 UTC

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