-
What information might this feature expose to Web sites or other parties, and for what purposes is that exposure necessary?
It exposes information about the most recent cross-document navigation. This is necessary to make UX choices that are based on the previous document or the type of navigation.
-
Do features in your specification expose the minimum amount of information necessary to enable their intended uses?
Yes.
-
How do the features in your specification deal with personal information, personally-identifiable information (PII), or information derived from them?
The feature doesn't deal with such information.
-
How do the features in your specification deal with sensitive information?
The feature doesn't deal with such information.
-
Do the features in your specification introduce new state for an origin that persists across browsing sessions?
No.
-
Do the features in your specification expose information about the underlying platform to origins?
No.
-
Does this specification allow an origin to send data to the underlying platform?
No.
-
Do features in this specification enable access to device sensors?
No.
-
Do features in this specification enable new script execution/loading mechanisms?
No.
-
Do features in this specification allow an origin to access other devices?
No.
-
Do features in this specification allow an origin some measure of control over a user agent's native UI?
No.
-
What temporary identifiers do the features in this specification create or expose to the web?
None.
-
How does this specification distinguish between behavior in first-party and third-party contexts?
There is no difference in behaviour.
-
How do the features in this specification work in the context of a browser’s Private Browsing or Incognito mode?
There is no difference in behaviour for these modes.
-
Does this specification have both "Security Considerations" and "Privacy Considerations" sections?
Not in itself, it's not a new specification.
-
Do features in your specification enable origins to downgrade default security protections?
No.
-
How does your feature handle non-"fully active" documents?
It only works in fully active documents.
-
What should this questionnaire have asked?
No suggestions.