User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030204 All my javascript code using the XPathEvaluator class is broken in the last few nightly builts. I couldn't find documentation about changes in the API, so i guess this is a bug. Reproducible: Always Steps to Reproduce: 1. javascript:new XPathEvaluator(); Actual Results: Error: XPathEvaluator is not defined Source File: javascript:new XPathEvaluator(); Line: 1 Expected Results: Either create the XPathEvaluator object or if that class is deprecated or has become a singleton, tell me so.

Probably a duplicate of bug 191916.

reporter: could you try if this is fixed in the latests nightlies?

This is not fixed in the latest nightly build/1.3b: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210 However, the bug is not reproducible in the way i mentioned earlier. javascript:new XPathEvaluator(); in the address bar does work, but the attached script: <script> new XPathEvaluator(); </script> does not. Also: javascript:XPathEvaluator.prototype.constructor results in an error: Error: XPathEvaluator.prototype has no properties Source File: javascript:XPathEvaluator.prototype.constructor Line: 1 While: javascript:DOMParser.prototype shows: [xpconnect wrapped native prototype]

Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.3b) Gecko/20030210 tested on my 1.3b talkback install, worksforme. could you try a fresh install (prune previous installs good, too) on a fresh profile?

this works for me too on a 1.3b-release on Win98SE. Laurens: Did you test this on a release build?

I've tested this in 1.3 Beta Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210 And the lastest nightly build: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030218 In both versions the bug is not fixed. javascript:new XPathEvaluator(); works, but the new test case I attached still generates an error.

I'm seeing this too on Win2k. My installed build is missing dom_xpath.xpt so this might be a packaging problem.

The checkin for bug 186703 removed dom_xpath.xpt from packages-win but didn't add it anywhere else, so DOM Level 3 XPath is completely broken on Windows. I have no idea where we need to re-add it, I suppose packages-win since that's where transformiix.dll is.

Sorry, peterv. I'll add it back in and recheck the packages-win patch file list from bug 186703 to see if there are any other files in the same situation.

Comment on attachment 114910 [details] [diff] [review] patch v1.0 dom_xpath.xpt is added to the [browser] section of packages-win

Isn't XPath support a basic Gecko-like thing? the dom_* naming of the .xpt seems to hint at this. If that's the case this might better go in the GRE rather than in the browser application.

Comment on attachment 114910 [details] [diff] [review] patch v1.0 r/sr=jst

Comment on attachment 114910 [details] [diff] [review] patch v1.0 sr=dveditz given jst's blessing for the browser.xpi placement

if transformiix is included in the GRE you should include dom_xpath.xpi, if transformiix is not included there is very little point in including dom_xpath.xpi.

patch checked in.

Comment on attachment 114910 [details] [diff] [review] patch v1.0 safe packaging fix, a=dveditz

Thanks guys!