Closed
Bug 788951
Opened 13 years ago
Closed 9 years ago
Need notification mechanism for cookies
Categories
(Firefox Graveyard :: SocialAPI, defect)
Firefox Graveyard
SocialAPI
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: markh, Unassigned)
Details
(Whiteboard: [needs-api-change])
It would be ideal if social content could be notified about changes to its cookies so the sidebar and worker could efficiently detect when the user logs into or out of the provider's main site and adjust accordingly. Similarly, it would also help efficiently detect entering and exiting private browsing.
Currently providers are simulating this by polling for cookies each second which seems extremely inefficient, may impact the responsiveness of the UI and may suffer if Firefox becomes more aggressive about throttling setTimeout/setInterval timeouts.
Comment 1•13 years ago
|
||
The previous API for this was the "social.cookie-changed" notification sent by the WorkerAPI (see leftover compat code in WorkerAPI.jsm, and discussions in bug 774003).
To do this cleanly, I think an additional cookie service API for watching changes for a specific domain would be useful.
Reporter | ||
Updated•13 years ago
|
OS: Windows 7 → All
Hardware: x86_64 → All
Whiteboard: [needs-api-change]
Comment 2•9 years ago
|
||
deprecation in fx51
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Product: Firefox → Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•