This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6290 - [selectors-api2] Reconsider The Inclusion a Namespace Resolution Mechanism
Summary: [selectors-api2] Reconsider The Inclusion a Namespace Resolution Mechanism
Status: RESOLVED WONTFIX
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Selectors API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 enhancement
Target Milestone: ---
Assignee: Lachlan Hunt
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-09 13:57 UTC by Lachlan Hunt
Modified: 2009-11-26 12:08 UTC (History)
2 users (show)

See Also:

Attachments

Description Lachlan Hunt 2008-12-09 13:57:11 UTC 
Re-evaluate the need for namespace resolution, considering the use cases.  As it is expected that SVG will be available for use within HTML, potential use cases for namespace prefix resolution may become more significant.  The SVG WG is strongly demanding this feature; need to obtain clear use cases and problem statments from them and evaluate their significance.

Need to evaluate the demand for this feature among authors:
* Find out whether or not JS library implementations support namespace resolution.
* Investigate use of alternative mechanisms like DOM 3 XPath.

Also need to investigate alternative technical solutions over the preiously used NSResolver function.
Comment 1 Lachlan Hunt 2009-11-26 12:08:54 UTC 
Developing a solution for this will require significant time and effort, and be very costly.  There is currently insufficient justification for pursuing this, and as such, I am resolving this WONTFIX.