-
Notifications
You must be signed in to change notification settings - Fork 115
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
insertDTMF should normalize input #768
Comments
The spec refers to charcters A-D and says that "The characters a to d are equivalent to A to D." So it makes sense that a-d when entered are converted to ASCII upercase, and that browsers would only generate A-D. |
In the merged PR, I added a statement about normalization. Are there places where it needs to be made clear that the browser always outputs normalized values? |
The PR is mostly okay. The main problem is that it's not really phrased as a requirement, but rather as a statement of fact, yet nowhere is there a requirement that supports the statement of fact. https://ln.hixie.ch/?start=1140242962&count=1 might help. |
Anne, are you saying that the statement "The characters a to d (normalized to uppercase on entry) are equivalent to A to D." should be phrased as "The characters a to d MUST be considered equivalent to A to D"? That's language not changed by this PR (despite being marked in red), so if so, there's a new issue. (The rest of the sentence is full of MUSTs, so count as normative conformance requirements in Hixie's taxonomy). If you think this matters, please raise an issue on it. |
Basically I'd use an ASCII uppercase operation. That makes it easier to write generic code that does something with the attribute values and is also somewhat good practice.
The text was updated successfully, but these errors were encountered: