-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop executionContexts? #59
Comments
It seems to me we either need to:
Reloading contexts seems like the best option to actually getting the user to a known sane state. |
2 is needed either way right? That seems like a separate problem that also exists. |
There may be an expectation that |
It appears that Firefox landed their removal: https://bugzilla.mozilla.org/show_bug.cgi?id=1548034#c8 |
There are plans to remove executionContexts from the spec: w3c/webappsec-clear-site-data#59 Firefox already removed it https://bugzilla.mozilla.org/show_bug.cgi?id=1548034 Chromium implementation is not finish: https://bugs.chromium.org/p/chromium/issues/detail?id=898503&q=clear-site-data&sort=-modified&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified Signed-off-by: Daniel Kesselberg <[email protected]>
There are plans to remove executionContexts from the spec: w3c/webappsec-clear-site-data#59 Firefox already removed it https://bugzilla.mozilla.org/show_bug.cgi?id=1548034 Chromium implementation is not finish: https://bugs.chromium.org/p/chromium/issues/detail?id=898503&q=clear-site-data&sort=-modified&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified Signed-off-by: Daniel Kesselberg <[email protected]>
There are plans to remove executionContexts from the spec: w3c/webappsec-clear-site-data#59 Firefox already removed it https://bugzilla.mozilla.org/show_bug.cgi?id=1548034 Chromium implementation is not finish: https://bugs.chromium.org/p/chromium/issues/detail?id=898503&q=clear-site-data&sort=-modified&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified Signed-off-by: Daniel Kesselberg <[email protected]>
There are plans to remove executionContexts from the spec: w3c/webappsec-clear-site-data#59 Firefox already removed it https://bugzilla.mozilla.org/show_bug.cgi?id=1548034 Chromium implementation is not finish: https://bugs.chromium.org/p/chromium/issues/detail?id=898503&q=clear-site-data&sort=-modified&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified Signed-off-by: Daniel Kesselberg <[email protected]>
There are plans to remove executionContexts from the spec: w3c/webappsec-clear-site-data#59 Firefox already removed it https://bugzilla.mozilla.org/show_bug.cgi?id=1548034 Chromium implementation is not finish: https://bugs.chromium.org/p/chromium/issues/detail?id=898503&q=clear-site-data&sort=-modified&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified Signed-off-by: Daniel Kesselberg <[email protected]>
Hi team,
then tab1 would trigger the reload of tab2, which would attempt to clear executionContexts as well, thus re-loading tab1 and so on, causing an infinite loop of reloading between the 2 tabs Suggestion: if this interpretation is correct, instead of reloading all the pages of the same origin, maybe we should instead unload other same-origin browsing contexts instead of reloading them. Hope this helps. Thanks for all this security work! |
We might drop this feature from Firefox as Chrome doesn't implement it and we keep running into issues with it. Latest is https://bugzilla.mozilla.org/show_bug.cgi?id=1548034.
The text was updated successfully, but these errors were encountered: