![]() ![]() Anything not specified in the profile will track the compiled-in defaults of whichever application version you're launching. The profile only contains differences to default settings, as well as what can be thought of as databases - think history, bookmarks, cookies etc, as well as installed extensions. A Firefox-based browser unable to load/work with the profile (directory) of a previous version would be considered a (serious) bug, and should be reported as such. Each profile contains metadata about its structure level / which version of the application last touched it. Think about how Firefox would handle profiles of multiple users when installed as a normal, system-wide application - the application update does not know about different user profiles, those are the complete responsibility of the (updated) application, when it starts. (One reason to keep profile backups around when updating the application.) In certain cases, an updated profile will then refuse to load in an older version of the application, with an appropriate message. This happens "silently" when you first start the browser with a profile that's not up to whatever structural features might be required by the new current version. All those applications "know" how to bring practically any profile from (almost) any previous version up to current structure. Some of my thoughts/what I know about how Mozilla profiles work:Ī) Profiles/Profile directories of Firefox (and Thunderbird, and LibreWolf being forked from Firefox, etc) are not "tied" to a specific release version of the software. this did get long, but I decided to leave it that way and rather give too much background. ![]() ![]() What kind of breakage are you worried about? I think I can kinda understand where you're coming from. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |