Closed Bug 1544557 Opened 1 year ago Closed 1 year ago

shield icon showing in standard, but not strict

Categories

(Firefox :: Protections UI, defect)

defect
Not set
normal

Tracking

()

RESOLVED INVALID
Tracking Status
firefox68 --- affected

People

(Reporter: ewright, Unassigned)

References

(Blocks 1 open bug)

Details

STR:

  • start a fresh profile using Nightly v68
  • open about:preferences#privacy, observe it is set to "standard"
  • open a new tab, visit bugzilla.mozilla.org
  • observe the shield animation in address bar.
  • open the control panel "trackers" and "cookies" are both listed (trackers is not listed as blocked, just that a tracker exists)
    • click the cookies label, notice the google-analytics cookie listed as blocked
    • click the trackers label, notice a google-analytics tracker listed, not blocked.
  • go back to about:preferences
  • change the category to "strict"
  • refresh the bugzilla tab
  • the shield is no longer there
  • open the control panel, only "cookies" is listed
    • click the cookies label, notice the google-analytics cookie is gone

ER:

  • in strict mode "trackers" should be listed and should be labeled "blocked"
  • the shield should show when a blocking event happens

It seems that something is going on with google-analytics.com being the only block-able content, and is classified as both a tracker and a tracking cookie. However, when it is (presumably) being blocked as a tracker, all evidence of it disappears.

Is the DNT: 1 header set in the HTTP request when fetching the Bugzilla page? Mozilla properties use the DNT header to decide whether to use GA, and choose to not use GA when the UA sends a DNT: 1 header.

Flags: needinfo?(ewright)

(In reply to :Ehsan Akhgari from comment #1)

Is the DNT: 1 header set in the HTTP request when fetching the Bugzilla page? Mozilla properties use the DNT header to decide whether to use GA, and choose to not use GA when the UA sends a DNT: 1 header.

Indeed, I didn't realize that enabling tracking protection automatically turns on "Do Not Track" feature. I can't seem to find documentation that this is the case. It's especially confusing because privacy.donottrackheader.enabled is false.

Flags: needinfo?(ewright)

Yeah this is a rather old change (bug 1258033).

So is there anything unexpected happening here?

Flags: needinfo?(ewright)

(In reply to :Ehsan Akhgari from comment #3)

Yeah this is a rather old change (bug 1258033).

So is there anything unexpected happening here?

Nope, I suppose it's not unexpected. I'll chat with UX about this though, since we don't have any indication that DNT is turned on.

Status: NEW → RESOLVED
Closed: 1 year ago
Flags: needinfo?(ewright)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.