Closed Bug 17460 Opened 27 years ago Closed 26 years ago

content of input fields are lost when collapse/expand toolbars

Categories

(MailNews Core :: Composition, defect, P1)

x86
Windows 98
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: tbetz, Assigned: hyatt)

References

Details

Open mail composition-->enter an email (or some text) address in the "to:" field --> press on the tab left to it (the tab to collaps) --> press the tab again to see the email address again you have entered, but its gone. tested with build: 1999102608
Assignee: ducarroz → buster
Severity: normal → blocker
Summary: email address (to:) in mail composition → [Dogfood] content of input fields are lost when collapse/expand toolbars
Target Milestone: M11
This is similar/identical to bug 16709. You can reproduce it with any input field embeded in a toolbar like the URL field in the navigator window of the subject in message compose.
Whiteboard: [PDT-]RN
Not dogfood, workaround is there. Will put on dogfood release notes. PDT-
How come no workaround. I am sure we can find a solution, either by changing the editfield code or by doing some tricky stuff in JS. MessageCompose really need a solution. Users think their are sending a mail to some people and the result is that we will miss some of them!!! Ender always reset the content of the inputfield to the content of the DOM at the initialization of the page (first load). If we could change the value in the DOM during the edition (on handler like onchange or onblur), the problem will be fixed. I have tried myself to set the value from JS during an onChange and onBlur with the JS: myInputField.value = myInputField.value but it apparently never reach the DOM, only the gfx text widget!
Target Milestone: M11 → M13
Status: NEW → ASSIGNED
Depends on: 16709
Priority: P3 → P1
this is another instance of the "need to save/restore frame state" problem that nisheeth is working on, and has a partial solution for already. see bug 16709. when that is fixed, this should also be fixed, but it's useful to not dup this bug just to be sure we test this case.
Update. I verfied bug 16709 using builds 12/13 on win98 and the scenario for that bug, but this bug is not fixed. 16709 was for losing the content when scrolling, we don't lose the display of the content as stated in that bug, but we do lose the actual content (see new bug 21656).
Summary: [Dogfood] content of input fields are lost when collapse/expand toolbars → content of input fields are lost when collapse/expand toolbars
Whiteboard: [PDT-]RN
updating summary fields
Assignee: buster → hyatt
Status: ASSIGNED → NEW
Depends on: 21656
this bug is dependent on 21656. I think that this is actually a dup of that bug (but then, I thought the same about 16709, which only turned out to be the first step in solving this problem.) So leaving this bug open, assigning to hyatt. He can dup it if he's sure.
*** Bug 21940 has been marked as a duplicate of this bug. ***
Assignee: hyatt → nisheeth
Nisheeth, each frame constructor should just hold a frigging global history state object for all content nodes... a table accessible from the frame constructor that can be written into by the tree.
*** Bug 19093 has been marked as a duplicate of this bug. ***
Assignee: nisheeth → hyatt
Hyatt, giving this one back to you as per our recent conversation...
*** Bug 19345 has been marked as a duplicate of this bug. ***
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Fixed, although the contents don't get restored until you click inside the text field after showing it. It is a bug in the Ender frame. I'm closing this. A separate bug should be filed against buster for that issue.
the bug you ask for already exists and it is bug 21940
Using build 2000012520m13 on win98 and linux and 2000012603m13 on mac this is fixed. Note comment by hyatt on 1/14 about having to click in field to get text back still exists and a separate bug was already logged. Verified
Status: RESOLVED → VERIFIED
QA Contact: lchiang → esther
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.