Closed Bug 21656 Opened 25 years ago Closed 25 years ago

[Dogfood]names added to addressing pane not sent to

Categories

(MailNews Core :: Composition, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: esther, Assigned: hyatt)

References

Details

(Whiteboard: [PDT+] Expected Fix Date: 1/14/00)

Using builds 1999121309 on win98, and build 19991211308m12 mac and linux, if you
compose a message with your email address as the 1st recipient, then add 3 more
names (buggy scroll bar- you have to scroll in order to get the 4th name
addressed), then send not all the recipients are sent to.

1. Launch Messenger
2. Open your Inbox and give your password
3. Click New Msg and address yourself as the first recipient, click <Enter> to
got to the next line.  Add recipient 2, continue add recipient 3
4. Now scroll down so you can add recipient 4 (a different bug)
5. Type in a subject
6. Type in the body
7. Send.
8. Get the message
Result: not all the recipients are listed in the header
Expected: all the recipient to be listed and to receive a message

Note: this was found while verifying complex bug 16709, will investigate more
tomorrow, had to get this in now.
Status: NEW → ASSIGNED
Summary: [Dogfood]names added to addressing pane not sent to → [Dogfood]names added to addressing pane not sent to
Target Milestone: M12
This problem is due because when you query the value from JS of an input element
which is not visible (frame has been destroyed), you don't get the right
content. Hyatt knows the problem. Hyatt, do we have bug number for this specific
case? if no, who should reassign this bug?
Assignee: ducarroz → nisheeth
Status: ASSIGNED → NEW
Reassigning to nisheeth.
Hyatt, I am in the middle of reflow command coalescing work, so I am not going
to be able to get to this for another two weeks.  If you have time, could you
take a crack at fixing this?  DOM queries for frame state on content whose
frames are not around should do the following:

a) Create a temporary frame for the content object
b) Call nsCSSFrameConstructor::InitAndRestoreFrameState() on the frame.
c) Ask the frame for the state that the DOM query needed
d) Destroy the frame.

If you could do this generically, then the other case that you mentioned in your
email would work also, namely, DOM calls on content whose style is display:none
will return valid frame state information.
Whiteboard: [PDT+]
Putting on PDT+ radar.
Assignee: nisheeth → hyatt
I just spoke to Hyatt and he has agreed to take a look at this.  Re-assigning to
him.
Status: NEW → ASSIGNED
Whiteboard: [PDT+] → [PDT+]12/17 proposed fix
Target Milestone: M12 → M13
Note: the bug for the difficulty getting to the 4th line of the Addressing area
is 21769.
add myself to cc list
Assignee: hyatt → nisheeth
Status: ASSIGNED → NEW
Whiteboard: [PDT+]12/17 proposed fix → [PDT+]
Hyatt is going on vacation tomorrow, and will not be able to even look at this
until 1/7/2000. It is non-trivial, so might not make M13 unless someone else
takes it. reassigning back to nisheeth in case he has time before then.
Status: NEW → ASSIGNED
Whiteboard: [PDT+] → [PDT+] Expected Fix Date: 1/7/00
Adding expected fix date.  Will work on this bug after reflow command coalescing
work is done.
adding self to cc-list
Blocks: 17460
Assignee: nisheeth → hyatt
Status: ASSIGNED → NEW
Giving this bug back to Hyatt as he is now back from vacation.  I wasn't able to
get to this while he was away.
Status: NEW → ASSIGNED
Whiteboard: [PDT+] Expected Fix Date: 1/7/00 → [PDT+] Expected Fix Date: 1/14/00
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Just landed.  Boy was this a nightmare to implement.
Using win & linux build 2000012520m13 and mac build 2000012603m13 this is fixed 
as stated in original scenario.  However, if you click on Reply to All when 
there are more than 3 addressees, only (3) show up in the addressing pane, 
separate bug already logged weeks ago.  Will find it later, this is verified.
Status: RESOLVED → VERIFIED
QA Contact: lchiang → esther
The reply to all bug mentioned in above comment is 24519.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.