[BATIK-706] XPathResult not exposed to JavaScript

• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Affects Version/s: 1.7
• Component/s: Scripting
• Environment: Operating System: other; Platform: Other; URL: http://home.arcor.de/martin.honnen/batikBugs/XPath/XPathResultTest1.svg
• Assignee: Batik Developer's Mailing list
• Reporter: Martin Honnen
• Created: 02/Apr/07 08:50
• Updated: 02/Apr/07 16:50
• Resolved: 02/Apr/07 16:50

Description

With the Mozilla and Opera W3C DOM Level 3 XPath API implementation the
XPathResult object is exposed to script so that script can use the constants
like XPathResult.ORDERED_NODE_SNAPSHOT_TYPE. With Batik 1.7 beta this is not the
case as the test case at
<http://home.arcor.de/martin.honnen/batikBugs/XPath/XPathResultTest1.svg>
shows, it gives an error "XPathResult is not defined" with Batik while it
displays "3" with Mozilla or with Opera.
The ECMAScript bindings in the W3C DOM specifications are unfortunately not too
clear on how things need to be exposed to script but
<http://www.w3.org/TR/DOM-Level-3-XPath/ecma-script-binding.html> speaks about
"Properties of the XPathResult Constructor function:
XPathResult.ANY_TYPE
The value of the constant XPathResult.ANY_TYPE is 0."
so based on that one can infer that a function XPathResult with properties like
ANY_TYPE should be exposed.