Bug 1698845 Comment 3 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to Meridel [:meridel] from comment #2)
> I don't think that we actually need to update the string here? Please see this slide: 
> https://docs.google.com/presentation/d/1OWIVLOVyWHmqr385W6KSA_HupFa7m3XfCwmkKJZacBs/edit#slide=id.g79fcbdcd30_0_8
> 
> 
> All bullet points in the ETP section imply that protections will be provided in all windows (normal and private). If a protection is ONLY offered in private windows (like Tracking content), that is called out as an exception. Is that right?

Sorry if that wasn't clear, this is the case here. We're adding protections in private mode that non-private windows will not be getting (for now). So we'd like to call this out as an exception.

Currently, in Release, the description for the protection we're offering in Standard mode is "Cross-site tracking cookies", while the description in Strict (and Standard in Nightly) is "Cross-site cookies". An accurate representation would be:

Cross-site tracking cookies
(All) Cross-site cookies in Private Windows

Though we also discussed whether this distinction was meaningful enough to the average user to warrant a string change at all.

Does that help? Otherwise feel free to ping me on Slack :)
(In reply to Meridel [:meridel] from comment #2)
> I don't think that we actually need to update the string here? Please see this slide: 
> https://docs.google.com/presentation/d/1OWIVLOVyWHmqr385W6KSA_HupFa7m3XfCwmkKJZacBs/edit#slide=id.g79fcbdcd30_0_8
> 
> 
> All bullet points in the ETP section imply that protections will be provided in all windows (normal and private). If a protection is ONLY offered in private windows (like Tracking content), that is called out as an exception. Is that right?

Sorry if that wasn't clear, this is the case here. We're adding protections in private mode that non-private windows will not be getting (for now). So we'd like to call this out as an exception.

Currently, in Release, the description for the protection we're offering in Standard mode is "Cross-site tracking cookies", while the description in Strict (and Standard in Nightly) is "Cross-site cookies". An accurate representation of the Standard protections after our changes would be:

Cross-site tracking cookies
(All) Cross-site cookies in Private Windows

Though we also discussed whether this distinction was meaningful enough to the average user to warrant a string change at all.

Does that help? Otherwise feel free to ping me on Slack :)

Back to Bug 1698845 Comment 3