I understand the point, John. However, at least in my experience doing UA outreach, the question I often end up being asked by people who are better informed is along the lines of "have you talked to the W3C?", and if the person is even better informed they will ask "have you talked to the WHATWG?". There is a significant expectation from the broader community that these issues will be fixed via standards instead of one website/software at a time with proper library implementation. It would also provide us with the ability to point to the WHATWG's greater notability and say "see, they accepted EAI/UA as legitimate" to other players we want to convince or pressure.

So, yeah... I'm still of the opinion that this would give us significant returns.

Best,

On 13 May 2024 17:08, John Levine wrote:
It appears that Mark Datysgeld via UA-EAI <mark@governanceprimer.com> said:
-=-=-=-=-=-
-=-=-=-=-=-

Jim, thank you for bringing an update concerning my nemesis, HTML5 
input. As you know, I have talked endlessly about this being our 
absolute priority.

It seems Arnt and John are holding the fort over at the Github repo, but 
if anybody else has the level of expertise required to help over there 
(it already moved past my knowledge level), please do so. This is vital.
Honestly, I wouldn't bother.  For many years if you want to let people
enter an EAI address, you use a regular text box, not an email box.  In
view of all of the bad ideas the HTML people have about the ways they
want to forbid valid EAI addresses, I expect that we'll still tell people
to use a regular text box to enter an EAI address.

R's,
John
--
Mark W. Datysgeld
Director at Governance Primer [governanceprimer.com]
ICANN GNSO Councilor