Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Pressing enter after entering a username and password no longer submits

  • 2 replies
  • 1 has this problem
  • 4 views
  • Paskiausią atsakymą parašė Rumbles

more options

When I log in to most sites my password manager automatically fills the username and password and I just click on submit.

Some sites aren't in the password manager, and I have to type in the username, tab to type in the password, and normally I would just hit enter and it would submit the u/n and p/w

Recently I have noticed, this doesn't work, I have to click on submit or tab until I am on the submit button then press enter. Other forms where I search (for example) i can enter text in the field then press enter from that field and it submits fine.

I am wondering if there is a setting in firefox that would control that, or if it is just a plugin that is likely to be breaking this behaviour.

When I log in to most sites my password manager automatically fills the username and password and I just click on submit. Some sites aren't in the password manager, and I have to type in the username, tab to type in the password, and normally I would just hit enter and it would submit the u/n and p/w Recently I have noticed, this doesn't work, I have to click on submit or tab until I am on the submit button then press enter. Other forms where I search (for example) i can enter text in the field then press enter from that field and it submits fine. I am wondering if there is a setting in firefox that would control that, or if it is just a plugin that is likely to be breaking this behaviour.

Chosen solution

hi, this problem should have gotten solved in firefox 65.0.1 according to the release notes at https://www.mozilla.org/en-US/firefox/65.0.1/releasenotes/

Skaityti atsakymą kartu su kontekstu 👍 1

All Replies (2)

more options

Chosen Solution

hi, this problem should have gotten solved in firefox 65.0.1 according to the release notes at https://www.mozilla.org/en-US/firefox/65.0.1/releasenotes/

more options

philipp said

hi, this problem should have gotten solved in firefox 65.0.1 according to the release notes at https://www.mozilla.org/en-US/firefox/65.0.1/releasenotes/

Thanks, I didn't realise it was a bug, and I am running the affected version 65.0+build2 on 18.04

I guess I just need to wait for the ubuntu repo to offer me 65.0.1