w3c / w3c/FileAPI

Self-Review Questionnaire for FileAPI: Security and Privacy

Open
#214 0 comments 0 reactions 1 assignee View on GitHub

@mkruisselbrink is already working on this.

Since Nov 11, 2025.

Dominant language
HTML
Stars
118
Forks
52
Avg merge
9d 16h
Merged PRs (30d)
1

Description

Self-Review Questionnaire: Security and Privacy

The full questionnaire is at https://w3c.github.io/security-questionnaire/.

For your convenience, a copy of the questionnaire's questions is included here in Markdown, so you can easily include your answers in an explainer.


  1. What information does this feature expose,
    and for what purposes?
  2. Do features in your specification expose the minimum amount of information
    necessary to implement the intended functionality?
  3. Do the features in your specification expose personal information,
    personally-identifiable information (PII), or information derived from
    either?
  4. How do the features in your specification deal with sensitive information?
  5. Does data exposed by your specification carry related but distinct
    information that may not be obvious to users?
  6. Do the features in your specification introduce state
    that persists across browsing sessions?
  7. Do the features in your specification expose information about the
    underlying platform to origins?
  8. Does this specification allow an origin to send data to the underlying
    platform?
  9. Do features in this specification enable access to device sensors?
  10. Do features in this specification enable new script execution/loading
    mechanisms?
  11. Do features in this specification allow an origin to access other devices?
  12. Do features in this specification allow an origin some measure of control over
    a user agent's native UI?
  13. What temporary identifiers do the features in this specification create or
    expose to the web?
  14. How does this specification distinguish between behavior in first-party and
    third-party contexts?
  15. How do the features in this specification work in the context of a browser’s
    Private Browsing or Incognito mode?
  16. Does this specification have both "Security Considerations" and "Privacy
    Considerations" sections?
  17. Do features in your specification enable origins to downgrade default
    security protections?
  18. What happens when a document that uses your feature is kept alive in BFCache
    (instead of getting destroyed) after navigation, and potentially gets reused
    on future navigations back to the document?
  19. What happens when a document that uses your feature gets disconnected?
  20. Does your spec define when and how new kinds of errors should be raised?
  21. Does your feature allow sites to learn about the user's use of assistive technology?
  22. What should this questionnaire have asked?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.