![]() ![]() Then again, how should I proceed to update Firefox when a new version arises? Because this is not acceptable and multiple profiles is a (great) feature. So, again, the issue is not the Firefox installation itself, but simply the secondary profile. I am writing this in my primary profile, the one I used to update Firefox 95.0.1 and that is working fine. ![]() Since it's only one of the profiles that isn't working under the updated Firefox, and since the issue is clearly the version stated somewhere inside that profile, how can I edit those minVersion and maxVersion variables so that it (the troublesome profile) accepts to be opened by the new version? Is it is a JSON file, an INI file, or some other kind of file, and which one, and is it pure text or hexadecimal or what? Learn about Mozilla and the issues that matter to us. Get the customizable mobile browser for Android smartphones. 2015-37 CORS requests should not follow 30x redirections after preflight. Release notes for each version of Firefox. 2015-38 Memory corruption crashes in Off Main Thread Compositing. 2015-39 Use-after-free due to type confusion flaws. 2015-40 Same-origin bypass through anchor navigation. Unfortunately only for one of the profiles, and the other one didn't quite "get" that it would now work with a 95.0.1 application rather than the old 95.0 one. 2015-41 PRNG weakness allows for DNS poisoning on Android.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |