If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

https://mail.google.com/” was blocked because tracking protection is enabled

NEW
Unassigned

Status

()

Toolkit
WebExtensions: Untriaged
P5
enhancement
3 months ago
10 days ago

People

(Reporter: YF (Yang), Unassigned, NeedInfo)

Tracking

55 Branch
Points:
---

Firefox Tracking Flags

(firefox-esr52 affected, firefox54 affected, firefox55 affected, firefox56 affected, firefox57 wontfix)

Details

(Whiteboard: [design-decision-needed])

(Reporter)

Description

3 months ago
STR:
1. Install or load the https://addons.mozilla.org/firefox/addon/fastest-notifier-for-gmail/versions/?page=1#version-0.3.0
2. Make sure Gmail is logged in.
3. Click the toolbar button to activate its panel.


Actual results:
1. Loading at all the time.
2. Seen an message in debugging the add-on: The resource at “https://mail.google.com/” was blocked because tracking protection is enabled panel.html


Expected results:
1. Normal loading.
2. No wrong message.
(Reporter)

Updated

2 months ago
Status: UNCONFIRMED → NEW
Has STR: --- → yes
Component: Tracking Protection → WebExtensions: Untriaged
Ever confirmed: true
Product: Firefox → Toolkit
(Reporter)

Comment 1

2 months ago
STR:
1-2. Change privacy.trackingprotection.enabled to true in about:config.
(Reporter)

Comment 2

2 months ago
The problem also occurs for https://addons.mozilla.org/firefox/addon/gmail-panel-and-notifier/
status-firefox54: --- → affected
status-firefox55: --- → affected
status-firefox56: --- → affected
status-firefox-esr52: --- → affected
Summary: “https://mail.google.com/” was blocked message with Gmail™ Notifier + 0.3.0 → “https://mail.google.com/” was blocked because tracking protection is enabled

Comment 3

10 days ago
I think we've discussed this before, ni'ing myself to find the dupe
Severity: normal → enhancement
status-firefox57: --- → wontfix
Flags: needinfo?(amckay)
Priority: -- → P5
Whiteboard: [design-decision-needed]
You need to log in before you can comment on or make changes to this bug.