Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107784
MIME-Version: 1.0
References: <CAEPJdu=DYZ8RTUtb-mDOGPdXGK4Z-h59rUq_A=wB=u6AaO7aDg@mail.gmail.com>
In-Reply-To: <CAEPJdu=DYZ8RTUtb-mDOGPdXGK4Z-h59rUq_A=wB=u6AaO7aDg@mail.gmail.com>
Date: Sat, 9 Nov 2019 18:36:31 +0100
Message-ID: <CAEPJdum3nvDMP_kWCDj4KoqoqdSXpe2CNfOQitzWrFvkcOE3-Q@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Cc: Thomas Weinert <thomas@weinert.info>
Content-Type: multipart/alternative; boundary="0000000000007ba87a0596ed572d"
Subject: Re: [RFC] DOM Living Standard API
From: kontakt@beberlei.de (Benjamin Eberlei)

--0000000000007ba87a0596ed572d
Content-Type: text/plain; charset="UTF-8"

On Fri, Mar 22, 2019 at 9:14 PM Benjamin Eberlei <kontakt@beberlei.de>
wrote:

> Hi Internals,
>
> Thomas and I are working on updating the ext/dom to add support for the
> current DOM Living Standard API as standardized here:
> https://dom.spec.whatwg.org/
>

> https://wiki.php.net/rfc/dom_living_standard_api
>
> This RFC is targeting 7.4 and contains three independent changes:
>
> - a set of new methods and interfaces that can be implemented BC as
> addition to the existing ext/dom.
> - a removal of a few "dead" classes that are exposed to userland, but
> neither documented nor containing implementation code.
> - a compatibility layer to switch the implementation between DOM Level 1-3
> and the Living Standard in places where BC is not possible.
>
> A pull request includes a nearly complete implementation of the new
> methods, but nothing of the cleanup/compatibility yet:
> https://github.com/beberlei/php-src/pull/1
>
> We are looking forward for your feedback.
>
> greetings
> Benjamin
>

Heads up, I will start the vote on this RFC on Monday.

Given ext/dom argsinfo stub patch is finally merged I could add support for
arginfo stubs for this RFC as well, so there is only one refactoring task
open to reduce code duplication, which I will do after RFC acceptance.

Based on feedback here and private mails the RFC now only contains a single
change, the addition of new methods and interfaces from the current DOM
standard that can be added with minimal BC breaks.

--0000000000007ba87a0596ed572d--