Closed
Bug 301351
Opened 19 years ago
Closed 19 years ago
Profile information should contain version number
Categories
(Toolkit :: Startup and Profile System, enhancement)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: Geert.Poels, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b3) Gecko/20050712 Firefox/1.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b3) Gecko/20050712 Firefox/1.0+ To avoid starting a browser of a different baseline with a 'possibly' incorrect profile, a version number in the profiles.ini [Profilex], might be very usefull. Origin of this bug : 1) Launching Deer Park with a Firefox 1.x profile caused the profile to be really messed up. After reusing it on FF 1.5, the UI of the browser was completely gone and the browser was unusable and unresponsive. 2) Deer Park release notes state the incompatibility of certain extensions, etc. ... My proposed solution : put a version number in the profile entry [Profilex]. Add a warning to the dialog when the user selects a possible incompatible profile. fe : Launching Deer Park(=2.x) with a 1.x profile or launching FF 1.x with a 1.x+1 profile. Just a warning, no prevention. Regarding my error with the messed up UI. Did Deer Park updated my profile in some way? Reproducible: Always
Comment 1•19 years ago
|
||
We want deerpark to work seamlessly with profiles created with 1.0.x. Let's fix the problems with upgrading (besides, it's technically infeasible to use a profiles.ini flag).
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
| Reporter | ||
Comment 2•19 years ago
|
||
It would be a very good thing if Deer Park could just pick up 1.x profiles That will be the major scenario when this version is officially released. But it's unlikely 1.x browsers will correctly pick up DP profiles In such a case, a warning is not a bad thing. Where this flag would be put is of less importance.
| Assignee | ||
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•