[csswg-drafts] [css-conditional-3] define whether/how it matters if namespace prefixes are declared

• From: L. David Baron via GitHub <sysbot+gh@w3.org>
• Date: Wed, 17 Oct 2018 17:25:05 +0000
• To: public-css-archive@w3.org
• Message-ID: <issues.opened-371185102-1539797104-sysbot+gh@w3.org>

dbaron has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-conditional-3] define whether/how it matters if namespace prefixes are declared ==
One issue that came up in #3207 (noticed by @heycam while reviewing code from @emilio) is that the spec should define to what extent namespace prefixes are required to be declared.  In particular, how do:

```css
@supports (content: attr(n|href)) {
}
```

```js
CSS.supports("content", "attr(n|href)");
```

```js
CSS.supports("(content: attr(n|href))");
```

depend on whether the namespace prefix `n` has been declared?  Do they:
* treat all namespace prefixes as already declared?
* treat all namespace prefixes as undeclared (invalid)?
* depend on a set of namespace declarations (which set, exactly)?

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3220 using your GitHub account

Received on Wednesday, 17 October 2018 17:25:06 UTC