The scope of storage access as per-frame or per-page was discussed in the standards process here: https://github.com/privacycg/storage-access/issues/3
The decision was to have per-page storage access by default. Recent feedback from Google and conversation with Mozilla suggest that we might want to support the caller choosing the scope.
This bug tracks supporting different scope configurations while keeping the existing default as per-frame. A later patch will switch the default and add test cases for per-page scope (unless my code reviewers ask me to do it all in one patch).
Created attachment 399794 [details]
Thank you, Alex!
Committed r262024: <https://trac.webkit.org/changeset/262024>
All reviewed patches have been landed. Closing bug and clearing flags on attachment 399794 [details].