Closed
Bug 101601
Opened 23 years ago
Closed 23 years ago
Insert HTML is positioned badly and does not remember position after being moved and closed
Categories
(SeaMonkey :: Composer, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: TucsonTester2, Unassigned)
References
Details
Build ID: 20010924
The "Insert HTML" window opens up in the top left corner of the screen and all
you can see is the cancel button. If you hit the escape key the window will
close and then you can reopen it where you can actually use the window. But if
you position the window on the right side and close it, the next time it is
opened it will be off of the screen.
Reproducible: Always
Steps to Reproduce:
1.Open composer
2.Click on Insert->HTML
3.Hit esc (Sometimes the "Insert HTML" window will be correctly placed)
4.Click on Insert->HTML
5.Drag the "Insert HTML" window to the right side of the screen and click cancel
6.Click on Insert->HTML
7.Hit Esc (it will always be off of the screen at this point)
Actual Resutls:
Initially the "Insert HTML" window is in the wrong place. If you reposition the
window it will always open to the opposite side you placed it. Often this will
be to an extreme where you can not see the window on the screen.
Expected Results:
I would expect that the window would stay on the screen and where I placed it.
This works fine for every other window, such as the table properties window.
Reporter | ||
Updated•23 years ago
|
OS: All → MacOS X
Comment 2•23 years ago
|
||
I see two problems with the Insert HTML dialog:
1) Opening this dialog for the first time, the dialog title window is behind the
application menu. Closing the dialog by clicking cancel and reopening the dilaog
(Insert -HTML) resolves this issue.
2) Dragging dialog to a different location on the screen and closing will cause
the dialog to not display when invoking the Insert - HTML command again. This is
pretty bad...
Comment 3•23 years ago
|
||
Marking FIXED as I'm sure this is part of the generic window positioning problem
under Mac OS X 10.0 (i.e. upgrade to Mac OS X 10.1 and the problem goes away).
Somebody re-open if they can prove me wrong :-)
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•