Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:122051 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 64337 invoked from network); 26 Dec 2023 22:22:23 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 26 Dec 2023 22:22:23 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 1EE84180058 for ; Tue, 26 Dec 2023 14:22:49 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from mail-oo1-f47.google.com (mail-oo1-f47.google.com [209.85.161.47]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 26 Dec 2023 14:22:48 -0800 (PST) Received: by mail-oo1-f47.google.com with SMTP id 006d021491bc7-59426ca689cso1958683eaf.0 for ; Tue, 26 Dec 2023 14:22:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1703629342; x=1704234142; darn=lists.php.net; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=2s/eEA/d6ynz9eWwNpu2k0J3IQr9XPA8BxjgliMOZuE=; b=DA/zKlwMDsMKGLOUZmbOw1D0Cbeqn+XELvcWSsmiL40X1XAkvsckBBW+zehLIdXxwp qVx+Yoy2qwS/NM2+sP7XAwKnUNqM27dA4jMjfjIXpndTEwaAtRLLavayk2qjWTM0uJmi pvofmCYEVUveVmskdU1Y9SXJd82XFYlzP3aeGhZ8m/YGHhQEytcdoRUR7lmNuWOQlndS m50blVDLbduE8j+OOFw/TGO7hFvI2/e2RSLARn0rBIFyXeELqsddsxSOpzm8RqsZ9rft qEhaNeArYC6y+izCHKacjwpJoaUgVw1Ox3VThgxehQt5wMZaQHXZMcSf9h7GwcC5sLpK krgw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703629342; x=1704234142; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=2s/eEA/d6ynz9eWwNpu2k0J3IQr9XPA8BxjgliMOZuE=; b=EQ5ELgAL1aMIrOA3jhEP+j2FZ4uTZNJKQcyMFwAaLEebD9uBfULDE/q41s0IcGNHRd AnIjBdn/53NwvDK5yFf7HHMql6JBWHKouuuX/KlUeaor4fBhdmTimWOSeO7mKUIUIxV1 E/ZqPpY8Jbj5Cp9e/n7VT0/jWdNsEjLhrO/R2Bx0mGulNCkX46nyxLQsTDdn6Z43d4g3 mB9732pENvzf7x6L+JTRb/1tfeE+BFHdrptqkcnLfBSM+di82wzXUFU2IT/Zcny3xbUe Wg2f35rbRwTys0HCyGgGSZ9Tryi7AHcbALbg4HU3jmt7fQ0i6ctKaMwOVc/iWlapAPQS uxvw== X-Gm-Message-State: AOJu0YxCcCvbbWH8SmhPNDZXHQ4xu2lJTkh4gqKx1v/hc2N3kfVaJDuK FZhhHnAjUUCpIAbOBi4+dV5yC/G/R1uWmxauRH8= X-Google-Smtp-Source: AGHT+IHpaKUzgcXLxcZdJk1a9Z0ew5KDLbXAvHeRspqJ6fr/2r09rBBuK6FYusqXTEBu6DA2LqU2zVb5CKHrqQTVItk= X-Received: by 2002:a05:6820:628:b0:594:25d9:505d with SMTP id e40-20020a056820062800b0059425d9505dmr3955601oow.6.1703629342287; Tue, 26 Dec 2023 14:22:22 -0800 (PST) MIME-Version: 1.0 References: <756bcf2b-f98d-4203-9004-1cbfd402337a@gmail.com> <64e23177-e5c4-4897-b5f1-9d5111f7ab1e@gmail.com> In-Reply-To: <64e23177-e5c4-4897-b5f1-9d5111f7ab1e@gmail.com> Date: Tue, 26 Dec 2023 23:22:11 +0100 Message-ID: To: Niels Dossche Cc: PHP internals Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Pre-RFC: Fixing spec bugs in the DOM extension From: landers.robert@gmail.com (Robert Landers) On Tue, Dec 26, 2023 at 11:14=E2=80=AFPM Niels Dossche wrote: > > Hi Tim > > On 26/12/2023 22:58, Tim D=C3=BCsterhus wrote: > > Hi > > > > On 12/26/23 22:45, Niels Dossche wrote: > >> In my opinion, having them become proper classes instead of aliases ha= s my preference: either we fix everything in one go now while we have the o= pportunity, or never. > > > > As I've already told you in private, I'm in favor of using this opportu= nity. > > > >> Let me know what you think, especially regarding the type issues. > >> > > > > Will the classes be made `final` if they are no longer aliases? That sh= ould (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 t= o bring this even further to allow custom Element classes (e.g. MyHTMLScrip= tElement etc). > I'd like to hear from more people on this matter. > > > > > Best regards > > Tim D=C3=BCsterhus > > Kind regards > Niels > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: https://www.php.net/unsub.php > Hi Niels, > We still have the registerNodeClass() feature, and I've seen people ask t= o bring this even further to allow custom Element classes (e.g. MyHTMLScrip= tElement etc). > I'd like to hear from more people on this matter. Custom element classes would be really nice! I ended up having to write a custom html5 parser in pure php due to the shortcomings of php's extension. Having the ability to create custom elements can make the semantics much more clear (a HeaderElement class, for example). Robert Landers Software Engineer Utrecht NL