W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2020

Re: [csswg-drafts] [css-conditional-3] define whether/how it matters if namespace prefixes are declared (#3220)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Thu, 22 Oct 2020 14:19:17 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-714527458-1603376356-sysbot+gh@w3.org>
The CSS Working Group just discussed `define whether/how it matters if namespace prefixes are declared`, and agreed to the following:

* `RESOLVED: the CSS.supports() function considers all namespaces invalid (like .querySelector() does), the @supports rule consults the stylesheet's namespace map`

<details><summary>The full IRC log of that discussion</summary>
&lt;gregwhitworth> Topic: define whether/how it matters if namespace prefixes are declared<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/3220<br>
&lt;TabAtkins> @supports (content: attr(n|href)) {<br>
&lt;TabAtkins> }<br>
&lt;gregwhitworth> TabAtkins: things that take a namespace value, such as the attr function<br>
&lt;gregwhitworth> TabAtkins: in this case if the n namespace is not declared should this supports declaration valid or not<br>
&lt;gregwhitworth> TabAtkins: emilio_ had an opinion 14 mins ago<br>
&lt;gregwhitworth> TabAtkins: only consider it valid when the namespace has been declared<br>
&lt;gregwhitworth> TabAtkins: I don't like namespaces so I don't care<br>
&lt;chris> ok someone else take this, I will rejoin<br>
&lt;TabAtkins> document.querySelector("a|b")<br>
&lt;gregwhitworth> TabAtkins: emilio_ also pointed out ^ (example) does check the namespace map<br>
&lt;fantasai> chris points out it's a corner case<br>
&lt;gregwhitworth> TabAtkins: thus we should probably stay consistent with APIs that care about namepaces<br>
&lt;gregwhitworth> TabAtkins: it shouldn't matter, as chris said it's a corner case<br>
&lt;gregwhitworth> fremy: one thing - you have to re-verify the at-supports<br>
&lt;gregwhitworth> fantasai: no - that's not true, namespaces are per file<br>
&lt;gregwhitworth> fremy: how does that work in queryselector?<br>
&lt;fantasai> https://www.w3.org/TR/css-namespaces/#scope<br>
&lt;gregwhitworth> rune: yeah I don't get how query selector will work<br>
&lt;emilio_> It does _not_ check the ns map, there's no ns map to check<br>
&lt;gregwhitworth> TabAtkins: at-supports should query the stylesheets namespace value<br>
&lt;emilio_> But yeah @supports could<br>
&lt;gregwhitworth> TabAtkins: so, I'm fine with emilio_ opinion<br>
&lt;gregwhitworth> fantasai: I'm in favor of what's easy to implement as well<br>
&lt;TabAtkins> proposed resolution: the CSS.supports() function considers all namespaces invalid (like .querySelector() does), the @supports rule consults the stylesheet's namespace map<br>
&lt;gregwhitworth> chris: I just want it defined<br>
&lt;gregwhitworth> astearns: any objections<br>
&lt;gregwhitworth> the CSS.supports() function considers all namespaces invalid (like .querySelector() does), the @supports rule consults the stylesheet's namespace map<br>
&lt;gregwhitworth> RESOLVED: the CSS.supports() function considers all namespaces invalid (like .querySelector() does), the @supports rule consults the stylesheet's namespace map<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 22 October 2020 14:19:20 UTC

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