Add non-"fully active" document question #128
Conversation
As discussed in w3ctag/design-reviews#628, there are some privacy considerations that might be worth pointing out in the Security & Privacy Questionnaire. This change adds a question on non-"fully active" document handling to the questionnaire.
questionnaire.markdown
Outdated
| @@ -37,4 +37,5 @@ For your convenience, a copy of the questionnaire's questions is quoted here in | |||
| > Considerations" sections? | |||
| > 17. Do features in your specification enable origins to downgrade default | |||
| > security protections? | |||
| > 18. What should this questionnaire have asked? | |||
| > 18. How does your feature handle non-"[=Document/fully active=]" documents? | |||
There was a problem hiding this comment.
Markdown doesn't support Bikeshed linking syntax, so maybe use a Markdown link here.
There was a problem hiding this comment.
I should make the Python script that generates this markdown file strip out Bikeshed syntax.
There was a problem hiding this comment.
Ah, right, this was automatically generated. I've removed the bikeshed syntax here and index.bs as well to not be blocked by the script change!
index.bs
Outdated
| How does your feature handle non-"fully active" documents? | ||
| </h3> | ||
|
|
||
| After a user navigated away from a document, |
index.bs
Outdated
|
|
||
| After a user navigated away from a document, | ||
| the document might stay around in a non-"[=Document/fully active=]" state, | ||
| and might be reused when the user navigates back to the entry holding the document. |
There was a problem hiding this comment.
not sure "to the entry" is easy to understand. Maybe just remove?
|
Nice! That's something we wanted to add. Thanks for doing it! + @msramek FYI |
|
Thanks a lot for the review! I've addressed the comment and so this should be mergeable now. I heard from @ArthurSonzogni that Chrome's intents review process now also considers a feature's relationship with BFCache/non-fully active documents, so it's nice to have an official linkable guide here :) |
As discussed in w3ctag/design-reviews#628, there are some privacy considerations that might be worth pointing out in the Security & Privacy Questionnaire.
This change adds a question on non-"fully active" document handling to the questionnaire.
cc @hober @domenic @fergal
Note that there's another PR for the "Web Platform Design Principles" doc at w3ctag/design-principles#317
Preview | Diff