On Windows, the profile manager stores the Netscape profiles three directory levels up from the application location (I believe). Would it be better to store the Netscape profiles in a user account specific directory location (as on UNIX), such as the "Application Data" directory in the user's Windows profile directory? To find the location of this directory, you can use the nsSpecialSystemDirectory class with the Win_Appdata parameter.

At present, the implementation is aimed to be parallel with 4.5 world. This might change as we identify the advantages of new ideas.

I believe the 4.5 way of storing profiles on Windows allows security violations. Other users should not have access to the profiles I create in my Windows account, by default at least. By storing the profiles in a user specific location, other accounts are prevented from accessing them, as the UNIX way of storing them achieves.

At present, users are allowed to store the profiles in the location of thier choice. The default is still relative to the exe location. We will discuss policy you have mentioned inorder to verify the feasibiliy of that choice. Moving TFV to M9.

Storage of profiles in a directory relative to the application - the current default - is not the preferable option. In the case where the application is stored on a server where the user has no write permission, or where the application is stored in Windows NT and the administrator has removed write permission to the directories containing the application, the user has no choice but to store their profile in a user specific location. Their "Application Data" directory, or their home path (determined from HOMEDRIVE & HOMEPATH environment variables) would be much better defaults, and would bring the Windows version of Mozilla into line with the UNIX version.

There is a similar request for Macintosh too. Issues related to storing profiles (possible impacts) in those directories will be discussed and will be implemented in M10.

This is the same problem discussed in 6464, marking duplicate. *** This bug has been marked as a duplicate of 6464 ***

Moving all Profile Manager bugs to new Profile Manager Backend component. Profile Manager component to be deleted.