Closed Bug 1203326 Opened 9 years ago Closed 9 years ago

Disable push quotas

Categories

(Core :: DOM: Notifications, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox43 --- affected

People

(Reporter: lina, Unassigned)

References

Details

If we're going to ship background-only push in 42, we should disable quotas. Otherwise, a site can receive at most 16 messages before its subscription is killed.

The quota is replenished when the user returns to the site, but, without notifications, sites can't encourage users to do that.
wouldnt the user just need to go back to the main site to have the subscription renewed.
I don't think that this is a good idea, without some sort of visible indicator, the background activity could persist.  That makes the tracking problem worse, not better.  As dougt says, if the user returns, then the site will be fine.
How would the user know they need to return to the site?
(In reply to Martin Thomson [:mt:] from comment #2)
> I don't think that this is a good idea, without some sort of visible
> indicator, the background activity could persist.

I think it would be helpful to have this either way.
The problem that the quota is designed to mitigate is *more* relevant without notifications, not less.  Why would we remove the protection that we have?
Seems that in the absence of some user-visible notification that the Push quota has been reached (which I think is a bad idea at this point, we just have to rely on a user that expects something to happen actually going back to the site, since that is the only way they can actually tell something has happened. All push systems start with quotas, even if the user can't tell it is there.
Depends on: 1201571
We'll address this in Product Owners meeting.
Blocks: 1201571
No longer depends on: 1201571
Per Edwin, we're leaving the quota in place.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.