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
"A user agent" vs "the user agent" #399
Labels
Comments
patrickhlauke
added a commit
that referenced
this issue
Aug 3, 2021
To avoid confusion, any time a normative/clear statement is made, change to "the" (to not give the impression that a UA can somehow delegate things to another UA). Closes #399
patrickhlauke
added a commit
that referenced
this issue
Aug 3, 2021
To avoid confusion, any time a normative/clear statement is made, change to "the" (to not give the impression that a UA can somehow delegate things to another UA). Closes #399
patrickhlauke
added a commit
that referenced
this issue
Aug 3, 2021
To avoid confusion, any time a normative/clear statement is made, change to "the" (to not give the impression that a UA can somehow delegate things to another UA). Closes #399
patrickhlauke
added a commit
that referenced
this issue
Aug 3, 2021
* Change instances of "a user agent" to "the user agent" To avoid confusion, any time a normative/clear statement is made, change to "the" (to not give the impression that a UA can somehow delegate things to another UA). Closes #399 * Case sensitive find/replace - also catch uppercase "A user agent..."
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The spec inconsistently uses "a user agent" vs "the user agent". I spotted quite a few places like this:
where the spec defines a normative behavior for the specific user agent for the whole context.
One precise problem: we can only talk about a "shared"
pointerId
in apointerdown
-pointermove
-pointerup
event sequence when all these events are in a single user agent implied by the context. So I think we should say "The user agent MUST fire..." in (almost?) all the cases.The text was updated successfully, but these errors were encountered: