Closed
Bug 170959
Opened 23 years ago
Closed 23 years ago
composer window is raised after publishing completes
Categories
(SeaMonkey :: Composer, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.2beta
People
(Reporter: mcs, Assigned: cmanske)
References
Details
Attachments
(1 file)
|
936 bytes,
patch
|
Brade
:
review+
alecf
:
superreview+
|
Details | Diff | Splinter Review |
Running with Netscape 7.0 on Windows 2000sp3 (tried to reproduce with Mozilla
1.1 and 1.2a but the publishing progress dialog does not automatically close on
those builds - already filed as bug 167996).
Problem: even if you switch to another Mozilla window (e.g., a browser window)
while the publishing progress dialog is open, the composer window associated
with the publishing progress dialog is raised and made the top-most window after
publishing completes. This is annoying and disruptive.
Steps to reproduce:
1) Open a browser window and a composer window (can be for the same page).
2) Click on the Publish toolbar icon, type password if necessary.
3) While the progress dialog says "Publishing..." switch to the browser window.
4) Wait for publishing to complete and the progress dialog to close by itself.
Notice that the composer window is raised to the top and the browser window is
lowered.
| Reporter | ||
Comment 1•23 years ago
|
||
This can't be fixed until after bug 167996 is fixed.
Depends on: 167996
| Reporter | ||
Comment 2•23 years ago
|
||
The same thing happens with Mozilla 1.0.1 on Windows 2000.
| Assignee | ||
Comment 3•23 years ago
|
||
This is unavoidable. The publishing progress dialog is a non-modal child window
of the Composer window. There is intricate interaction between the two to
post messages to the progress dialog. When it closes, you are now editing the
document at a new location, so showing that to the user and putting focus back
to the Composer page makes sense for most users. This is what causes the
Composer window to come forward.
Brade: Is this wontfix?
| Reporter | ||
Comment 4•23 years ago
|
||
Hmmm. My suggestion is that if the progress dialog does not have focus at the
time it closes itself, then focus should NOT be returned to the associated
composer window. Does that make sense?
Comment 5•23 years ago
|
||
confirming; I suggested comment 4
Status: UNCONFIRMED → NEW
Ever confirmed: true
| Assignee | ||
Comment 6•23 years ago
|
||
Sounds good to me! I'll try to do that.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.2beta
| Assignee | ||
Comment 7•23 years ago
|
||
In "SetDocumentEditable(true)", which is called when we are done publishing,
we were explicitly setting focus to the Composer window. The reason was because
that used to be necessary for "window.updateCommands()" to work, but I tried
simply removing that line and the commands seem to update perfectly fine!
| Assignee | ||
Updated•23 years ago
|
Comment 8•23 years ago
|
||
Comment on attachment 100784 [details] [diff] [review]
patch v1
r=brade
Can we add a comment somewhere indicating that we shouldn't call focus due to
bug 170959? I'm not sure exactly where the comment should go but I'm sure you
can find the best place for it.
Attachment #100784 -
Flags: review+
Comment 9•23 years ago
|
||
Comment on attachment 100784 [details] [diff] [review]
patch v1
sr=alecf
Attachment #100784 -
Flags: superreview+
| Assignee | ||
Comment 10•23 years ago
|
||
checked into 1.2beta trunk
Comment 11•23 years ago
|
||
Mark, can you please verify if this is fixed for you in latest build ?
thanks.
| Reporter | ||
Comment 12•23 years ago
|
||
Verified on Windows in a trunk build from 2002-10-08.
Status: RESOLVED → VERIFIED
Comment 13•23 years ago
|
||
*** Bug 143429 has been marked as a duplicate of this bug. ***
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•