Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124376
Feedback-ID: ia2404087:Fastmail
User-Agent: Cyrus-JMAP/3.11.0-alpha0-568-g843fbadbe-fm-20240701.003-g843fbadb
Precedence: bulk
MIME-Version: 1.0
Message-ID: <c9e51cdb-c7b4-46e1-888b-b0cf6e8a032c@app.fastmail.com>
In-Reply-To: <80EA6CA9-E14E-4672-A88A-46EFE9E2F3F0@automattic.com>
References: <80EA6CA9-E14E-4672-A88A-46EFE9E2F3F0@automattic.com>
Date: Wed, 10 Jul 2024 15:42:20 -0700
To: "Dennis Snell" <dennis.snell@automattic.com>,
 Internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] Decoding HTML and the Ambiguous Ampersand
Content-Type: multipart/alternative;
 boundary=8f0326255aea45259e6eaa8055911763
From: jimw@trainedmonkey.com ("Jim Winstead")

--8f0326255aea45259e6eaa8055911763
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 9, 2024, at 5:00 PM, Dennis Snell wrote:
> [ lots snipped ]
>=20
> We=E2=80=99re exploring pure-PHP solutions to these problems in WordPr=
ess in attempts to improve the reliability and safety of handling HTML. =
I=E2=80=99d love to hear your thoughts and know if anyone is willing to =
work with me to create an RFC or directly propose patches. We=E2=80=99ve=
 created a step function which allows finding the next character referen=
ce and decoding it separately, enabling some novel features like highlig=
hting the character references in source text.
>=20
> Should I propose an RFC for this?

The missing character references would probably be okay to add via a PR =
now.

Handling the ambiguous ampersand rules (either through a new flag or new=
 functions) would need to go through the RFC process. My gut tells me th=
at a new flag might be the easiest way to get it in, but I haven't looke=
d at the problem very deeply.

Timing wise, most people are very focused on hitting the deadline for PH=
P 8.4's feature freeze, and this is almost certainly too late for that. =
I would take the time to prototype solutions, make sure the full scope o=
f the problem is understood, and look to hit the ground running with an =
RFC and discussion in early September.

I'm also not sure what sort of connection may be found with the new HTML=
5 DOM features/implementation (https://wiki.php.net/rfc/domdocument_html=
5_parser).

Thanks.

Jim
--8f0326255aea45259e6eaa8055911763
Content-Type: text/html;charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">#qt {=
font-family:-apple-system, Helvetica, Arial, sans-serif;}

p.MsoNormal,p.MsoNoSpacing{margin:0}
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div style=3D"f=
ont-family:Arial;">On Tue, Jul 9, 2024, at 5:00 PM, Dennis Snell wrote:<=
br></div><blockquote type=3D"cite" id=3D"qt" style=3D""><div><div>[ lots=
 snipped ]<br></div><div style=3D"font-family:Arial;"><br></div><div sty=
le=3D"font-family:Arial;">We=E2=80=99re exploring pure-PHP solutions to =
these problems in WordPress in attempts to improve the reliability and s=
afety of handling HTML. I=E2=80=99d love to hear your thoughts and know =
if anyone is willing to work with me to create an RFC or directly propos=
e patches. We=E2=80=99ve created a step function which allows finding th=
e next character reference and decoding it separately, enabling some nov=
el features like highlighting the character references in source text.<b=
r></div><div><br></div><div>Should I propose an RFC for this?<br></div><=
/div></blockquote><div style=3D"font-family:Arial;"><br></div><div style=
=3D"font-family:Arial;">The missing character references would probably =
be okay to add via a PR now.<br></div><div style=3D"font-family:Arial;">=
<br></div><div style=3D"font-family:Arial;">Handling the ambiguous amper=
sand rules (either through a new flag or new functions) would need to go=
 through the RFC process. My gut tells me that a new flag might be the e=
asiest way to get it in, but I haven't looked at the problem very deeply=
.<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"fon=
t-family:Arial;">Timing wise, most people are very focused on hitting th=
e deadline for PHP 8.4's feature freeze, and this is almost certainly to=
o late for that. I would take the time to prototype solutions, make sure=
 the full scope of the problem is understood, and look to hit the ground=
 running with an RFC and discussion in early September.<br></div><div st=
yle=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">I=
'm also not sure what sort of connection may be found with the new HTML5=
 DOM features/implementation (<a href=3D"https://wiki.php.net/rfc/domdoc=
ument_html5_parser">https://wiki.php.net/rfc/domdocument_html5_parser</a=
>).<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"f=
ont-family:Arial;">Thanks.<br></div><div style=3D"font-family:Arial;"><b=
r></div><div style=3D"font-family:Arial;">Jim<br></div></body></html>
--8f0326255aea45259e6eaa8055911763--