Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Drop executionContexts? #59

Open
annevk opened this issue May 3, 2019 · 4 comments
Open

Drop executionContexts? #59

annevk opened this issue May 3, 2019 · 4 comments

Comments

@annevk
Copy link
Member

annevk commented May 3, 2019

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.
@wanderview
Copy link
Member

It seems to me we either need to:

  1. Figure out how to make executionContexts work correctly.
  2. Or spec what actually happens to things like open blobs, cache_storage Response, etc when their underlying storage is nuked. AFAIK that is completely undefined.

Reloading contexts seems like the best option to actually getting the user to a known sane state.

@annevk
Copy link
Member Author

annevk commented May 3, 2019

2 is needed either way right? That seems like a separate problem that also exists.

@asakusuma
Copy link

There may be an expectation that executionContexts is required to ensure storage kills a service worker. I would much rather provide the guarantee that storage alone kills any service workers though. Tangentially, there were already some potential issues with spec guarantees around removing service workers: #54

@ericlaw1979
Copy link

It appears that Firefox landed their removal: https://bugzilla.mozilla.org/show_bug.cgi?id=1548034#c8

@jungkees jungkees mentioned this issue Jun 14, 2019
Open
kesselb added a commit to nextcloud/server that referenced this issue Jul 9, 2019
@kesselb
Don't send executionContexts for Clear-Site-Data
27be224 
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 <mail@danielkesselberg.de>
kesselb added a commit to nextcloud/server that referenced this issue Jul 9, 2019
@kesselb
Don't send executionContexts for Clear-Site-Data
bfadc0c 
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 <mail@danielkesselberg.de>
@kesselb kesselb mentioned this issue Jul 9, 2019
Merged
kesselb added a commit to nextcloud/server that referenced this issue Jul 9, 2019
@kesselb
Don't send executionContexts for Clear-Site-Data
6235a66 
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 <mail@danielkesselberg.de>
backportbot-nextcloud bot pushed a commit to nextcloud/server that referenced this issue Sep 16, 2019
@kesselb
Don't send executionContexts for Clear-Site-Data
48b7464 
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 <mail@danielkesselberg.de>
backportbot-nextcloud bot pushed a commit to nextcloud/server that referenced this issue Sep 16, 2019
@kesselb
Don't send executionContexts for Clear-Site-Data
24d2081 
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 <mail@danielkesselberg.de>
@annevk annevk mentioned this issue Jul 23, 2020
Open
This was referenced Oct 21, 2021
Closed
Merged
@annevk annevk mentioned this issue Feb 23, 2022
Open
@domenic domenic mentioned this issue Mar 31, 2022
Open
@github-actions github-actions bot mentioned this issue Aug 20, 2022
Merged
@github-actions github-actions bot mentioned this issue Sep 29, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@asakusuma @wanderview @annevk @ericlaw1979