W3C home > Mailing lists > Public > www-style@w3.org > March 2014

Re: [cssom] CSSNamespaceRule

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 21 Mar 2014 08:42:52 -0700
Message-ID: <CAAWBYDBrVT+XZXT0mMETYa_8mRQiRab0shSxJ2OnN07jxYMk4A@mail.gmail.com>
To: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
Cc: www-style list <www-style@w3.org>
On Fri, Mar 21, 2014 at 1:55 AM, Daniel Glazman
<daniel.glazman@disruptive-innovations.com> wrote:
> As the original author and editor of Selectors 3, I should have
> detected this before, my bad. This behaviour specified by Selectors 3
> was a mistake. A style rule containing an unrecognized namespace in a
> type selector or attribute selector should just never match, but not be
> invalid. I understand it will keep in the OM rules that never match but
> the impact seems low: most documents relying on namespaces in selectors
> will include namespace declarations or the corresponding styles won't
> work at all and the web designer will see it. It's like having a
> namespace declaration and style rules with that namespace in a
> stylesheet but no element from that namespace in the document. We have
> to deal with them in the style engine, they never match, they cost
> some cycles. Author's responsibility.

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.

~TJ
Received on Friday, 21 March 2014 16:36:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:41 UTC