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
Can't save setting in FF67 #25
Comments
Same for me, FF 66.0.3 on Ubuntu 19.04 x86_64 |
Same for me, FF 66.0.3 on macOS 10.13.6. |
Now it works. |
It does not work, again. (same as @ooker777) |
broken again FF 67.0 (Ubuntu), Format Link 3.0.1 |
It seems to occur when create a new environment. I commented that on #20. |
Ditto -It does not let you save settings; there are no default settings; It does nothing at this point. Format Link v3.0.1 in FF 64.0.4 Windows |
Oddly, I have one Firefox instance where FormatLink does still work perfectly: Firefox 67.0.4, Windows 10, FormatLink v3.0.1 (May 7, 2019 - automatic updates set to Default rather than On). I wish I knew where the difference was between this and my other installations that don't work. |
Reproduced in Firefox 70.0b14 (64-bit). I checked stderr log of
It seems that the line 27 of Lines 27 to 29 in 3291a7c
EDIT: There have already been a PR to fix this: #28. |
Quick workaround
By this workaround, the extension started to work as expected in my environment. |
I don't understand this workaround - what am I supposed to be changing? Using FF74, I can't save any settings. |
@nopoz You are supposed to change (initialize) the internal storage of FormatLink addon. Currently FormatLink has a bug and it cannot initialize its internal storage through plugin's usual setting page. The workaround above is a procedure for doing manual initialization of the storage. |
Sorry for being late, I added the fix as commented at #25 (comment) and published version 4.0.2. |
Sorry for not responding. I'm closing this since it's too old. |
I try this:
with and without checking
Create submenus
, but it resets after saved. The panel is blank:The text was updated successfully, but these errors were encountered: