Closed Bug 1487178 Opened 6 years ago Closed 6 years ago

Ensure that the Firefox configuration is up to date for the Content Blocking project

Categories

(Firefox :: General, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 63
Tracking Status
firefox63 --- fixed

People

(Reporter: ehsan.akhgari, Assigned: ehsan.akhgari)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

The desired behavior we've agreed on right now is as follows:

The New Content Blocking UI is enabled
Third party cookies UI is enabled
Fastblock UI is enabled
Trackers (TP) UI is enabled.
FastBlock itself is disabled
CookieBehavior setting is unchanged (i.e. Tracking Cookies isn't enabled by default)
Tracking Protection is on only in private mode.
For users who have not changed any settings, the UI Onboarding Tour should only show up in Private Mode when they click the Show me how it works button.
Users who turn on FastBlock OR Tracking Cookies OR Tracking Protection in regular mode will see the UI Tour in Normal mode (variation 1 or 2 depending on their settings).
The Report Breakage button should exist
With some small tweaks:

The New Privacy Panel UI is enabled
The content blocking backend pref is ON
Third party cookies UI is enabled
Fastblock(Slow Loading Trackers) UI is enabled
Trackers (TP) UI is enabled.
FastBlock feature itself is disabled in Beta (but enabled in Nightly, (TBD gradual rollout in Beta) )
CookieBehavior setting is unchanged (i.e. Tracking Cookies isn't enabled by default)
Tracking Protection is on only in private mode.
For users who have not changed any settings, the UI Onboarding Tour should only show up in Private Mode when they click the Show me how it works button.
Users who turn on FastBlock OR Tracking Cookies OR Tracking Protection in regular mode will see the UI Tour in Normal mode (variation 1 or 2 depending on their settings).
The Report Breakage button should exist
Comment on attachment 9005509 [details] [diff] [review]
Ensure that the Firefox configuration is up to date for the Content Blocking project

Review of attachment 9005509 [details] [diff] [review]:
-----------------------------------------------------------------

Thanks!
Attachment #9005509 - Flags: review?(jhofmann) → review+
https://hg.mozilla.org/integration/mozilla-inbound/rev/07abec90d85cb065f17ddb8f75adcc24be5f5f1f
Bug 1487178 - Ensure that the Firefox configuration is up to date for the Content Blocking project; r=johannh
https://hg.mozilla.org/mozilla-central/rev/07abec90d85c
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 63
With some small tweaks:

The New Privacy Panel UI is enabled
The content blocking backend pref is ON
Third party cookies UI is enabled
Fastblock(Slow Loading Trackers) UI is enabled
Trackers (TP) UI is enabled.
FastBlock feature itself is disabled in Beta (but enabled in Nightly, (TBD gradual rollout in Beta) )
CookieBehavior setting is unchanged (i.e. Tracking Cookies isn't enabled by default)
Tracking Protection is on only in private mode.


ddabbs: Does your tweaked recap above mean that the user would have the following in the prefs UI when this lands?


Content Blocking 
( *) ON

    [ ]  Slow-Loading Trackers
    
    [X]  All Detected Trackers

        (*) Only in private windows
        ( ) Always

    [ ] Third-Party Cookies
Correct.
Thank you Ehsan. Further clarification. Those settings are what's intended for FF 65? Or for 63?
Sorry I see the Target is 63. Duh.
My Nightly refreshed this morning and I noticed in the 'shield menu' that "Slow-loading Trackers" were blocked on one of my morning reads. Have the Content Blocking default preference settings changed for this to enable blocking slow-loading?
(In reply to DDabbs from comment #10)
> My Nightly refreshed this morning and I noticed in the 'shield menu' that
> "Slow-loading Trackers" were blocked on one of my morning reads. Have the
> Content Blocking default preference settings changed for this to enable
> blocking slow-loading?

Yes, see bug 1480443.  Also, random bugs aren't a forum for responding to user's questions, sorry about that.  We use these bugs in order to organize Firefox development.  I would appreciate if you could study https://bugzilla.mozilla.org/page.cgi?id=etiquette.html before commenting further.  :-)  Thanks!
Blocks: 1580351
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: