[Webkit-unassigned] [Bug 14101] XSLTProcessor does not accept Nodes as parameter values

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=14101


Michael Slama <michael.slama at hp.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |michael.slama at hp.com




--- Comment #15 from Michael Slama <michael.slama at hp.com>  2012-01-19 09:56:52 PST ---
(In reply to comment #13)
> The passing of nodes as parameter values is fully supported in the latest versions of:
> Internet Explorer
> Firefox
> Opera

We (HP ESSN) are being asked to add support for Chrome in upcoming enterprise Web application releases due to Chrome's rise in adoption, and this limitation is preventing that for some of our teams. 

We have been successfully using IE and Firefox to pass node-sets as parameters since late 2005 when the good folks at Mozilla (esp. Peter Van Der Beken) fixed their XSLT library to support node-set parameters in version 1.50. See https://bugzilla.mozilla.org/show_bug.cgi?id=248025 (comment #15 is referring to me because I was building Mozilla to test the fix).

Is there a way to move this issue to a higher priority, or perhaps request outside help to get it addressed? This is a critical requirement for our XSLT-heavy Web applications because we need to pass entire documents to the XSLT processor as parameters.

We have a large customer base and the addition of Chrome support within our organization would boost adoption even further IMO.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.