-
Notifications
You must be signed in to change notification settings - Fork 6
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
Status of incubation (and can we archive this repo)? #5
Comments
There's no active work on implementing this in Chromium, and Firefox especially doesn't like it. If a compelling use case comes up that isn't adequately handled by per-API request functions, someone could revive it, but it'll be simpler to work on adding things to the per-API request functions. e.g. time-limiting could be a pattern on those functions rather than a new parameter to |
@jyasskin, given the lack of activity in the last few years, I'm wondering if we can archive this repo? |
I don't see any problem with archiving this repo. We can always un-archive it later if someone wants to revive it. |
Is this spec dead? See w3c/permissions#159.
It's mentioned and required by Time Limited Permissions spec. See https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/TimeLimitedPermissions/Explainer.md#api-proposal.
The text was updated successfully, but these errors were encountered: