Skip to content

Commit

Permalink
Update speculation rules security and privacy questionnaire
Browse files Browse the repository at this point in the history
  • Loading branch information
jeremyroman authored Nov 14, 2023
1 parent 0114801 commit a745cf2
Showing 1 changed file with 12 additions and 3 deletions.
15 changes: 12 additions & 3 deletions speculation-rules-security-privacy-questionnaire.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Security & Privacy Questionnaire (Speculation Rules)

Covers the [speculation rules explainer](triggers.md). Based on the [W3C TAG Self-Review Questionnaire: Security and Privacy](https://w3ctag.github.io/security-questionnaire/).
Covers the [speculation rules explainer](triggers.md) and [spec](https://wicg.github.io/nav-speculation/speculation-rules.html). Based on the [W3C TAG Self-Review Questionnaire: Security and Privacy](https://w3ctag.github.io/security-questionnaire/).

### What information might this feature expose to Web sites or other parties, and for what purposes is that exposure necessary?

Expand Down Expand Up @@ -96,10 +96,19 @@ Browsers could choose to behave more conservatively, but doing so may make it po

### Does this specification have both "Security Considerations" and "Privacy Considerations" sections?

Not as yet, though we recognize that it cannot be considered complete without one.
Yes:

We do discuss security and privacy considerations thoroughly in the relevant explainers, and will be porting that into the overall "prerendering revamped" specification as that specification gets more concrete.
* [Security Considerations](https://wicg.github.io/nav-speculation/speculation-rules.html#security-considerations)
* [Privacy Considerations](https://wicg.github.io/nav-speculation/speculation-rules.html#privacy-considerations)

### Do features in your specification enable origins to downgrade default security protections?

No.

### 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?

The prefetches and prerenders already triggered may remain in memory and be used after the document is restored from bfcache, if not expired. Additional speculation can occur after that point.

### What happens when a document that uses your feature gets disconnected?

User agents [must not initiate preloading in a document which is not fully active](https://wicg.github.io/nav-speculation/speculation-rules.html#consider-speculation).

0 comments on commit a745cf2

Please sign in to comment.