We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

Input fields are not working in Responsive design tool (OSX)

  • 2 replies
  • 5 have this problem
  • 2 views
  • Last reply by alyr42

alyr42
alyr42
more options

After I switch to Responsive Design Mode I can not type anything into the input fields, instead FF try to search in website content, like I'd press Cmd+F. The only way to fill any input field is to paste some content into it.

What I've done: 1. switch to responsive design mode 2. choose any device, or leave it default (responsive) 3. reload the website 4. clicking into any form field (e.g. login form, username field) 5. start typing the username

Result: I am typing into the search bar (normally appears after press Cmd+F shortcut), instead of the form field where I clicked before.

I am using OSX 10.13.2 and Firefox 57.0.3. The problem is real since the new FF design and new Responsive mode released.

After I switch to Responsive Design Mode I can not type anything into the input fields, instead FF try to search in website content, like I'd press Cmd+F. The only way to fill any input field is to paste some content into it. What I've done: 1. switch to responsive design mode 2. choose any device, or leave it default (responsive) 3. reload the website 4. clicking into any form field (e.g. login form, username field) 5. start typing the username Result: I am typing into the search bar (normally appears after press Cmd+F shortcut), instead of the form field where I clicked before. I am using OSX 10.13.2 and Firefox 57.0.3. The problem is real since the new FF design and new Responsive mode released.

Modified by alyr42

Chosen solution

Thanks for your comment Pkshadow. I've just found the bug report, it is more than a years old but still open somehow. (https://bugzilla.mozilla.org/show_bug.cgi?id=1322385)

My problem solved after the following option:

Set accessibility.typeaheadfind=false in about:config.

I hope it will help for others too.

Read this answer in context 👍 0

All Replies (2)

Shadow110
Shadow110
more options

If you have a bug, file a bug report. https://bugzilla.mozilla.org/ Bug Writing Guidelines : https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines Please let us know if this solved your issue or if need further assistance.

alyr42
alyr42 Question owner
more options

Chosen Solution

Thanks for your comment Pkshadow. I've just found the bug report, it is more than a years old but still open somehow. (https://bugzilla.mozilla.org/show_bug.cgi?id=1322385)

My problem solved after the following option:

Set accessibility.typeaheadfind=false in about:config.

I hope it will help for others too.

Modified by alyr42