426955 - "Add a Keyword for this Search" does not capture all necessary fields for (at least) POSTed forms

Status: RESOLVED INCOMPLETE

(Firefox :: Bookmarks & History, defect)

Description

[walf]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-AU; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-AU; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12

I am using Firefox's keyword functionality to simplify a login.

Normally, when submitting forms by pressing the Enter key, Firefox behaves as if you've clicked the first submit button on that form. If that submit button has a name attribute, any value it holds is sent along with the form request. However if you add a keyword search for a form it does not capture the submit button's value. Thus it has inconsistent behaviour and has the ability to break keyword searches.

Reproducible: Always

Steps to Reproduce:
1. Go to example URL (https://members.adam.com.au/login.php)
2. enter any text in the username field
3. right-click on the password field and do 'Add a Keyword for this Search'

there is no need to actually use the resulting keyword bookmark to test the problem
4. go to Tools > Page Info > Forms and view the Login form's details, note that each control has a name attribute so should be 'successful' by html spec.
5. open your firefox profile's bookmarks.html in a text editor and find Username%3D including the quotes to view the bookmark's POST_DATA attribute

Actual Results:  
the POST_DATA does not contain the field 'Login' from the form's submit button.

Expected Results:  
it should contain the login field resulting in a value like Username%3Dtest&Password%3D%25s&Login%3DLog%20in

it can be worked around by manually editing the bookmark.html file

Comment 1

[Shawn Wilsher :sdwilsh]

Bulk closing all UNCONFIRMED bugs dealing with places that haven't had any bug activity in over 120 days, have no votes, and are not enhancement requests.

If you are still experiencing this issue in Firefox 3.0 or later, please re-open the bug with steps to reproduce (if they were not part of the original comment).