Add Dom\Element::insertAdjacentHTML() (#16614)

Fix GH-16473: dom_import_simplexml stub is wrong

It's been wrong since PHP 8.0 at least, and the signature was inherited
in 8.4-dev to the new DOM methods.

Closes GH-16489.

Add Dom\Element::$outerHTML getter

Reference: https://html.spec.whatwg.org/multipage/dynamic-markup-insertion.html#the-outerhtml-property

Fix GH-13988: Storing DOMElement consume 4 times more memory in PHP 8.1 than in PHP 8.0

We avoid creating backing storage by using the feature introduced in
f78d5cfcd2fe06ddd6da33ff880c6

Fix GH-13988: Storing DOMElement consume 4 times more memory in PHP 8.1 than in PHP 8.0

We avoid creating backing storage by using the feature introduced in
f78d5cfcd2fe06ddd6da33ff880c6823072adc1b.

Closes GH-15593.

show more ...

Remove DOMImplementation::getFeature() (#15233)

RFC: https://wiki.php.net/rfc/deprecations_php_8_4#remove_domimplementationgetfeature_feature_version

Deprecate DOM_PHP_ERR (#15234)

* Deprecate DOM_PHP_ERR

RFC: https://wiki.php.net/rfc/deprecations_php_8_4#deprecate_dom_php_err_constant

* Apply suggestions from code revie

Deprecate DOM_PHP_ERR (#15234)

* Deprecate DOM_PHP_ERR

RFC: https://wiki.php.net/rfc/deprecations_php_8_4#deprecate_dom_php_err_constant

* Apply suggestions from code review

Co-authored-by: Tim Düsterhus <timwolla@googlemail.com>

---------

Co-authored-by: Tim Düsterhus <timwolla@googlemail.com>

show more ...

Support templated content

The template element in HTML 5 is special in the sense that it does not
add its contents into the DOM tree, but instead keeps them in a separate
shadow DOM

Support templated content

The template element in HTML 5 is special in the sense that it does not
add its contents into the DOM tree, but instead keeps them in a separate
shadow DOM document fragment. Interacting with the DOM tree cannot touch
the elements in the document fragment.

Closes GH-14906.

show more ...

Implement PHP-specific extensions to Dom (#14754)

See RFC: https://wiki.php.net/rfc/dom_additions_84

Implement Dom\TokenList (#13664)

Part of RFC: https://wiki.php.net/rfc/dom_additions_84

Closes GH-11688.

Implement Dom $innerHTML property

Implement CSS selectors

Trim trailing whitespace (#14721)

Implement Dom\HTMLElement class

Implement Dom\Document::$title getter

Implement Dom\Document::$head

Implement Dom\Document::$body getter

Introduce Dom\AdjacentPosition and use it in the insert adjacent methods

See https://wiki.php.net/rfc/dom_additions_84#allowing_php-specific_developer_experience_improvements

Make XMLDocument::xinclude() return values and error conditions sane

See https://wiki.php.net/rfc/dom_additions_84#api_amendments

Remove XML_GLOBAL_NAMESPACE (#14265)

This constant is only available if it is defined by libxml2, but it is
never defined because the minimum version of libxml2 that we support had
r

Remove XML_GLOBAL_NAMESPACE (#14265)

This constant is only available if it is defined by libxml2, but it is
never defined because the minimum version of libxml2 that we support had
removed XML_GLOBAL_NAMESPACE already.

show more ...

Update ext/dom names after policy change (#14171)

Make documentURI and URL not readonly (#13982)

These aren't actually readonly right now because `@readonly` means
nothing, and the setters are configured in php_dom.c. So no functional

Make documentURI and URL not readonly (#13982)

These aren't actually readonly right now because `@readonly` means
nothing, and the setters are configured in php_dom.c. So no functional
changes here.

DOM spec marks these as readonly, but the problem is that this reduces
usefulness in XML contexts (like WSDL scheme handling). In context of a
browser, for which DOM was designed, this actually makes sense to have
as readonly because it is tied to the origin of the page etc. But PHP is
not a browser. This also wasn't readonly in "old DOM".

show more ...

Implement HTMLCollection::namedItem()

DOM stubs: Reference interfaces from the global namespace correctly (#13801)

Change return type of DOM\HTMLDocument::saveHTML() (#13701)

Strict error checking is always true for classes in "new DOM".
This means that we always throw an error when calling
`php_

Change return type of DOM\HTMLDocument::saveHTML() (#13701)

Strict error checking is always true for classes in "new DOM".
This means that we always throw an error when calling
`php_dom_throw_error`, and therefore the false return value is not
actually possible.
Also change the stub to reflect this.

show more ...

[RFC] Add a way to opt-in ext/dom spec compliance (#13031)

RFC: https://wiki.php.net/rfc/opt_in_dom_spec_compliance