This proposal restricts information provided to the page (spelling/grammar highlights), and does not expand it.
Yes.
No, it further restricts exposure of the user’s dictionary.
N/A, see 3.
N/A, see 3.
6. Do the features in your specification introduce state that persists across browsing sessions?
No.
No.
No.
9. Do features in this specification enable access to device sensors?
No.
10. Do features in this specification enable new script execution/loading mechanisms?
No.
11. Do features in this specification allow an origin to access other devices?
No.
12. Do features in this specification allow an origin some measure of control over a user agent’s native UI?
No.
13. What temporary identifiers do the features in this specification create or expose to the web?
N/A, see 3.
14. How does this specification distinguish between behavior in first-party and third-party contexts?
No difference.
15. How do the features in this specification work in the context of a browser’s Private Browsing or Incognito mode?
No difference.
16. Does this specification have both “Security Considerations” and “Privacy Considerations” sections?
It’s a proposed modification of another spec’s security/privacy considerations.
17. Do features in your specification enable origins to downgrade default security protections?
No.
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?
No difference.
19. What happens when a document that uses your feature gets disconnected?
No difference.
20. Does your spec define when and how new kinds of errors should be raised?
No new errors.
21. Does your feature allow sites to learn about the user’s use of assistive technology?
No.
22. What should this questionnaire have asked?
Unknown