Clarification:   Is there anything that the server side can do, to prevent this dialog from appearing in the first place.   I will be happy to change the name of the POST-variable to pumpkin, say, instead of anything remotely resembling password, if it would thereby convince Firefox not to try to be so dammed clever.

In other words ... what can I do, in terms of the nature of the POST exchange, to persuade our well-intentioned good friend Firefox:   “nothing to see here ... move along ... these aren’t the ’droids you’re looking for ...”

I cannot reasonably change the settings of (no kidding...) four thousand client machines ... I can’t even tell any of these end-users what to do.   The only way I can address this problem is to fake-off Firefox, and I really, really need to find a way to do precisely that.   (Yesterday...)

Hopefully not. It is after all a security setting. It would be a little pointless if every scam artist, hacker, and other assorted bad guy could bypass it to enable a drive by.

---

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

What kind of page are you talking about here?

From the description, you seem to be implying that it isn't a login screen or a user settings/configuration/password change page... but what is it exactly?

Personally, and without any knowledge of how things actually work, I would expect that a password change dialog would be needed whenever *TWO* hidden-type fields are seen on the same form. I would expect to have to autofill an existing password whenever there is only a single hidden-type field.