On 15 Jul 2019, at 14:52, John Levine wrote:
In article <op.z4vd4xybag6dn2@chaalss-macbook-pro.home> you write:
Note that there are quite a lot of browsers with substantial usage, which choose when to do something different, beyond "the 4" that control the WHAT-WG. Testing some of those - or filing issues for them to support EAI - might be worthwhile.
Unless I missed something fairly basic, the browser has no effect a web site accepting EAI addreses.
well, if one puts <input type=‘email’>, then the browser is involved. And my current basic tests on my platform show that none of them accepts EAI.
Every browser in the past decade has enough UTF-8 support to allow sites to input EAI addresses.
if one puts <input type=‘text’>, then browser accepts utf8
The site's Javascript does the address validation and the site's servers either handle EAI addresses or don't. The WHATWG pattern is just a regular expression for programmers to use to validate user input.
that is the next level of validation. First one depends on how the <input> tag is used. Marc.
Regards, John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.