Closed Bug 540359 Opened 15 years ago Closed 14 years ago

XPathResult not exposed to Jetpacks

Categories

(Mozilla Labs :: Jetpack Prototype, enhancement)

Product:
Mozilla Labs
Component:
Jetpack Prototype
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: melkor, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
Build Identifier: 

To use document.evaluate effectively you need XPathResult.
Jetpack does not expose this global which makes using document.evaluate less attractive.

I'm failing to see the down side to implementing this; it only requires the addition of one line of code in 'content\js\jetpack-environment.js' around line #126.

"XPathResult": XPathResult,

Reproducible: Always
OS: Windows 7 → All
Hardware: x86 → All
Summary: Jetpack does not expose the global XPathResult → XPathResult not exposed to Jetpacks
We will be monitoring all these issues after the rebooted Jetpack code base is released in the first week of March to ensure their causes are not duplicated. Many of the bugs/issues with the prototype version of Jetpack will be made irrelevant given the structure of the new SDK.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.