Closed
Bug 1511933
Opened 6 years ago
Closed 6 years ago
We show the "Blockable content detected on this site" label even when a first-party cookie has been accessed
Categories
(Firefox :: Site Identity, defect, P4)
Firefox
Site Identity
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: ehsan.akhgari, Unassigned)
References
Details
STR:
1. Go to http://example.com.
2. Open the web console.
3. Type document.cookie and press Enter.
4. Open the Control Centre.
The "Blockable content detected on this site" label should not appear on the control centre.
Comment 1•6 years ago
|
||
I think this is a WONTFIX.
1) Sometimes, IMO, it helps both users and developers to not alter the UI too much for all edge cases one might encounter.
2) If you want to be super precise about it, any cookie is blockable by content blocking (you just have to go to custom and select block all cookies). So if we changed this someone could file a new bug arguing that it should say "Blockable content detected" and they wouldn't be wrong.
Thoughts?
Updated•6 years ago
|
Priority: -- → P4
Comment 2•6 years ago
|
||
Ehsan is proposing that in the case where only first party cookies are on a page, instead of saying "Blockable content detected on this site", we say "No blockable content detected on this page". But if we do this, we also lose the Cookies section in Control Center, which means we lose the Cookies subpanel, and there is no way for a user to see the Cookies if they wanted to. This was designed with the intent that the cookies subpanel always existed if cookies existed. So this proposal goes against the design. However, it is a stretch to say that first party cookies are blockable content. We shouldn't be encouraging our users to block all cookies.
This should be considered if we revamp the UI in the future.
Comment 3•6 years ago
|
||
Given that there are valid arguments for not doing this right now I'll close it. If we revamp the UI in the future it will be all different anyway.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•