Open Bug 1376611 Opened 7 years ago Updated 2 years ago

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

Categories

(WebExtensions :: General, defect, P3)

55 Branch
defect

Tracking

(firefox-esr52 affected)

Tracking Status
firefox-esr52 --- affected

People

(Reporter: yfdyh000, Unassigned)

References

Details

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.
Status: UNCONFIRMED → NEW
Has STR: --- → yes
Component: Tracking Protection → WebExtensions: Untriaged
Ever confirmed: true
Product: Firefox → Toolkit
STR: 1-2. Change privacy.trackingprotection.enabled to true in about:config.
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
I think we've discussed this before, ni'ing myself to find the dupe
Severity: normal → enhancement
Flags: needinfo?(amckay)
Priority: -- → P5
Whiteboard: [design-decision-needed]
Ah I was thinking about bug 1308640 which fixed it for fetch. It looks like this is opening an iframe to gmail though?
Flags: needinfo?(amckay) → needinfo?(mixedpuppy)
Priority: P5 → P3
Whiteboard: [design-decision-needed]
As of bug 1345158, the extensions can now check to see if trackingProtectionMode is enabled and at least raise a warning to the user as documented at: https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/privacy/websites
Adding https://mail.google.com/* to permissions gets past the never loading issue, but it still doesn't get messages as it does with TP off. I don't see any messages about anything being blocked once I've done that, but it seems that something is. Maybe François has some idea why TP might block something, but no logging appears about it.
Flags: needinfo?(mixedpuppy) → needinfo?(francois)
Further info. appcache is used by the addon, and there are failures around that. however, those failures happen with tp off, and the extension appears to work in that case. I wonder if TP does anything around appcache (e.g. loading something appcached that might not be in permissions).
(In reply to Shane Caraveo (:mixedpuppy) from comment #6) > Maybe François has some idea why TP might block something, but no logging > appears about it. I don't have any ideas about why it's happening, but if it's happening, it's probably a bug :) If you want to confirm that TP is the one blocking the resource, you can enable the MOZ_LOG debugging: MOZ_LOG="UrlClassifierDbService:5,nsChannelClassifier:5" (see https://wiki.mozilla.org/Security/Tracking_protection#QA) (In reply to Shane Caraveo (:mixedpuppy) from comment #7) > Further info. appcache is used by the addon, and there are failures around > that. however, those failures happen with tp off, and the extension appears > to work in that case. I wonder if TP does anything around appcache (e.g. > loading something appcached that might not be in permissions). Appcache is not currently covered by tracking protection (see bug 1262339).
Flags: needinfo?(francois)
This problem is still present on latest Nightly builds.
Depends on: 1458374
Product: Toolkit → WebExtensions

Is this still an issue?

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.