Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doesn't work with First-Party Isolation enabled in Firefox #36

Open
yaxunema95 opened this issue Jul 28, 2020 · 2 comments
Open

Doesn't work with First-Party Isolation enabled in Firefox #36

yaxunema95 opened this issue Jul 28, 2020 · 2 comments

Comments

@yaxunema95
Copy link

In Firefox (using 78.0.2 on Arch Linux), with First-Party Isolation (FPI) enabled (privacy.firstparty.isolate = true in about:config), the extension will interrupt downloads, but won't open them in Persepolis, so downloads will never start.

FPI restricts access to cookies, site storage, etc. by domain, though one of the permissions of the Persepolis extension is "Access your data for all websites". I'm not sure what's supposed to take priority here, but it looks like FPI--the extension is looking for cookies (required for some downloads) and Firefox is blocking access to them.

@JafarAkhondali
Copy link
Member

Duplicate #20.
Sending URLs to Persepolis without cookies will result in in ambiguous behavior. It would a better idea if FF could allow exceptions in their list.

@yaxunema95
Copy link
Author

Duplicate #20.

Wow, how'd I miss that?

It would a better idea if FF could allow exceptions in their list.

Agreed. Not sure what the best suggestion to FF devs would be. FPI is a huge win for privacy, and it makes sense that web extensions are considered third parties. Download manager integrators are an odd special case.

Forgive me for spitballing here, but I could suggest the following on FF's Bugzilla as possible options:

  1. Have the extension permission "Access your data for all websites" override FPI (i.e. leave it to the user to pay attention to permissions).
  2. Add a privacy.firstparty.isolate.include_extensions preference to toggle the above option.
  3. Add some sort of additional per-extension trust option, similar to "Allow in private windows".

The ultimate solution would be per-domain/extension exceptions/overrides/profiles for all preferences, but we might be a long way from that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants