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

manifest.common.json: disallow running in incognito mode #705

Merged
merged 2 commits into from
Jul 10, 2019
Merged

manifest.common.json: disallow running in incognito mode #705

merged 2 commits into from
Jul 10, 2019

Conversation

Mikaela
Copy link
Contributor

@Mikaela Mikaela commented Apr 2, 2019

I am not entirely sure this came to the correct spot as there are no examples that I could see and I think incognito could logically be a permission.

Requested in #704 (comment). Closes #704

Copy link
Member

@lidel lidel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @Mikaela! I tested it with Firefox Nightly and worked as expected.

There is one nuance to address here: we need to set minimal version of Firefox to be 67.
If we ship this with <67, then extension will fail to load with this error:

Error: unknownError: Could not install add-on at '/home/lidel/project/ipfs-companion/add-on': Error: Extension is invalid

Can you please update this PR and bump the minimal versions in below places to 67?

https://github.com/ipfs-shipyard/ipfs-companion/blob/8048f9f3a1bda5cf13987236f6d91d4136521ccf/add-on/manifest.firefox.json#L11

https://github.com/ipfs-shipyard/ipfs-companion/blob/8048f9f3a1bda5cf13987236f6d91d4136521ccf/.babelrc#L10

This way we will ensure update will get in effect only when user updates to Firefox 67.

ps. don't worry about failing Travis tests, they fail because WebExtension linter is not aware of updates in Firefox 67. We will update it before this PR is merged.

@Mikaela
Copy link
Contributor Author

Mikaela commented Apr 8, 2019

Done, however this may drop privacy.resistfingerprinting users to old version until Firefox ESR updates to 67 or higher thanks to Firefox bug 1394448: Cannot install Addon withprivacy.resistFingerprinting==true.

As a workaround I think I am switching back to the beta channel which I left only because it doesn't work with Firefox Sync resulting me either not having IPFS Companion at all or having two of them.

@lidel
Copy link
Member

lidel commented Apr 8, 2019

Thank you @Mikaela

You raised a valid concern: we don't want to force people to switch to different browser channel if they want to use Companion Beta. Companion Beta should always work with Stable Firefox.

I believe a safe way to ship this is to park this PR until Firefox 67 lands in Stable by the end of this quarter. Firefox 68 will become ESR in July soon after that:

release-overview-high-res d3c9788f2dd1

Does this sound ok?

@Mikaela
Copy link
Contributor Author

Mikaela commented Apr 9, 2019

I think it sounds ok (but I am staying in the beta as I am curious enough and following enough issues).

I think you may be overestimating my skills/abilities/knowledge on Firefox/webextensions/development and spent a long time staring at documentation after you asked me to look into this in #704 (without which I wouldn't have done anything).

Mikaela added 2 commits April 17, 2019 14:26
Closes #704

Signed-off-by: Mikaela Suomalainen <mikaela+git@mikaela.info>
Signed-off-by: Mikaela Suomalainen <mikaela+git@mikaela.info>
@lidel
Copy link
Member

lidel commented Jul 10, 2019

Firefox 68 landed to ESR channel, let's merge this! :)

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

Successfully merging this pull request may close these issues.

How to handle Incognito Mode?
2 participants