Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123715
Precedence: bulk
MIME-Version: 1.0
References: <28a3990b-f0a4-4c4e-a14d-3eac3aa7fbce@gmail.com>
 <CAJp_myXQn8VTQK7gZA4sCCvQ=6zO-dqtZ5A3gZ8catACj3xu=g@mail.gmail.com> <7d69ef65-4c16-4479-9239-46b6df20cac3@gmail.com>
In-Reply-To: <7d69ef65-4c16-4479-9239-46b6df20cac3@gmail.com>
Date: Thu, 20 Jun 2024 16:55:49 -0500
Message-ID: <CAJp_myX+enEbQPR7qJuqvvRMFQwCUH0YFJeZ5Zpx5qMoNbw6Uw@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] [Vote] New ext-dom features in PHP 8.4
To: Niels Dossche <dossche.niels@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000004542c1061b5961db"
From: mweierophinney@gmail.com ("Matthew Weier O'Phinney")

--0000000000004542c1061b5961db
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Jun 20, 2024, 1:27=E2=80=AFPM Niels Dossche <dossche.niels@gmail.co=
m> wrote:

> On 20/06/2024 16:28, Matthew Weier O'Phinney wrote:
> >
> >
> > On Mon, Jun 10, 2024 at 1:15=E2=80=AFPM Niels Dossche <dossche.niels@gm=
ail.com
> <mailto:dossche.niels@gmail.com>> wrote:
> >
> >     Hi internals
> >
> >     I'm opening the vote of my RFC "New ext-dom features in PHP 8.4".
> >     RFC link: https://wiki.php.net/rfc/dom_additions_84 <
> https://wiki.php.net/rfc/dom_additions_84>
> >     Voting runs until 24th of June 21:00 GMT+2.
> >
> >     Kind regards
> >     Niels
> >
> >
> > Question: why is `Dom\Document::$head` marked as readonly?
>
> The HTML spec defines the head property to be readonly:
> https://html.spec.whatwg.org/#document
> That's why $head is marked readonly.
>
> So I guess the question becomes "why does the HTML spec define it this
> way?"
> I couldn't find a conclusive answer to this, it looks like this has been
> read-only since HTML's early days...
> I thought about it but don't really see a technical reason why this is th=
e
> case. If I had to take a guess I'd say it's for simplicity sake.
> > he/him
>

I can understand that from a browser perspective, but from PHP, where we
might be manipulating HTML to send back to the client, having it readonly
would be a pretty big hindrance.

>

--0000000000004542c1061b5961db
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><br><br><div class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D"gmail_attr">On Thu, Jun 20, 2024, 1:27=E2=80=AFPM Niels Dossche &l=
t;<a href=3D"mailto:dossche.niels@gmail.com">dossche.niels@gmail.com</a>&gt=
; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">On 20/06/2024 16:28, Matth=
ew Weier O&#39;Phinney wrote:<br>
&gt; <br>
&gt; <br>
&gt; On Mon, Jun 10, 2024 at 1:15=E2=80=AFPM Niels Dossche &lt;<a href=3D"m=
ailto:dossche.niels@gmail.com" target=3D"_blank" rel=3D"noreferrer">dossche=
.niels@gmail.com</a> &lt;mailto:<a href=3D"mailto:dossche.niels@gmail.com" =
target=3D"_blank" rel=3D"noreferrer">dossche.niels@gmail.com</a>&gt;&gt; wr=
ote:<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Hi internals<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0I&#39;m opening the vote of my RFC &quot;New ext-do=
m features in PHP 8.4&quot;.<br>
&gt;=C2=A0 =C2=A0 =C2=A0RFC link: <a href=3D"https://wiki.php.net/rfc/dom_a=
dditions_84" rel=3D"noreferrer noreferrer" target=3D"_blank">https://wiki.p=
hp.net/rfc/dom_additions_84</a> &lt;<a href=3D"https://wiki.php.net/rfc/dom=
_additions_84" rel=3D"noreferrer noreferrer" target=3D"_blank">https://wiki=
.php.net/rfc/dom_additions_84</a>&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Voting runs until 24th of June 21:00 GMT+2.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Kind regards<br>
&gt;=C2=A0 =C2=A0 =C2=A0Niels<br>
&gt; <br>
&gt; <br>
&gt; Question: why is `Dom\Document::$head` marked as readonly?<br>
<br>
The HTML spec defines the head property to be readonly: <a href=3D"https://=
html.spec.whatwg.org/#document" rel=3D"noreferrer noreferrer" target=3D"_bl=
ank">https://html.spec.whatwg.org/#document</a><br>
That&#39;s why $head is marked readonly.<br>
<br>
So I guess the question becomes &quot;why does the HTML spec define it this=
 way?&quot;<br>
I couldn&#39;t find a conclusive answer to this, it looks like this has bee=
n read-only since HTML&#39;s early days...<br>
I thought about it but don&#39;t really see a technical reason why this is =
the case. If I had to take a guess I&#39;d say it&#39;s for simplicity sake=
.<br>&gt; he/him<br></blockquote></div></div><div dir=3D"auto"><br></div><d=
iv dir=3D"auto">I can understand that from a browser perspective, but from =
PHP, where we might be manipulating HTML to send back to the client, having=
 it readonly would be a pretty big hindrance.=C2=A0</div><div dir=3D"auto">=
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote></div></div></div>

--0000000000004542c1061b5961db--