-
Notifications
You must be signed in to change notification settings - Fork 24
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
Request #30
Comments
Seems like a cool idea. I don't know how the script is supposed to work, so idk if I can make it work. I refactored it with the usual changes for compatibility with fx-autoconfig, but I don't see any change (whether I use the old version you linked, or my refactored version of the updated version). Not sure what it's supposed to do or under what circumstances. Doesn't seem to matter whether I log into fx account or not. By manually invoking some of the functions I can force it to show a gray overlay, but no visible input field, and it doesn't happen automatically at startup. There's no documentation so it's hard to tell what the intention is. For working code I can usually figure things out on my own, but it doesn't seem to be working at all, at least with my environment and the latest Nightly. Maybe I'm using it wrong or there are some requirements I'm not aware of. So I will need some pretty detailed info on how this is supposed to work. |
Hi there! Thank you for answering me. The script was born long time ago, having only one function: At Firefox startup, the script created a colored screen (filling the whole Firefox screen), and a small centered window asked for a password (if I'm not wrong, this password is the same one used in Firefox to deal with other passwords, the so called master-password). In the begging this script was too primitive, and a simple ESC command was capable to skip or to bypass the blocking password screen. After the original primitive script, most of the new sub-functions included in updated and upgraded versions are line codes avoiding to skip or to bypass the blocking password screen. So along the time, the script really has not developed new functions, but it has incorporated a lot of new rules against keys or commands capable of bypassing the lock screen. In this context, what do we expect from you? As a second stage, if by chance you want and you can do more than adapting this script, if you want to add new functions and develop further this script, then we'll consider that a big plus, a huge bonus. It'll be amazing for us if you fork this script, and if you keep this script in your repo, updated and upgraded with new functions. Thank you in advance! |
Sorry to ask again, is there any chance you can make the latest version of this script work with the latest fx-autoconfig? If you can't do that, please feel free to close this issue. Thank you in advance : ) |
I might be able to eventually but I'm very busy. This github repo is just a hobby, on top of a full-time job running a business, plus other intellectual and charitable commitments. I have not had much time to invest in Firefox autoconfig scripts lately. |
I totally understand! |
THIS IS JUST A REQUEST
Hi!
This JS script creates a kind of password screen when Firefox starts.
The original script was adapted to be compatible and to work with MrOtherGuy fx-autoconfig, following these simple rules:
However, the script was updated to this new version. And it's not working with MrOtherGuy fx-autoconfig (the rules mentioned above are not working in the new version).
You have an incredible JS repo compatible with MrOtherGuy fx-autoconfig. So please, if possible, my requests are:
Can you adapt the latest updated version of the JS script in order to work with MrOtherGuy fx-autoconfig?
Even better: Please can you write a new JS script fully compatible with MrOtherGuy fx-autoconfig, having as main function the creation of a kind of password screen (or similar) when Firefox starts? It'll be great if you can do that, because that will help us (users of this JS script) to always keep the latest working and updated script.
Thank you
The text was updated successfully, but these errors were encountered: