12663 - [Dogfood] Can't type in New Msg window in body, forced to type in signature area

Status: VERIFIED FIXED

(MailNews Core :: Composition, defect, P3)

Description

[esther]

Using 1999082617 M10 build on win98, when you bring up a New Msg window and
click on the cursor, it lands in front of the text in the signature box (yellow
box).  It is very difficult to get the cursor to land in the body of the message
above the signature box.  Still need to try plain text and the Linux and Mac
platforms.

1. Launch Messenger (have preference for html compose = true)
2. Click New Msg toolbar button
3. Click in the body of the message to start typing.

Result:  the cursor lands in front of the text in the signature box
Expected:  the cursor lands in body above signature box

Comment 1

[lchiang]

The problem here is that we can't type a new message starting at the top of the
body for the compose window.

I'd say this is definitely blocking from dogfood usage.

Comment 2

[Jean-Francois Ducarroz]

I have the same problem when you do a reply. You cannot set the cursor at the
beginning of the message outside the blockquote block (the original message).
It's an Enditor selection bug (That's what Akkana told me). Reassign to Steve
Clark.

Comment 3

[lchiang]

cc: putterman since he also ran into this.

Comment 4

[lchiang]

The reply problem was even in the past builds.  It seems that this
reported problem (unable to set the cursor at the top of the message) is fairly
recent and now it applies to New Message.

Comment 5

[esther]

Mac 1999082816 M10 build and linux 1999082604 M10 build also have this problem.
Changing platform and os to all

Comment 6

[scottputterman]

In addition to what Esther stated, there is another problem.  Every once and a
while after clicking around, the signature disappears and you can start typing
from the top of the message.  However, when you send and then receive this
message, the body has no text.

Comment 7

[scottputterman]

I don't know if this is actually blocking anyone from doing work or blocking QA
from testing, but this bug makes the New Msg window pretty useless.  It would be
great if this could be fixed by M10.

Comment 8

[lchiang]

This is really blocking from dogfood mail usage since we want to send new
messages with the text typed in correctly.

Comment 9

[Kathleen :Brade]

ok, there seems to be several problems I see:
  1) clicking outside the table causes the caret to appear in the table.  I'm
pretty sure that mjudge already has a bug which covers that issue.
  2) using the arrow key, you can move the caret to the left of the table but it
won't go above the table.  I think this is the bug that this bug is covering
(caret not in correct location)
  3) when you do type in from of the table, the text goes in front of a <br> tag
(according to the Debug->Output HTML menu info) but according to
[e-mail], the text doesn't actually get sent.  [e-mail]
is going to look into this problem.

add myself to cc list

Comment 10

[pmock]

Update. The third issue that Kathy described occurs on the 1999-08-27-12 build,
but it does not occur on todays build 1999-08-30-09 build.  The 3rd issues looks
like it got fixed in between the builds.

Comment 11

[lchiang]

Yes, items 1 and 2 remain.  For a new message in mail, it's hard to have to use
the left arrow each time.  Kathy, do you know what mjudge's bug number is?

Comment 12

[Kathleen :Brade]

Mike's bug is #12028; he has one other blocker at the moment.  Hopefully he can
fix that one soon (I think it's a catch all for selection problems having to do
with tables).

Comment 13

[pmock]

On the Win32 1999-08-30-10 and Linux 1999-08-30-01 builds, item 3 does not occur.
Item 1 & 2 remain.

Side note: on today Mac build, I can bring up a compose window on a G3/400 but I
can bring it up on a PPC 9600/300.  I mention this b/c jay noted that he could
not bring up a compose window on his smoketest.

Comment 14

[lchiang]

(yes, Peter, on the smoketest, it was a problem with the time delay in taking a
long time to bring up the compose window. That should be fixed in the next
respin).

Comment 15

[pmock]

Thank you Lisa for confirming.  It tooks an extreme amount of time to bring up a
compose window on my non-G3 PPC.  I lost track after 1/2 a hour.

Comment 16

[sol]

I think this needs to be fixed for PR1, so I added a note in the Status
Whiteboard.

Also, I note there is no target milestone for this bug yet.

Comment 17

[buster]

It's hard to tell what this bug is actually about.  So Mike, I suggest you focus
on the key problem:  users cannot easily get the selection to be in the blank
line above the signature box.  This is probably a dup of a bug you already have,
but please keep this bug open separately so you can be sure to test blank line
selection against the mail composition window as a test case.

For others that have added incidental info to this report: please please please
don't do that.  It just diminishes the utility of the original bug report.  File
separate bugs on things that are separate problems, and if they're related say
so in the dependancy lists.  Keeping a single bug report focused on a single
problem is the best chance you have of getting your bug addressed in a timely
fashion.  So, if you added in info about some unrelated bug in this report, I
urge you to submit a separate bug if it's still relevant.

Comment 18

[esther]

Adding Phil to cc list.  I think this should be fixed before we try to get new
users to use our mail product (unless we only want them to manipulate folders
and read messages).   This is not an acceptable way to send mail.

Comment 19

[Phil Peterson]

Yes, I agree with esther (this is a dogfood blocker) and buster (typing above
the the "this message sent with 5.0" box is the real problem)

Can we work around by taking out the "this message sent with 5.0" thingy at the
bottom?

Comment 20

[mjudge]

this is fixed

Comment 21

[pmock]

Verified as fixed
Verified using the following build:
 Win32 Seamonkey build 1999-09-13-09
 Linux Seamonkey build 1999-09-13-09
 MacOS Seamonkey build 1999-09-13-09