If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Safe Form Fill does not work

VERIFIED FIXED

Status

()

Toolkit
Form Manager
P3
blocker
VERIFIED FIXED
18 years ago
8 months ago

People

(Reporter: jay, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
Selecting item to pre-fill on form and clicking ok makes the safe form fill
dialog go away, but the field on the form is not filled out.

Steps:
1. Enter wallet info
2. Goto amazon sample page
3. Click Edit | Wallet | Safe Form Fill
4. Select one of the names to fill in
5. Click OK (even though it is hard to see due to Bug 10406)

Expected: The name selected should be filled in the name field on the amazon
form page

Actual: The field is still blank

Machine and Builds Tested:
Win98 with build 1999080908
Linux RH6 with build 1999080908

NOTE: This does not apply to Mac build 1999080908, which still hangs apprunner
(see Bug 11142)
(Reporter)

Updated

18 years ago
Severity: normal → blocker

Updated

18 years ago
Status: NEW → ASSIGNED
Depends on: 10406
Target Milestone: M9

Comment 1

18 years ago
"Hard to see" is an understatement.  I can't see the OK button at all on windows
due to 10406, and so have not been able to test this out for a long time.
Please tell me how you managed to click on that button.

If this is a blocker, then shouldn't 10406 be as well.

Comment 2

18 years ago
I jsut marked 10406 as a blocker

Updated

18 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED

Comment 3

18 years ago
Fixed.  Checked in new versions of WalletPreview.html and wallet.cpp.
(Reporter)

Updated

18 years ago
Status: RESOLVED → VERIFIED
(Reporter)

Comment 4

18 years ago
Verified Fixed on builds 1999081108 for Win and Linux.
Assignee: morse → nobody
Component: Form Manager → Form Manager
Product: Core → Toolkit
QA Contact: paulmac → form.manager
Target Milestone: M9 → ---
Version: Trunk → unspecified
You need to log in before you can comment on or make changes to this bug.