DOMDocument::loadHTML

(PHP 5, PHP 7)

DOMDocument::loadHTML — Load HTML from a string

说明

public bool DOMDocument::loadHTML ( string $source [, int $options = 0 ] )

The function parses the HTML contained in the string source. Unlike loading XML, HTML does not have to be well-formed to load. This function may also be called statically to load and create a DOMDocument object. The static invocation may be used when no DOMDocument properties need to be set prior to loading.

参数

source: The HTML string.
options: Since PHP 5.4.0 and Libxml 2.6.0, you may also use the options parameter to specify additional Libxml parameters.

返回值

成功时返回 TRUE ，或者在失败时返回 FALSE 。 If called statically, returns a DOMDocument 或者在失败时返回 FALSE .

错误／异常

If an empty string is passed as the source, a warning will be generated. This warning is not generated by libxml and cannot be handled using libxml's error handling functions.

此方法可以被静态调用,但会抛出一个 E_STRICT 错误。

尽管非正确格式化的 HTML 仍应该被成功调入，但此函数会在遇到错误标记时产生 E_WARNING 错误。libxml 错误处理函数可以用来处理这类错误。

范例

Example #1 Creating a Document

  <?php
$doc  = new  DOMDocument ();
 $doc -> loadHTML ( "<html><body>Test<br></body></html>" );
echo  $doc -> saveHTML ();
 ?>

更新日志

版本	说明
5.4.0	Added `options` parameter.

参见

DOMDocument::loadHTMLFile() - Load HTML from a file
DOMDocument::saveHTML() - Dumps the internal document into a string using HTML formatting
DOMDocument::saveHTMLFile() - Dumps the internal document into a file using HTML formatting

用户评论:

[#1] finkenb2 at mail dot lib dot msu dot edu [2015-10-05 16:03:24]

Warning: This does not function well with HTML5 elements such as SVG. Most of the advice on the Web is to turn off errors in order to have it work with HTML5.

[#2] cake at brothercake dot com [2012-12-16 17:57:46]

Be aware that this function doesn't actually understand HTML -- it fixes tag-soup input using the general rules of SGML, so it creates well-formed markup, but has no idea which element contexts are allowed.

For example, with input like this where the first element isn't closed:

<span>hello <div>world</div>

loadHTML will change it to this, which is well-formed but invalid:

<span>hello <div>world</div></span>

[#3] Alex [2010-04-10 08:45:01]

Beware of the "gotcha" (works as designed but not as expected): if you use loadHTML, you cannot validate the document. Validation is only for XML. Details here: http://bugs.php.net/bug.php?id=43771&edit=1

[#4] Shane Harter [2010-01-04 08:42:18]

DOMDocument is very good at dealing with imperfect markup, but it throws warnings all over the place when it does.

This isn't well documented here. The solution to this is to implement a separate aparatus for dealing with just these errors.

Set libxml_use_internal_errors(true) before calling loadHTML. This will prevent errors from bubbling up to your default error handler. And you can then get at them (if you desire) using other libxml error functions.

You can find more info here http://www.php.net/manual/en/ref.libxml.php

[#5] mdmitry at gmail dot com [2009-12-21 09:02:31]

You can also load HTML as UTF-8 using this simple hack:

<?php $doc = new DOMDocument(); $doc->loadHTML('<?xml encoding="UTF-8">' . $html); // dirty fix foreach ($doc->childNodes as $item) if ($item->nodeType == XML_PI_NODE) $doc->removeChild($item); // remove hack $doc->encoding = 'UTF-8'; // insert proper ?>

[#6] piopier [2009-06-14 08:29:19]

Here is a function I wrote to capitalize the previous remarks about charset problems (UTF-8...) when using loadHTML and then DOM functions.
It adds the charset meta tag just after <head> to improve automatic encoding detection, converts any specific character to an html entity, thus PHP DOM functions/attributes will return correct values.

<?php mb_detect_order("ASCII,UTF-8,ISO-8859-1,windows-1252,iso-8859-15"); function loadNprepare($url,$encod='') { $content = file_get_contents($url); if (!empty($content)) { if (empty($encod)) $encod = mb_detect_encoding($content); $headpos = mb_strpos($content,'<head>'); if (FALSE=== $headpos) $headpos= mb_strpos($content,'<HEAD>'); if (FALSE!== $headpos) { $headpos+=6; $content = mb_substr($content,0,$headpos) . '<meta http-equiv="Content-Type" content="text/html; charset='.$encod.'">' .mb_substr($content,$headpos); } $content=mb_convert_encoding($content, 'HTML-ENTITIES', $encod); } $dom = new DomDocument; $res = $dom->loadHTML($content); if (!$res) return FALSE; return $dom; } ?>

NB: it uses mb_strpos/mb_substr instead of mb_ereg_replace because that seemed more efficient with huge html pages.

[#7] Errol [2009-02-11 08:05:13]

It should be noted that when any text is provided within the body tag
outside of a containing element, the DOMDocument will encapsulate that
text into a paragraph tag (<p>).

For example:
<?php $doc = new DOMDocument(); $doc->loadHTML("<html><body>Test<br><div>Text</div></body></html>"); echo $doc->saveHTML(); ?>

will yield:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
"http://www.w3.org/TR/REC-html40/loose.dtd">
<html><body>
<p>Test<br></p>
<div>Text</div>
</body></html>

while:
<?php $doc = new DOMDocument(); $doc->loadHTML( "<html><body><i>Test</i><br><div>Text</div></body></html>"); echo $doc->saveHTML(); ?>

will yield:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
"http://www.w3.org/TR/REC-html40/loose.dtd">
<html><body>
<i>Test</i><br><div>Text</div>
</body></html>

[#8] jamesedwardcooke+php at gmail dot com [2008-10-19 23:37:08]

Using loadHTML() automagically sets the doctype property of your DOMDocument instance(to the doctype in the html, or defaults to 4.0 Transitional). If you set the doctype with DOMImplementation it will be overridden.

I assumed it was possible to set it and then load html with the doctype I defined(in order to decide the doctype at runtime), and ran into a huge headache trying to find out where my doctype was going. Hopefully this helps someone else.

[#9] xuanbn at yahoo dot com [2007-10-04 01:38:12]

If you use loadHTML() to process utf HTML string (eg in Vietnamese), you may experience result in garbage text, while some files were OK. Even your HTML already have meta charset  like

  <meta http-equiv="content-type" content="text/html; charset=utf-8">

I have discovered that, to help loadHTML() process utf file correctly, the meta tag should come first, before any utf string appear. For example, this HTML file

<html>
<head>
    <meta http-equiv="content-type" content="text/html; charset=utf-8">
    <title> Vietnamese - Ti?ng Vi?t</title>
  </head>
<body></body>
</html>

will be OK with loadHTML() when <meta> tag appear <title> tag.

But the file below will not regcornize by loadHTML() because <title> tag contains utf string appear before <meta> tag.

<html>
<head>
    <title> Vietnamese - Ti?ng Vi?t</title>
    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
<body></body>
</html>

[#10] hanhvansu at yahoo dot com [2007-04-26 20:50:54]

When using loadHTML() to process UTF-8 pages, you may meet the problem that the output of dom functions are not like the input. For example, if you want to get "C?nh tranh", you will receive "C????nh tranh". I suggest we use mb_convert_encoding before load UTF-8 page :
<?php $pageDom = new DomDocument(); $searchPage = mb_convert_encoding($htmlUTF8Page, 'HTML-ENTITIES', "UTF-8"); @$pageDom->loadHTML($searchPage); ?>

[#11] romain dot lalaut at laposte dot net [2007-02-15 08:31:30]

Note that the elements of such document will have no namespace even with <html xmlns="http://www.w3.org/1999/xhtml">

[#12] bigtree at DONTSPAM dot 29a dot nl [2005-04-26 02:15:39]

Pay attention when loading html that has a different charset than iso-8859-1. Since this method does not actively try to figure out what the html you are trying to load is encoded in (like most browsers do), you have to specify it in the html head. If, for instance, your html is in utf-8, make sure you have a meta tag in the html's head section:

<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
</head>

If you do not specify the charset like this, all high-ascii bytes will be html-encoded. It is not enough to set the dom document you are loading the html in to UTF-8.