When a new, blank Composer window already exists it should get reused when the user picks "Edit Page" from the File menu or Open Web Location from the browser. The recycling of the window already happens for Open Web Location and Open File within Composer. We're just inconsistent if it comes from the browser window.
I don't think I agree with this window recycling policy. If I'm opening a new document with a blank composer window foremost, then it does make some sense to laod in that window. However, doing an Edit Page on a browser window, and having that load in an existing compose window (when I have an untouched composer window in the background) seems odd to me; there is less 'connection' between the command, and where the document eventually loaded. It's also much less likely that users will make a new composer window, go back to the browser, then do Edit Page.
I'm with sfraser here. See bug 35578 (opening links from mailnews) and bug 20306 (clicking the navigator button on the "taskbar") for some related discussion. Current behavior for composer: - Ctrl-L in Navigator and selecting "New Composer window" always opens a new Composer window. - Ctrl-L in Composer always shows "New Composer window" as the default, but if you created the window with Ctrl-Shift-N and haven't changed anything, it reuses the window. So there's an inconsistency between what the dialog says it's going to do and what it does.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WONTFIX
The case of "I have a new window and haven't typeed anything" is a special case. We always load a page (including new blank page) into this initial blank window. That was a major request from previous versions, but I can see where the But I agree with Simon and Jesse that we shouldn't use an existing blank window if the command to edit or open a page from the browser.
verified in 1/12 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.