Proposal: add cookies.removeAll() method #690
Conversation
Initial draft
aselya
changed the title
|
|
||
| ### Objective | ||
|
|
||
| This new API addresses two workflows for developers: |
There was a problem hiding this comment.
It seems that the examples you provided is how extensions would have to achieve the functionality these days. Can you rephrase to emphasize that? To someone not deeply aware of the details, it can be read as part of the proposal for something net, not of existing behavior.
There was a problem hiding this comment.
Updated the language and I would appreciate feedback on if my rephrasing addresses the issue you brought up.
aselya
changed the title
|
Wanted to add some context to why I'm proposing this. When working on updating the implementation of the cookies API to include the Despite the behavior being a bug, I found the ability to delete multiple cookies with the same call to be quite useful and thought it made sense to add it to the cookies api. |
Updating parameters to explicitly reference cookies.remove Co-authored-by: Rob Wu <[email protected]>
Add more related issues Update the motivation language to reflect the related issues.
Add link to bug in the motivation
Update the objective to be more explicit about the pain point for developers.
Update language in objective.
Update language to make `{}` and error
Update case: `partitionKey : {}` to match `cookies.getAll`
Update requirements of details object.
Added more detailed description of host permissions impact on API call
Made update to remove the `top-level site` as an optional stand alone parameter.
There was a problem hiding this comment.
This looks good to me! Adding @rdcronin to make sure he is happy before we land.
Proposal introducing a new API cookies.removeAll()