Following up on comment 9. It looks like there isn't such a mechanism. The patch in comment 11 adds a call from content to parent process to fetch the updated cookie list on storage access grant. This also updates the `mCookieKeysInContent` list. It fixes 2 bugs. Both are covered by the test I'm adding in comment 10: 1. The bug STR: A cookie change in another tab doesn't arrive in the iframe. 2. When there is no first party context present (e.g. opened in a separate tab) cookies don't get sent to the iframe. While `mCookieKeysInContent` which leads to (1) was introduced in Bug 1713203, I don't think we should treat this as a regression. The real bug is (2) old. Mozregression was inconclusive, but led me back to versions that didn't even support the Storage Access API.
Bug 1865749 Comment 12 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Following up on comment 9. It looks like there isn't such a mechanism. The patch in comment 11 adds a call from content to parent process to fetch the updated cookie list on storage access grant. This also updates the `mCookieKeysInContent` list. It fixes 2 bugs. Both are covered by the test I'm adding in comment 10: 1. The bug STR: A cookie change in another tab doesn't arrive in the iframe. 2. When there is no first party context present (e.g. opened in a separate tab) cookies don't get sent to the iframe on storage access grant. Which means `document.cookie` does not contain the first party cookies. While `mCookieKeysInContent` which leads to (1) was introduced in Bug 1713203, I don't think we should treat this as a regression. The real bug is (2) old. Mozregression was inconclusive, but led me back to versions that didn't even support the Storage Access API.