Go to Waterfox and manually open the extension from your computer. Close the ZIP file and rename the extension back to XPI. Save the file and replace the version in the ZIP file with the version you just edited. If Waterfox has its own non-Firefox territory in the Roaming folder, it is hard to understand why this conflict occurs. Search for all instances of max and adjust the version to a very high number. Everything ported from Classic to Current without a hitch, only saved logins refuse to. Hours spent on browsing different websites, forums, waterfoxs github issues, and Im stuck with this shit. However, this is designed so that two instances cannot share the same profile. 3rd party tools (none support Waterfox Classic, or are obvious scams/require accounts and/or upload stuff to cloud) I am fuming. ini launch (which no normal user would get near, I think), to allow a second instance of Firefox to run. To make Waterfox Current stand out from the crowd, it was compiled with many optimizations so that it will perform faster and. The Firefox source code was taken and compiled in order to specifically run for 64-Bit Windows computers. I suspect this is something to do with not wanting to set up an authentication token for the fork, and relying on the original Firefox one.ĮDIT: For clarity, the 'other' Firefox running at the time of the screen shot is Waterfox Classic.ĮDIT 2: According to the forums, you need to add a flag to the. Waterfox provides you with a high-performance browser 64-Bit version of Mozilla Firefox. Seems all the forks of Firefox have this problem of root-level identification as Firefox, and not whatever the derivative browser is. I downloaded and installed the latest Firefox, set 'Launch now' at the end of the install procedure and got this: Turns out, as I suspected, that Firefox cannot live with Waterfox classic.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |