Small tweaks to the Storage Access API data#21379
Conversation
github-actions
bot
added
the
data:api
|
FYI @tunetheweb |
api/Permissions.json
Outdated
| "chrome": { | ||
| "version_added": "119" | ||
| }, | ||
| "chrome_android": "mirror", |
There was a problem hiding this comment.
I had 120 for the storage-access permission on Android based on this so would be surprised if this did make it to 119. Might be worth double checking.
There was a problem hiding this comment.
OK. I've updated it for now, but we'll try to get it checked.
@cfredric, do you know what Chrome and Chrome Android versions the top-level-storage-access permission feature is supported from?
There was a problem hiding this comment.
The top-level-storage-access permission support in Chrome (tracked as requestStorageAccessFor) shipped alongside RWS, which was enabled by default in Chrome 119 (commit).
There was a problem hiding this comment.
Thanks! So the data as-is does sound about right.
Co-authored-by: Barry Pollard <barrypollard@google.com>
…browser-compat-data into moar-storage-access-api
Elchi3
left a comment
Elchi3
left a comment
There was a problem hiding this comment.
Thanks and sorry for the delay.
4 participants
Summary
#21336 updated the Storage Access API compat data rather nicely. I created mdn/content#30500 to update the SAA docs and introduce the concept of related website sets to MDN, and in doing so, I found a couple of details I thought worth including in the BCD.
So, here goes.
Test results and supporting details
Related issues