DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=42021>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=42021 Summary: XPathResult not exposed to JavaScript Product: Batik Version: 1.7 Platform: Other URL: http://home.arcor.de/martin.honnen/batikBugs/XPath/XPath ResultTest1.svg OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Scripting AssignedTo: batik-dev@xmlgraphics.apache.org ReportedBy: [EMAIL PROTECTED] 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. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
