Recent changes to bugs

#193 Patch for PHP 8

2025-11-06T21:02:52.963000Z

DELETE THIS BUG REPORT

#199 Incorrect handling of
tags next to line breaks

2025-11-06T21:02:49.238000Z

DELETE THIS BUG REPORT

#201 Never return false on documents

2025-11-06T21:02:45.373000Z

DELETE THIS BUG REPORT

#203 Always tell user where he expected non-existing element

2025-11-06T21:02:42.560000Z

DELETE THIS BUG REPORT

#204 Convenience function for getting first element

2025-11-06T21:02:39.286000Z

DELETE THIS BUG REPORT

#210 Find first child element like CSS does not respect order

2024-11-30T21:30:48.382000Z

Sorry, wrong goal. Close this.
The correct answer it's here:
https://sourceforge.net/p/simplehtmldom/support-requests/63/

Find first child element like CSS does not respect order

2024-11-30T10:10:24.533000Z

Find first child element like CSS does not respect order
I'm talking about '>' selector.
You can see from the following code like CSS rules are not respected.

...
$section = $html->find('div.main',0);
$div = $main->find('div')[0];

//then removing something like (just for explain)
//foreach ($div->find('sup') as $sup) { $sup->outertext = ''; }

/* OVER A RESULT LIKE THIS
<div>
    <section>
        <section>A</section>
    </section>
    <section>B</section>
</div>
*/

//here the problem
striptags ( $div->find('> section')[0] ) //this gives back A
striptags ( $div->find('> section')[1] ) //this gives back A TOO!!

I love PHP Simple HTML DOM Parser, but this is a big bug.
Please kill the bug 😎🐞🦋🐝🐜 🔫🔫🔫

Decoding HTML entities corrupts text in HTML

2024-11-21T17:58:00.025000Z

Processing texts with the html_entity_decode added in feature #52 corrupts the text in many cases. This is an example:

$html = '<p>Use &lt; or &gt; symbols</p>';
var_dump($html);
$htmlDocument = new HtmlDocument();
$htmlDom = $htmlDocument->load($html);
$html = $htmlDom->save();
var_dump($html);
$htmlDom = $htmlDocument->load($html);
$html = $htmlDom->save();
var_dump($html);

Output:

string(31) "<p>Use &lt; or &gt; symbols</p>"
string(25) "<p>Use < or > symbols</p>"
string(23) "<p>Use <or> symbols</p>"

In fact, if the text contains any properly encoded HTML code to display on the page, it will be replaced by the tags after saving and cannot be displayed on the page anymore. It makes the Simple HTML DOM library absolutely unsafe for use. Decoding HTML entities should be removed or at least disabled by default.

#208 $node->find() finds element next to $node

2023-10-17T05:09:45.871000Z

This bug persists even with well-formed HTML with single root element:

<?php

$s_htm = <<<EOT
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<body>
  <div class="c1"></div>
  <div class="c2"></div>
</body>
</html>
EOT;
...

$node->find() finds element next to $node

2023-10-17T01:35:03.545000Z

<?php

$s_htm = '<div class="c1"></div><div class="c2"></div>';

include_once('HtmlDocument.php');
use simplehtmldom\HtmlDocument;
$o_doc = new HtmlDocument();
$o_doc->load($s_htm);
$o_elm1 = $o_doc->find('.c1',0);
echo("an element of class='".($o_elm1->getAttribute('class'))."' was found => ok\n");
$o_elm2 = $o_elm1->find('*',0);
if(NULL === $o_elm2) {
  echo("no sub-elements found within div.c1 => ok\n");
} elseif(is_object($o_elm2)) {
  echo("a sub-element of class='".($o_elm2->getAttribute('class'))."' was found within div.c1 => bug\n");
}

outputs:

an element of class='c1' was found => ok
a sub-element of class='c2' was found within div.c1 => bug

Expected output:

element of class='c1' was found => ok
no sub-elements found within div.c1 => ok

Recent changes to bugs

#193 Patch for PHP 8

#199 Incorrect handling of tags next to line breaks

#201 Never return false on documents

#203 Always tell user where he expected non-existing element

#204 Convenience function for getting first element

#210 Find first child element like CSS does not respect order

Find first child element like CSS does not respect order

Decoding HTML entities corrupts text in HTML

#208 $node->find() finds element next to $node

$node->find() finds element next to $node

#199 Incorrect handling of
tags next to line breaks