It looks like people are planning to mutate the namespace stuff in
Selectors API. At this point, I think we have the following choices:
1) Forget about namespaces for the initial implementation and just not
allow queries that actually involve resolving a namespace.
2) Ship the NSResolver implementation we already have written, which
corresponds to the published spec draft.
3) Pick either the proposal to reuse @namespace described in
http://dev.w3.org/2006/webapi/selectors-api/#nodeselector or
the proposal to use a new object described in
http://lists.w3.org/Archives/Public/public-webapps/2008JulSep/0124.html
and implement it, then push for adopting it as a standard.
The minimal-work approach is probably 2. 1 takes a bit more work, and 3
would require yet more work. Probably not more than a day's worth.
So I guess the question is which we think is best for the web, since at
this point we could do any of the three for 1.9.1, I think.
-Boris
_______________________________________________
dev-tech-layout mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-layout
