Skip to content
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

Input events 2024-11-21 > 2024-12-19 #79

Open
Tracked by #166
siusin opened this issue Nov 21, 2024 · 0 comments
Open
Tracked by #166

Input events 2024-11-21 > 2024-12-19 #79

siusin opened this issue Nov 21, 2024 · 0 comments
Labels
LC Working Draft approaching CR. pending This issue needs to get a reviewer assigned to it REVIEW REQUESTED

Comments

@siusin
Copy link

siusin commented Nov 21, 2024

In the issue title above add the document name followed by the date of this request, then the date of your proposed deadline for comments.

  • name of spec to be reviewed:
    Input Events Level 2

  • URL of spec:
    https://www.w3.org/TR/2024/WD-input-events-2-20241018/

  • Does your document have an in-line Security Considerations section, ideally one separate from the Privacy Considerations? If not, corrrect that before proceeding further.
    Yes

  • What and when is your next expected transition?
    CR, 2024-12-19

  • What has changed since any previous review?
    Please review the list of normative changes since 2018 at the following link: Horizontal Review of Input events input-events#166

  • Please point to the results of your own self-review (see https://w3ctag.github.io/security-questionnaire/)
    (1) PII? No
    (2) High value data? No
    (3) New state that persists across browsing sessions? No
    (4) Persistent, cross-origin state? No
    (5) Newly expose data to an origin? No
    (6) New script exe/loading? No
    (7) Access location? No
    (8) Access sensors? No
    (9) Access local computing environment? No.
    (10) Access other devices? No
    (11) Control over UA's UI? No
    (12) Expose temp IDs? No
    (13) 1st party vs. 3rd party contexts? No
    (14) What about "incognito"? No changes
    (15) Local data persist? No
    (16) "Security Considerations" and "Privacy Considerations"? There are
    no known security or privacy impacts of this feature beyond
    fingerprinting [ fingerprinting-guidance] techniques that already are
    available through existing events, such as the keydown and keypress [
    UI-EVENTS] events.
    (17) Downgrade default security? N

  • Where and how to file issues arising?
    https://github.com/w3c/input-events/issues/new
    Thank you!

  • Pointer to any explainer for the spec?
    None.

Other comments:
the previous review request: https://lists.w3.org/Archives/Public/public-web-security/2017Jun/0007.html

@siusin siusin added REVIEW REQUESTED pending This issue needs to get a reviewer assigned to it LC Working Draft approaching CR. labels Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
LC Working Draft approaching CR. pending This issue needs to get a reviewer assigned to it REVIEW REQUESTED
Projects
None yet
Development

No branches or pull requests

1 participant