1. Go to a site that will pop up the form toolbar, ex home.netscape.com 2. Do not enter any data on the site 3. Click the save form data toolbar 4. A dialog box will pop up saying data has been captured, what data? Expected results: If there is no data on the form, the save button should be disabled or a dialog should say there is no data to save Actual results: dialog says data has been captured

Taking this a step further, the save button should be disabled in all of the following cases: 1. There is no data on the form 2. The form has not changed since the last time save-form-data was performed 3. The form has not changed since the last time prefill-form was performed

Agreed

nav triage team: since we've decided to remove the toolbar, not a beta stopper.

This is more general than just the toolbar. Wherever the "save" appears (context menu, edit menu, toolbar), it should be disabled in the three cases I mentioned above. Currently it is disabled in the first case only.

See also bug 77073. Turns out that the tests for enabling/disabling the menu items are slowing down the menu creation already. Adding more to those tests might slow it down even more.

Marking target milestone to be the same as milestone for bug 77073

this is working for me. any empty form produces disables save data entries