1807559 - Set ETP level to be more strict on a per-site basis

Status: NEW

(Firefox for Android :: Privacy, enhancement)

Description

[Chris Peterson [:cpeterson]]

From github: https://github.com/mozilla-mobile/fenix/issues/20460.

What is the user problem or growth opportunity you want to see solved?

Currently ETP is a global setting that applies to all sites you visit, with the option of exempting certain sites where no ETP protections will be applied. I think it would be valuable to have the option to set ETP to be stricter on a per-site basis in a similar way to cookie permissions that exist in Page Info -> Permissions on desktop Firefox.

How do you know that this problem exists today? Why is this important?

There is no method I'm aware of on fenix to customize this setting. You can observe the global nature of the ETP setting through the following procedure: Visit a website -> Tap the ETP shield on the address bar -> Select "Protection Settings" -> Change your settings (ex Standard -> Strict) -> Back out of the menu -> Open a different site -> Tap the ETP shield on the new site -> Select "Protection Settings" -> Observe that your changes from the previous site have persisted.

This is important because there are some websites that use first party cookies to track users on their page and to modify page features or behavior on the basis of this tracking. There are also many websites where first party cookies are necessary for use of the site. Current ETP settings constrain user choice on this aspect of site behavior. Users currently face a choice where they must either:

1. Set their ETP to be as strict as needed for a minority of websites, but manually opt out (and therefore have no ETP) on sites where first party cookies are desired

OR

2. Set their ETP to the level they would like for default sites, and have to tolerate the undesirable behavior by a minority of visited sites.

With this feature users would have more control over site behavior.

Who will benefit from it?

Any user who visits sites that have a mix of desirable and undesirable first party cookie behavior.

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.