Open Bug 1640117 Opened 4 years ago Updated 1 year ago

Request to access cookie: Incorrect message in console when *Content Blocking* is disabled but *Enhanced Tracking Protection* is enabled

Categories

(Firefox :: Protections UI, defect, P3)

77 Branch
defect

Tracking

()

People

(Reporter: olivier.vit, Unassigned)

Details

(Keywords: good-first-bug)

Attachments

(1 file, 2 obsolete files)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Firefox/76.0

Steps to reproduce:

Launch a new profile, go to https://www.resoneo.com/
By default, Enhanced Tracking Protection is enabled, NOT Content Blocking

Actual results:

In console I get messages like

Request to access cookie or storage on “<URL>” was blocked because it came from a tracker and content blocking is enabled
Request to access cookie or storage on “https://platform.twitter.com/widgets/widget_iframe.2a0082900…adde2d7b849b06a0bb.html?origin=https%3A%2F%2Fwww.resoneo.com” was blocked because it came from a tracker and content blocking is enabled

Indeed cookies are blocked on that request, but because of Enhanced Tracking Protection being enabled, not because of Content Blocking

This message is inaccurate and misleading to developers willing to understand what is happening and how Firefox Content Blocking may affect their site usability and behavior

Expected results:

It should say

Request to access cookie or storage on “https://platform.twitter.com/widgets/widget_iframe.2a0082900…adde2d7b849b06a0bb.html?origin=https%3A%2F%2Fwww.resoneo.com” was blocked because it came from a tracker and enhanced tracking protection is enabled

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Protections UI

I would agree with this. At one point we were calling it "content blocking" but the name has since changed to "enhanced tracking protection", this is likely an artifact from then.

These strings should be changed: https://searchfox.org/mozilla-central/source/netwerk/locales/en-US/necko.properties#40,43,45

Severity: -- → S4
Keywords: good-first-bug
Priority: -- → P3
Assignee: nobody → ash153311
Attachment #9154431 - Attachment description: Bug 1640117 Change message in console for blocking contents from centent blocking to enhanced tracking protection → Bug 1640117 Change message in console for blocking contents from content blocking to enhanced tracking protection
Attachment #9154431 - Attachment description: Bug 1640117 Change message in console for blocking contents from content blocking to enhanced tracking protection → Bug 1640117 Change message in console for blocking contents from content blocking to enhanced tracking protection r=flod
Attachment #9154431 - Attachment is obsolete: true
Attachment #9154496 - Attachment description: Bug 1640117 Change message in console for blocking contents from content blocking to enhanced tracking protection. r=flod → Bug 1640117 Change message in console for blocking contents from content blocking to enhanced tracking protection.
Pushed by nbeleuzu@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/cf9b81801abc
Change message in console for blocking contents from content blocking to enhanced tracking protection. r=nchevobbe,dimi
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Flags: needinfo?(ash153311)

Should I just add new ids with maintaining previous ids to avoid testfailed?

Flags: needinfo?(ash153311)

There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:ash153311, could you have a look please?
For more information, please visit auto_nag documentation.

Flags: needinfo?(ash153311)
Attachment #9154496 - Attachment is obsolete: true
Assignee: ash153311 → nobody
Status: ASSIGNED → UNCONFIRMED
Ever confirmed: false
Flags: needinfo?(ash153311)

hi, i am working on this bug :) Please assign me !

Assignee: nobody → soniasingla.1812
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true

This good-first-bug hasn't had any activity for 6 months, it is automatically unassigned.
For more information, please visit auto_nag documentation.

Assignee: soniasingla.1812 → nobody
Status: ASSIGNED → NEW
Assignee: nobody → soniasingla.1812
Status: NEW → ASSIGNED

This good-first-bug hasn't had any activity for 2 months, it is automatically unassigned.
For more information, please visit auto_nag documentation.

Assignee: soniasingla.1812 → nobody
Status: ASSIGNED → NEW

Hello! I'm an Outreachy applicant and I'd love to work on this bug. May I be assigned please?

Flags: needinfo?(prathikshaprasadsuman)

I am an outreachy applicant.
Is this still open? I would like to work on it

Flags: needinfo?(mtigley)

I am an outreachy applicant.
Is this still open? I would like to work on it

It looks like there is already a patch that's been approved. Sonia, is there anything else that needs to be done to get this landed?

Flags: needinfo?(mtigley) → needinfo?(soniasingla.1812)

It should be ready to land :)

Flags: needinfo?(soniasingla.1812)

Hi, I'm Ayesha Solanki, an Outreachy applicant. I would like to contribute on this issue. Can you assign it to me?

Assignee: nobody → soniasingla.1812
Status: NEW → ASSIGNED
Flags: needinfo?(prathikshaprasadsuman)

The bug assignee is inactive on Bugzilla, so the assignee is being reset.

Assignee: soniasingla.1812 → nobody
Status: ASSIGNED → NEW
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: