Positive on the Cookie Store API (subset) #1047
Conversation
There was a problem hiding this comment.
Update makes sense given comments by @martinthomson and @ehsan on #94.
Given that this "positive" is only on a subset of the proposal, we should be precise in exactly what that subset is, and in asking for it, by filing an issue on https://github.com/WICG/cookie-store/issues/ asking for the precise subsetting we want (and believe others will support), and then citing that issue in our positive comment on #94 and/or the 'mozPositionDetail' field in this entry.
In addition, please follow-up on WICG/cookie-store#186 and indicate that we are positive with moving ONLY that subset to the WebApps WG, to help make that happen.
|
See #1106 |
activities.json
Outdated
| "mozPosition": "defer", | ||
| "mozPositionDetail": "This API provides better access to cookies. However, the improvements also expand access to cookie metadata and the interactions with privacy features like the Storage Access API are unclear. Work on improving cookie interoperability, which is ongoing, might be needed before an assessment can be made.", | ||
| "mozPosition": "positive", | ||
| "mozPositionDetail": "This API provides better access to cookies. Due to privacy concerns as outlined in issue 94, we are positive for a subset of this API which only exposes the same information available through document.cookie. At this time we're not ready to expose ServiceWorkerRegistration.cookies or implement the CookieStoreManager as proposed; we will discuss this along with the subset proposal in the appropriate standards group", |
There was a problem hiding this comment.
Please outline the privacy concerns inline or remove "Due to privacy concerns as outlined in issue 94,"
No description provided.