Support multiple profiles for the skeleton UI
Categories
(Toolkit :: Startup and Profile System, enhancement)
Tracking
()
People
(Reporter: alexical, Unassigned)
References
(Blocks 1 open bug)
Details
This is a bit tricky, because the size / location / maximization state of the browser window is stored in the profile, and at the time we need to display the skeleton UI we don't have a profile loaded. We resolve this currently by requiring us to be on the default profile. We could, however, attempt to at least resolve the profile path before we display the skeleton UI, and use that path to prefix our registry values.
In order to do this correctly I think we would need to fully parse the profiles.ini file to determine the default profile path. I think that's too fragile to maintain both inside and outside xul, so we'd need to rip the parsing pieces out nsToolkitProfileService / nsINIParser out of xul and into mozglue or something.
|
||
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Toolkit::Startup and Profile System' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Description
•