-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Firefox Load temporary addon not working #538
Comments
It looks like this is your first issue. Welcome! 👋 One of the project maintainers will be with you as soon as possible. We appreciate your patience. To safeguard the health of the project, please take a moment to read our code of conduct. |
I cannot reproduce your problem (I haven't tried it on Ubuntu though). The borderify extension works, as described at https://github.com/mdn/webextensions-examples/tree/main/borderify Can you show the output of the global Browser Console (https://firefox-source-docs.mozilla.org/devtools-user/browser_console/index.html)? |
For context, his "bug report" was cross-posted to https://bugzilla.mozilla.org/show_bug.cgi?id=1850464 |
Sorry cross-posted because I suspect this is also related to Firefox.
the issue is : when the add-on installing, there is not option to allow it run in the Private Window or not, and |
|
To exclude influence of customized settings, tomorrow, I will test this in a clean VM. |
At last, I found the cause of this issue is Snap (A tool to manage app installation on Ubuntu) If I moved the borderify code to $HOME dir(that's a directory in EXT4 partition), it works fine ! in previous testing, the borderify code was stored in a NTFS parition. |
and this can be reproduced in a clean VM.
|
does this mean that there's no issue in this repo but rather in Snap? |
Hey there! Just coming here to say that I had the same problem with the official Firefox Flatpak (another technology used to distribute Linux applications in a containerized environment). Changing the app's permission through Flatseal (an app to manage Flatpak permissions) and restarting the browser solved the issue: Now borderify works properly. This is clearly something to do with sandboxing of these technologies. If I had to guess, it is probably because the "Open file" dialog opens one specific file (the manifest.json), and does not give the application permission to look through the other files in the directory. |
Firefox version: 116.0.3 Ubuntu 22.04
the standard borderify addon is not working.
Reproduce steps:
"Load Temporary Add-on...",
then select the borderify manifest.json,
e.g: a page with url: https://www.mozilla.org/en-US/
in debug console, it will show a log "undefined: undefined",
I am certain that if no install the borderify addon, this log will not be printed.
however, no sure if this should be reported to Firefox or not. Thanks!
The text was updated successfully, but these errors were encountered: