- Alex Vincent: XPath Generator: One little oversight...
-
One of the reasons I even thought about writing a native XPath Generator for Mozilla-based applications is a need to take a XPath for a DOM tree and translate it into a path for a DOM Inspector-like node tree. Unfortunately, as my mind has just now started wandering back towards my Verbosio application (for which I would use this XUL tree), I realized I had completely forgotten to include any functionality in the IDL or in the implementation for creating a XPath that would be friendly to this. Specifically, I wanted a XPath that looks like: /node()[5]/node()[7]/node()[11]. I didn't think about that when writing the extension, though. Fortunately, I had a lot of foresight in allowing for extensibility. So, pending reviews to land the xpathgen code (which I don't expect right away), I'll submit a new bug to to "GET_CHILD_INDEXES_ONLY". I might argue that I own the spec and I can do what I want there, but I don't buy that. I'm doing this for the community, so even when I suggest a new idea for the spec, I make sure to run it by someone else for approval. view original article
Sat, 04 Mar 2006 19:52:12 +0100 - more Planet Mozilla articles
-
- related articles found at Planet Mozilla
- Alex Vincent: Beyond clones: synchronized DOM nodes Sun, 25 Nov 2007 08:14:52 +0100
- Alex Vincent: Do you generate XPaths? (Or need to?) Fri, 13 Jan 2006 03:12:41 +0100
- Alex Vincent: Exposing XPCOM components in JavaScript, part one Sat, 11 Nov 2006 07:55:25 +0100
- Alex Vincent: Exposing XPCOM components in JavaScript, part two Mon, 13 Nov 2006 21:25:03 +0100
- Alex Vincent: Here's what ManyOne is doing (with Mozilla included) Mon, 19 Dec 2005 19:48:26 +0100
- Alex Vincent: I need a bigger desk - or a better one. Wed, 02 May 2007 06:12:47 +0200
- Alex Vincent: ManyOne: Anyone out there with plug-in development experience? Wed, 21 Jun 2006 00:41:05 +0200