- From: Simon Sapin <simon.sapin@exyr.org>
- Date: Sun, 21 Apr 2013 17:04:27 +0200
- To: www-style@w3.org
Hi, Here are a few comment on the Selectors 4 ED that could lead to normative changes. §6.7 "What makes attributes of type ID special is that no two such attributes can have the same value in a conformant document." What about non-conformant documents that reuse the same ID? Can ID selector ever match multiple elements, in practice? §7.3 "The fragment identifier of the document URI is stripped before matching against the link's URI; otherwise all portions of the URI are considered." Shouldn’t both fragment identifiers be stripped? Same section: "Similarly if the document's URI is not a URL, the pseudo-class does not match anything." That’s only in the functional pseudo-class case, right? By the way, what’s the difference between URI and URL? (Definition needed, preferably by reference.) How are URIs parsed? Does http://w3.org:80/ match http://w3.org/ ? I suggest referring to the WHATWG URL standard for parsing, and use "has a relative scheme"[1] instead of "URI that is an URL". [1] http://url.spec.whatwg.org/#relative-scheme §8.1 "User agents not that do not support interactive media do not have to support this pseudo-class." What does it mean to not support a pseudo-class? Parse as invalid (and invalidate the whole selector list) or parse as a valid selector that doesn’t match anything? cssselect and WeasyPrint currently do the latter. §12.7 Should combinators inside :nth-match() and :nth-last-match() only be allowed in the Complete profile, as for :matches()? -- Simon Sapin
Received on Sunday, 21 April 2013 15:04:50 UTC