Closed Bug 1524873 Opened 6 years ago Closed 5 years ago

Trackers are not classified in Safe Mode

Categories

(Toolkit :: Safe Browsing, defect, P1)

defect

Tracking

()

RESOLVED FIXED
mozilla75
Tracking Status
firefox75 --- fixed

People

(Reporter: itiel_yn8, Assigned: dimi)

References

(Blocks 1 open bug)

Details

Crash Data

Attachments

(1 file, 2 obsolete files)

Not sure if this is an issue only with the icon not showing up on the URL bar, or with Content Blocking not working at all in Safe Mode.
This may very well be marked as INVALID if this is the intentional behaviour.

Johann, is the Tracking Protection component the right one for this bug?

Flags: needinfo?(jhofmann)

Oh, thanks for the nudge, this didn't appear in my triage list. Not sure what I did wrong there...

This would be the right component for these bugs, but trying it out I get the following errors logged in the console:

NS_ERROR_XPC_GS_RETURNED_FAILURE: ServiceManager::GetService returned failure code: UrlClassifierListManager.jsm:67
NS_ERROR_XPC_GS_RETURNED_FAILURE: ServiceManager::GetService returned failure code: SafeBrowsing.jsm:185

And accordingly, all of the trackers on the page are found but none are classified as trackers (see the sub-panel in the site identity popup)

Which makes me think that this is a urlclassifier issue. Dimi, can you take a look, please?

Thank you!

Component: Tracking Protection → Safe Browsing
Flags: needinfo?(jhofmann) → needinfo?(dlee)
Product: Firefox → Toolkit
Summary: Content Blocking shield icon does not appear on the URL bar in Nightly's Safe Mode → Trackers are not classified in Safe Mode
Assignee: nobody → dlee
Status: NEW → ASSIGNED
Flags: needinfo?(dlee)
Priority: -- → P1

SafeBrowsing is disabled intentionally in Bug 1134954 so Content Blocking doesn't work.

Johann, do you have any concern about this? If no, I will mark it as INVALID.

Flags: needinfo?(jhofmann)

Hmmm I find the argument presented in bug 1134954 a bit weak (something crashed to we disable it in Safe Mode). Nowadays this is affecting Content Blocking and Safe Browsing, which I would consider essential enough features that they might continue to be turned on in Safe Mode.

There's a definition of Safe Mode here: https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode

Safe Mode is a special Firefox mode that can be used to troubleshoot and fix problems. Safe Mode temporarily turns off hardware acceleration, resets some settings, and disables add-ons (extensions and themes) that might be causing problems. By comparing Firefox behavior in normal mode to its behavior in Safe Mode you may be able to pinpoint the cause of the problem.

This says "resets some settings", but doesn't really mention entirely disabling default browser features.

CC'ing other folks who might want to chime in.

Flags: needinfo?(jhofmann)

(In reply to Johann Hofmann [:johannh] from comment #4)

Hmmm I find the argument presented in bug 1134954 a bit weak (something crashed to we disable it in Safe Mode). Nowadays this is affecting Content Blocking and Safe Browsing, which I would consider essential enough features that they might continue to be turned on in Safe Mode.

I think the intention in Bug 1134954 is just to disable SafeBrowsing update, not features that using safe browsing database, which I think it makes sense because SafeBrowsing update is not something really necessary in Safe Mode.

My bad that I didn't get it in the first place, I'll check why "Disable SafeBrowsing Update" becomes "SafeBrowsing not working"...

Priority: P1 → P2

(In reply to Johann Hofmann [:johannh] from comment #4)

There's a definition of Safe Mode here: https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode

Safe Mode is a special Firefox mode that can be used to troubleshoot and fix problems. Safe Mode temporarily turns off hardware acceleration, resets some settings, and disables add-ons (extensions and themes) that might be causing problems. By comparing Firefox behavior in normal mode to its behavior in Safe Mode you may be able to pinpoint the cause of the problem.

This says "resets some settings", but doesn't really mention entirely disabling default browser features.

See https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode/history
The Mozilla Support article was recently updated to include more information. Should we also update the article to add that Content blocking/ETP and Safe Browsing features are disabled in Safe Mode?

(In reply to Alice Wyman from comment #6)

See https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode/history
The Mozilla Support article was recently updated to include more information. Should we also update the article to add that Content blocking/ETP and Safe Browsing features are disabled in Safe Mode?

You are right, this is what is happening so far, we should update that.
I am going to work on this bug this quarter, hope we can turn those features on in Safe Mode soon.

Priority: P2 → P1

(In reply to Dimi Lee [:dimi][:dlee] from comment #7)

You are right, this is what is happening so far, we should update that.
I am going to work on this bug this quarter, hope we can turn those features on in Safe Mode soon.

Thanks. I updated https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode/

Blocks: safe-mode

This patch enables SafeBrowsing in Safe Mode because features based
on SafeBrowsing are essential for Firefox(For example, Enhanced Tracking Protection).

Since Safe Browsing update is nondeterministic, we disable periodical
SafeBrowsing update to make troubleshooting easier. Manually trigger an
update via about:classifier is still enabled.

This patch enables SafeBrowsing in Safe Mode because features based
on SafeBrowsing are essential for Firefox(For example, Enhanced Tracking Protection).

Since Safe Browsing update is nondeterministic, we disable periodical
SafeBrowsing update to make troubleshooting easier. Manually trigger an
update via about:classifier is still enabled.

Last, SafeBrowsing tables provided by Google will be ignored in Safe
Mode to ensure the SafeBrowsing warnings are update-to-date.

This patch enables SafeBrowsing in Safe Mode because features based
on SafeBrowsing are essential for Firefox(For example, Enhanced Tracking Protection).

Since Safe Browsing update is nondeterministic, we disable periodical
SafeBrowsing update to make troubleshooting easier. Manually trigger an
update via about:classifier is still enabled.

Last, SafeBrowsing tables provided by Google will be ignored in Safe
Mode to ensure the SafeBrowsing warnings are update-to-date.

Attachment #9127095 - Attachment is obsolete: true
Attachment #9127096 - Attachment is obsolete: true
Pushed by dlee@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/e72506f78ff1 Enable SafeBrowsing in Safe Mode. r=gcp
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla75
Crash Signature: [@ nsUrlClassifierDBService::AsyncClassifyLocalWithFeatures]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: