Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122173
Date: Thu, 18 Jan 2024 13:05:50 +0000
To: Niels Dossche <dossche.niels@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Message-ID: <lqcQzuiFsM5DUwmwevipw3GNQgEY03S0IOA7zT-FEh7OROFUZCY903C34kpOOTsPvLl1DgUix6MLWURPlpjLsgsoSD2WSRJBWH58Xsmk-lQ=@gpb.moe>
In-Reply-To: <2006cef3-0e8c-49cc-9703-0fa70690a4ae@gmail.com>
References: <2006cef3-0e8c-49cc-9703-0fa70690a4ae@gmail.com>
Feedback-ID: 96993444:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] [Discussion] Opt-in DOM spec-compliance
From: internals@gpb.moe ("Gina P. Banyard")

On Wednesday, 17 January 2024 at 20:22, Niels Dossche <dossche.niels@gmail.=
com> wrote:
> Hi internals
>=20
> I'm starting discussion of my RFC "Opt-in DOM spec-compliance".
>=20
> RFC link: https://wiki.php.net/rfc/opt_in_dom_spec_compliance
> Pre-RFC pitch: https://externals.io/message/122048
>=20
> Kind regards
> Niels

Hello Niels,

Thank you for the RFC and the thorough overview of the current state.

I think converting the new aliases to proper classes which have the correct=
 spec behaviour is indeed the way to proceed.

I do have some questions however, do you really think we need the DOMDocume=
nt methods to import modern nodes into legacy documents?
As I can imagine, this would provide fewer incentives for users to move to =
the new spec compliant classes.
The other thing to clarify is why and when would those return false, compar=
ed to the methods that import legacy nodes which never throw?

Best regards,

Gina P. Banyard