- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Fri, 21 Mar 2014 10:58:26 -0700
- To: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
- Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, www-style list <www-style@w3.org>
On Fri, Mar 21, 2014 at 10:49 AM, Daniel Glazman <daniel.glazman@disruptive-innovations.com> wrote: > On 21/03/14 17:47, Bjoern Hoehrmann wrote: >> * Tab Atkins Jr. wrote: >>> I agree. Can we just change this rule? It's not like namespace usage >>> in stylesheets is common, or even rare (I'd probably use the term >>> "almost non-existent"). It's probably fine to switch the behavior to >>> just making them not match. >> >> I think this needs to be context-specific; the behavior is probably fine >> for style sheets, but when selectors are used in APIs, selectors with >> namespace prefixes that have not been declared are likely better off if >> they throw an exception. > > Agreed. Individual contexts can do that without any cooperation on our part. We can remove the invalidity in general, and Selectors API can just define that the presence of a namespaced type or attribute selector is a syntax error. ~TJ
Received on Friday, 21 March 2014 17:59:27 UTC