Closed Bug 366605 Opened 18 years ago Closed 18 years ago

session restoration in failing in simple test

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 346337

People

(Reporter: ray, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1


I can open a page with form and put in some values. Then I 'Force Quit' the app and re-launch and the session restore does not put in all the fields.


Reproducible: Always

Steps to Reproduce:
1. I launched a local build of FF with: /Users/ray/mo/browser/mozilla/dist/Minefield.app/Contents/MacOS/firefox -P minefield1

2. I loaded a local html file that I had created:

<html><head><title>test1</title></head>
<body bgcolor="ffffff">
<form action="foo.cgi">
<input type="text" name="text1"><br>
<input type="text" name="text1"><br>
<input type="text" name="text1"><br>
<input type="submit">
</form>
</body></html>

3. I clicked in the first form field to put the keyboard focus there and typed "aaa", without the quotes.

4. I typed the tab key to move the keyboard focus to the second field and typed "bbb".

5. 4. I typed the tab key to move the keyboard focus to the third field and typed "ccc".

6. I hit the tab key again and the keyboard focus went to the location URL field.

7. I used "Force Quit" to kill the Minefield app instance.

8. I relaunched Minefield and confirmed the restore of the session.
Actual Results:  
The restored session has "aaa" in the first form field and the second and third fields are blank.


Expected Results:  
The restored session should have "aaa" in the first form field, "bbb" in the second form field, and "ccc" in the third form field.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.