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.

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

FR: Ability for a frame to indicate on initial load that storage access is required #131

Open
lghall opened this issue Oct 24, 2022 · 3 comments
Labels
future Will consider for a future revision

Comments

@lghall
Copy link

lghall commented Oct 24, 2022

At Google Workspace, we have embeds that require authentication on initial load (for example: an embedded document or a calendar appointment booking page).

This request is to expose a way for a frame to automatically request storage access on initial load via a browser-level UI associated with the frame (such as an overlay over the frame), and automatically reload the frame (and ideally other same-site frames on the same page in this state) if access is granted.

@annevk annevk added the future Will consider for a future revision label Jun 29, 2023
@annevk
Copy link
Collaborator

annevk commented Jun 29, 2023

I don't think this is something WebKit would be interested in. We want end users to engage with the nested document and have that guide the user around the initial request.

@bvandersloot-mozilla
Copy link
Collaborator

Ditto from Mozilla- if the iframe doesn't have permission to get storage access, what should be shown? I think having an interstitial page (same-origin as the intended embedded document) that requests storage-access and redirects to the intended document is a better solution. This request won't even need user interaction if the permission is already set.

@johannhof
Copy link
Member

So I think there may be some interesting things we could experiment with to help this request in spirit in the future, such as a dedicated permission element and / or more inline UI for Storage Access, but as it stands it's not high on our list of priorities either. I think I'd be interested in websites' real world experiences regarding the prompt-in-the-corner user experience and engagement rate to get a better sense of how much improvement here is needed.

I think this is still worth keeping around with a "future" label though, we've had a few issues stick around for a while to get eventually resolved (or improved).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future Will consider for a future revision
Projects
None yet
Development

No branches or pull requests

4 participants