Build ID: 20011003 The "Insert Character" window should be set so that it is always on top while in a composer window. This will make it easier to insert multiple characters into a document. As it is now the "Insert Character" menu will not close after you choose a symbol and insert it. Since it stays open it should let you click different areas of the page so that you can easily insert them throughout the document without having to switch windows. This also helps the window stay in the front and not get lost behind the page.
over to cmanske
Assignee: syd → cmanske
I think this request would be very annoying when user switches to a browser window, where the Insert Characters dialog would be irrelevant. Currently, if you are using it for multiple characters, you simply keep it in view. If you switch windows, you can activate it in Windows by clicking on the icon in the taskbar. Otherwise, selecting the menu command "Insert | Characters and Symbols" brings any existing dialog to the foreground. I'm inclined to not fix this. Brade?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Charley--I think you misunderstand how this should work. I think the request is for this window to always float in front of it's parent window (a Composer window). When another window is brought to the front (such as a browser window), the palette should hide itself. If the user opens a modal dialog (such as save) in Composer, the palette should also hide itself. This bug should be dependent on the floating dialog bug I filed recently. Possibly set milestone to "Future" or Mozilla 1.2?
I'm definitely not taking on the task of fancier window management as brade suggests.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Summary: [RFE] Put the "Insert Character" window always on top → Put the "Insert Character" window always on top
Assignee: cmanske → nobody
Status: ASSIGNED → NEW
QA Contact: sujay → composer
Target Milestone: Future → ---
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.