Bug #78877 [Opn]: LIBXML_PARSEHUGE output formatting
| From: | kieran at miami-nice dot co dot uk | Date: | Thu, 28 Nov 2019 15:57:25 +0000 |
| Subject: | Bug #78877 [Opn]: LIBXML_PARSEHUGE output formatting | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-223917@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=78877&edit=1
ID: 78877
User updated by: kieran at miami-nice dot co dot uk
Reported by: kieran at miami-nice dot co dot uk
Summary: LIBXML_PARSEHUGE output formatting
Status: Open
Type: Bug
Package: DOM XML related
PHP Version: 7.3.12
Block user comment: N
Private report: N
New Comment:
> it's about the different output with and without LIBXML_PARSEHUGE
Correct
Previous Comments:
------------------------------------------------------------------------
[2019-11-28 14:12:42] cmb@php.net
Ah, I thought it was about the differences between PHP < 7.3.0 and
>= 7.3.0! If it's about the different output with and without
LIBXML_PARSEHUGE, it can't be related to the mentioned bug fixes,
since these have only been applied to PHP 7.3+.
------------------------------------------------------------------------
[2019-11-28 13:55:48] kieran at miami-nice dot co dot uk
Description:
------------
I added LIBXML_PARSEHUGE to a rather large test suite and it instantly changed the formatting of a
lot of tests.
I thought it could be related to https://bugs.php.net/bug.php?id=76738 but cmb
linked me to https://bugs.php.net/bug.php?id=76738
I think it's a possible PHP bug because the output doesn't seem to change on Python https://repl.it/repls/InfantileMiserableDemo
but I'm not sure.
LIBXML_PARSEHUGE actually looks the more correct output, as it matches the input string.
Test script:
---------------
https://3v4l.org/d4RSn
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=78877&edit=1