Enable history flooding prevention in Release
Categories
(Toolkit :: Places, task, P3)
Tracking
()
People
(Reporter: mak, Assigned: mak)
References
(Blocks 1 open bug)
Details
(Whiteboard: [sng])
Attachments
(1 file)
We didn't get unexpected reports from Nightly, so let's proceed enabling the feature in Release.
Updated•6 months ago
|
Assignee | ||
Comment 1•3 months ago
|
||
Flooding prevention has been enabled for a few months in Nightly, it
is a first step in preventing pages from sending an excessive amounts
of visits to history, that may have both performance and ranking
consqeuences.
Updated•3 months ago
|
Comment 4•3 months ago
|
||
I assume we'll want a relnote for this. Please go ahead and add a relnote-firefox
nomination if that's the case.
Assignee | ||
Comment 5•3 months ago
•
|
||
From the user point of view nothing should change in normal conditions, as well as for normally behaving sites. thus I don't think it's necessary.
This is just some precautions against misbehaving web sites.
After discussion, let's put up a note as an heads-up.
Assignee | ||
Comment 6•3 months ago
|
||
Release Note Request (optional, but appreciated)
[Why is this notable]: As an heads-up, so related issues can be noted more easily
[Affects Firefox for Android]: no
[Suggested wording]: A safeguard has been put in place to prevent history from being overwhelmed by numerous consecutive visits from a single origin.
[Links (documentation, blog post, etc)]: not yet
Updated•25 days ago
|
Description
•