W3C home > Mailing lists > Public > public-css-archive@w3.org > January 2021

Re: [csswg-drafts] [selectors] Define how "legacy aliases" work on selectors. (#5847)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 13 Jan 2021 17:08:46 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-759590001-1610557725-sysbot+gh@w3.org>
The CSS Working Group just discussed `[selectors] Define how "legacy aliases" work on selectors.`, and agreed to the following:

* `RESOLVED: convert at parse time`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [selectors] Define how "legacy aliases" work on selectors.<br>
&lt;dael> Rossen_: Is emilio on?<br>
&lt;dael> [waiting for emilio to join]<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/5847<br>
&lt;dael> emilio: Have a couple places where we define a selector where for legacy reason can be impl as alias but no definion of that.<br>
&lt;dael> emilio: Came up as I did compat work on other pseudo classes.<br>
&lt;dael> emilio: Compat can change what needs to be done but seems as if we should have guidance on how this should work<br>
&lt;dael> emilio: afaict two options are keep zeroizing the non-standard or convert them at parse time<br>
&lt;dael> emilio: Some inconsistencies in Blink. Gecko should always turn it intot he stanrdard at parse time. I think that's what we do for properties in general<br>
&lt;dael> Rossen_: Prop is align more closely with converting at parse time<br>
&lt;dael> Rossen_: Questions or should we resolve on that?<br>
&lt;dael> Rossen_: I'll take silence as no<br>
&lt;dael> Rossen_: No comments or objections?<br>
&lt;dael> Rossen_: I see support in GH from TabAtkins<br>
&lt;dael> RESOLVED: convert at parse time<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5847#issuecomment-759590001 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 13 January 2021 17:08:48 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:25 UTC