541672 - Implement a version of querySelector and querySelectorAll that is namespace aware

Status: RESOLVED WONTFIX

(Core :: DOM: Core & HTML, enhancement, P5)

Description

[Robert Longson [:longsonr]]

Should only return elements that match and are in the supplied namespace too.

Comment 1

[Robert Longson [:longsonr]]

Or alternatively we could have something that returns elements in the same namespace as the node you are calling this method on.

Comment 2

[Olli Pettay [:smaug][[e-mail]]]

Could query selector allow CSS' @namespace declaration?

Comment 3

[Boris Zbarsky [:bzbarsky]]

We could just restore my original code, which allowed a namespace resolver callback, right?  Just make sure it's not callable from web script.

Comment 4

[Robert Longson [:longsonr]]

No longer required for bug 329212

Comment 5

[Kris Maglione [:kmag]]

I'd be in favor of allowing a namespace resolver callback (similar to document.evaluate), but I don't see why it shouldn't be callable from content scripts.

Comment 6

[Boris Zbarsky [:bzbarsky]]

> but I don't see why it shouldn't be callable from content scripts.

So as not to poison the well for when the spec version is updated to do namespaces (almost certainly using a different syntax and whatnot than what we'd do in the meantime).

Comment 7

[Kris Maglione [:kmag]]

The way I see it, the spec almost always arises from some browser implementing something and that implementation becoming popular rather than the other way around. In any case, I don't especially like the idea of offering slightly different interfaces to content and chrome, nor would I be much happier to break the interface for chrome consumers than for content consumers if it has to be updated for the spec. If that's to be the case I'd much rather have something like mozQuerySelector available to both.

Comment 8

[William J. Edney]

I'd also vote for a mozQuerySelector available to both. It's frustrating that with the advent of IE9, all major platforms are now X(HT)ML user agents, supporting CSS3 namespaces, but you can't query using namespaces. I know that this is a limitation of the current W3C spec, but it'd be nice to have some form of native implementation to start trying for solutions here.

Comment 9

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.

Comment 10

[Robert Longson [:longsonr]]

I guess we're not going to do this since we haven't seen the need in the last 11 years.