Re: [whatwg/dom] Details missing on (lack of) namespace support in Element.match (#458)

Full namespace support is not what this issue is about. I might file a separate issue for that. So far I managed to work without Element.matches at all. I came across it in ProseMirror. In [WebODF](http://webodf.org/demo/), we use CSS namespaces via dynamically generated CSS stylesheets. This works fine, but has global impact (CSS via <script/> is still global right?).

But this issue is about adding the word 'prefixes' and saying whether or not there is a default namespace since that affects the outcome of '*|html'. Current browser practice is that no default namespace has been declared. Probably that should be made explicit.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/458#issuecomment-300743714