Bugzilla

> When finished, I went into about:profile and I choose my old 32b default as the default one and it worked perfectly in TB v91.2 (64b) so... don't tell me tales about not being able to "fully go back and forth or cross-use profile". You're trying to avoid/kill my request which is PERFECTLY logic, sound and feasible.

You are misinterpreting comment 1 - but the instance/install/profile checking is now "complicated" so that's understandable.  

Going FORWARD in the same profile is not a problem - which is what you are wanting to do.  

But you installed the app (in this case 91.2.0) in a different path/location, by definition Thunderbird defaults to wanting a new profile - it's part of the new rules.  (Going forward or backward in versions/32bit vs 64bit doesn't matter - it's the location).

You are certainly good to go forward in release numbers using the same/old profile.  But if you put the application in a different location it's up to you to (manually) point to the old profile.

> When finished, I went into about:profile and I choose my old 32b default as the default one and it worked perfectly in TB v91.2 (64b) so... don't tell me tales about not being able to "fully go back and forth or cross-use profile". You're trying to avoid/kill my request which is PERFECTLY logic, sound and feasible.

You are misinterpreting comment 1 - but the instance/install/profile checking is now "complicated" so that's understandable.  

Going FORWARD in versions in the same profile is not a problem - which is what you are wanting to do.  

But you installed the app (in this case 91.2.0) in a different path/location, by definition Thunderbird defaults to wanting a new profile - it's part of the new rules.  (Going forward or backward in versions/32bit vs 64bit doesn't matter - it's the location).

You are certainly good to go forward in release numbers using the same/old profile.  But if you put the application in a different location it's up to you to (manually) point to the old profile.