Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122050
Message-ID: <64e23177-e5c4-4897-b5f1-9d5111f7ab1e@gmail.com>
Date: Tue, 26 Dec 2023 23:13:59 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: PHP internals <internals@lists.php.net>
References: <756bcf2b-f98d-4203-9004-1cbfd402337a@gmail.com>
 <ccbc41f4-5553-488e-bad1-a964f3984273@bastelstu.be>
In-Reply-To: <ccbc41f4-5553-488e-bad1-a964f3984273@bastelstu.be>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Pre-RFC: Fixing spec bugs in the DOM extension
From: dossche.niels@gmail.com (Niels Dossche)

Hi Tim

On 26/12/2023 22:58, Tim Düsterhus wrote:
> Hi
> 
> On 12/26/23 22:45, Niels Dossche wrote:
>> In my opinion, having them become proper classes instead of aliases has my preference: either we fix everything in one go now while we have the opportunity, or never.
> 
> As I've already told you in private, I'm in favor of using this opportunity.
> 
>> Let me know what you think, especially regarding the type issues.
>>
> 
> Will the classes be made `final` if they are no longer aliases? That should (hopefully) make similar changes somewhat easier in the future.

I've been thinking about that as well, but I'm not sure.
We still have the registerNodeClass() feature, and I've seen people ask to bring this even further to allow custom Element classes (e.g. MyHTMLScriptElement etc).
I'd like to hear from more people on this matter.

> 
> Best regards
> Tim Düsterhus

Kind regards
Niels