Bug #49820 [Opn->Fbk]: XSLTProcessor returns Error at xsl:variable with comment inside
Edit report at https://bugs.php.net/bug.php?id=49820&edit=1
ID: 49820
Updated by: mike@php.net
Reported by: felixsigl at gmail dot com
Summary: XSLTProcessor returns Error at xsl:variable with
comment inside
-Status: Open
+Status: Feedback
Type: Bug
Package: XSLT related
Operating System: Windows
PHP Version: 5.3.0
Block user comment: N
Private report: N
New Comment:
So, has this fix been released mainstream?
Previous Comments:
------------------------------------------------------------------------
[2010-02-10 01:49:43] wellnhofer at aevum dot de
The following commit fixes this bug in libxslt
http://github.com/nwellnhof/libxslt/commit/a73df1cbb57f0e250b9815c6b8ed72bd52cb4f72
------------------------------------------------------------------------
[2010-02-10 01:04:24] wellnhofer at aevum dot de
I had a deeper look at the XSLT spec and it seems the both cases are bugs in libxslt.
------------------------------------------------------------------------
[2010-02-09 23:50:22] wellnhofer at aevum dot de
The second example without whitespace is a bug in libxslt. It's a pretty minor issue, but maybe
I'll fix it in libxslt.
Nick
------------------------------------------------------------------------
[2009-10-10 14:15:14] felixsigl at gmail dot com
Hi,
i have tried:
<xsl:variable select="1"
name="var"><!--comment--></xsl:variable>
thus no whitspace
but the same error: XSLT-variable: The must be no child nodes, since the attribute
'select' was specified.
------------------------------------------------------------------------
[2009-10-10 11:54:46] Sjoerd@php.net
Thank you for your bug report.
Can you also reproduce it if you remove the whitespace between the variable tags? In your example,
the variable element would have a text child node with some whitespace in it. Technically, this is
not allowed since the variable tag should have no content at all.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=49820
--
Edit this bug report at https://bugs.php.net/bug.php?id=49820&edit=1
Thread (8 messages)