Complete CookieManager API
Bug #1556287 reported by
Chris Coulson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Oxide |
Triaged
|
Low
|
Alberto Mardegan | ||
| webapps-sprint |
Triaged
|
Undecided
|
Alberto Mardegan | ||
Bug Description
The CookieManager is a bit of a mess right now:
- It's not complete - it's exposes the bare minimum of calls required for online accounts, but the choice of exposed calls seems arbitrary.
- It's not a proper async API - it returns request IDs and relies on signal handlers for completion callbacks. This has always seemed a bit strange to me.
We should fix this.
| Changed in oxide: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| Changed in oxide: | |
| assignee: | nobody → Alberto Mardegan (mardy) |
| Changed in webapps-sprint: | |
| milestone: | none → sprint-20 |
| assignee: | nobody → Alberto Mardegan (mardy) |
| status: | New → Triaged |
| Changed in webapps-sprint: | |
| milestone: | sprint-20 → backlog |
To post a comment you must log in.
