-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Code-points, code-units, characters, oh my! #312
Comments
I think it's actually better to not talk about characters. We're slowly changing things around. Especially in the context of DOMString that would be extremely ambiguous. |
That's fine - but need guidance. I tried the other two and got laughed at for using them wrong 👍 |
Yeah, that's whatwg/infra#1 basically. I have plan, but haven't made the time thus far. |
Ok, don't feel so bad now - and that's great to see! Thanks @annevk! |
Seems this is in infra's realm. Closing here. |
As per, w3c/payment-request#322 and also in HTML, it seems that spec editors want to talk about "characters", as those things
logicallyeditorially make most sense.It would be nice if WebIDL allowed talking about "characters" in the context of DOMString.
The text was updated successfully, but these errors were encountered: