© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
(In reply to comment #35)
> This just seems like a bad workaround, it won't solve to problem at all.
Some people want to have one FF window and open all links in that, others want to have one FF window on each screen. The only 'proper' solution would be to make it highly configurable. Or, if that's not possible, choose one way which the majority of users prefer and upset the other users.
I actually don't see my patch as a 'bad workaround' as it could co-exist with a proper fix that allows multiple FF windows on independent screens. Don't get me wrong, I'd love to fix this properly, but as I see it (university courses + the complexity of a proper fix + getting accustomed to the mozilla development process + ...) I probably won't have time to do that before the 3.0 release (assuming the 'late 2007/early 2008'-roadmap still holds).
Right now FF's usability on multi-screen displays is severely impacted. I see my patch as an intermediate step between now (3.0?) and a proper fix sometime in the future (3.1/3.5?).
Christopher, you can't easily display a special error dialog because there's nothing special in the way how FF fails to start. From FF's point of view the profile is locked and it doesn't know why that is. One way to solve that would be to detect the FF instance on another screen, propagate that back and then fail with a special error dialog. Though I have to say I don't like that solution - why should FF fail if it already detects a running FF instance?