171856 - compose window has two carets but no focus after minimising/minimizing

Status: RESOLVED WORKSFORME

(MailNews Core :: Composition, defect)

Description

[Drew Devereux]

User-Agent:       Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.2a) Gecko/20020910
Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.2a) Gecko/20020910

When the caret in a compose window is in the body of an email being composed,
minimisation and restoration of the window causes two carets to appear, both
blinking.  One is located in the body of the email, the other is located where
it was last time it was in the header.

Reproducible: Always

Steps to Reproduce:
1. Click compose to get new compose window.  Caret blinks in To: line.  Type
something if you want.
2. Click in body of email.  Caret blinks in body.  Type something if you want.
3. Minimise window
4. Restore window.  There are two carets, both blinking, one in the To: line and
one in the body.
5. Type something.  No text appears at either caret position.

OR

1. Click compose to get new compose window.  Caret blinks in To: line.  Type
something if you want.
2. Click in Subject: line.  Caret blinks in Subject: line.  Type something if
you want.
2. Click in body of email.  Caret blinks in body.  Type something if you want.
3. Minimise window
4. Restore window.  There are two carets, both blinking, one in the Subject:
line and one in the body.
5. Type something.  No text appears at either caret position.

Actual Results:  
Two carets, both blinking, but neither has focus.


Expected Results:  
One caret, blinking, with focus, in the position it was in when the window was
minimised.

I don't think this is the same as bug 147077, because both carets are blinking
but neither has focus.

Comment 1

[esther]

I do see this in mozilla build Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.2a) Gecko/20020910, but not in commercial branch or trunk dated 20021001 on
winxp or linux.

Comment 2

[Vaclav Dvorak]

Confirming, changing component to Composition, adding blockage of bug 154188,
setting OS to All (seeing on Win98), adding "but no focus" and alternate
spelling to summary to help searchers.

After restoring the minimized window, there is _no_ focus (but two carets),
pressing Tab doesn't do anything.

Comment 3

[lee]

i can confirm on linux platform.  difference is that if the compose window is in
window manager focus, the address field has input focus, and two carets blink,
one in the address field and one in the body text area.

if the compose window is not window manager focused (focus on a completely
different window), only the body text area caret blinks, and no other carets are
visible.

help->about
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030115

$ dist/bin/mozilla -v
Mozilla 1.4a, Copyright (c) 2003 mozilla.org, build 2003030502

.mozconfig build parameters:

mk_add_options MOZ_MAKE_FLAGS=-j12
ac_add_options --disable-tests
ac_add_options --disable-debug
ac_add_options --enable-optimize=-O3
ac_add_options --with-extensions=default,irc
ac_add_options --enable-crypto #comment to disable PSM/SSL support
ac_add_options --enable-mathml #uncomment to enable mathml
ac_add_options --enable-java-supplement
ac_add_options --enable-svg
mk_add_options MOZ_INTERNAL_LIBART_LGPL=1
MOZ_INTERNAL_LIBART_LGPL=1
MOZ_CALENDAR=1
mk_add_options MOZ_CALENDAR=1
ac_add_options --enable-calendar

Comment 4

[Nick Lott]

This is the same as Bug 166121 and Bug 166278 I think. Someone needs to decide
which ones to dupe.
Basically the caret is switching focus between controls in a new comnpose window
and its final position is not consistent.

Comment 5

[Mike Cowperthwaite]

(In reply to comment #4)
> This is the same as Bug 166121 and Bug 166278 I think. 

I don't think so; both were about the location of the caret when the window is 
first opened -- not the same as reported here.


Drew Devereux, have you seen this bug in recent builds?  If not, please resolve 
this bug as WorksForMe.

Comment 6

[Drew Devereux]

Sorry, I can't help you.  I filed this bug against Mozilla, but I've since moved
to Thunderbird.  For what it's worth, I've never seen this bug in Thunderbird.

Comment 7

[Mike Cowperthwaite]

Bug was filed against an old build; I've never seen this particular symptom, but 
I know some related symptoms were addressed in the 1.4/1.5 timeframe.  =>WFM