1760511 - Keyboard not recognized after opening a new tab.

Status: RESOLVED DUPLICATE of bug 1757376

(Firefox :: Address Bar, defect)

Description

[[e-mail]]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:98.0) Gecko/20100101 Firefox/98.0

Steps to reproduce:

Type reddit.com, click enter, create a new tab with cmd+t. Press keyboard buttons.

Actual results:

Even if the caret was on the url bar, nothing is typed. No amount of mouse clicks to the url bar makes a difference. Firefox isn't frozen, I can switch between tabs and continue browsing

After a few seconds I can start typing to thr URL bar.

Expected results:

able to enter URL or search query on URL bar.

Comment 1

[[e-mail]]

I need to first switch to another app and then back to Firefox for it to be fixed.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Firefox::Address Bar' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 3

[Peter Magyari (Desktop QA)]

Hi,

I wasn't able to reproduce the issue on Firefox 98 or Firefox Nightly 100.0a1.

Could you check if this also occurs while using a new profile? Here is a link that can help:
https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles

Thanks!

Comment 4

[James Teow [:jteow]]

We recently fixed a bug that might be similar to this Bug 1757376, which was fixed in Firefox 100.

Please try downloading either Firefox Beta 100 or Firefox Nightly 101 to see the changes and let us know if the bug you were seeing was fixed in either of these versions.

Comment 5

[Drew Willcoxon :adw]

Reporter, I'll resolve this bug as incomplete for now, but if you're able to reply to comment 4, please do so here in the bug, thanks.

Comment 6

[[e-mail]]

(In reply to James Teow [:jteow] from comment #4)

We recently fixed a bug that might be similar to this Bug 1757376, which was fixed in Firefox 100.

Please try downloading either Firefox Beta 100 or Firefox Nightly 101 to see the changes and let us know if the bug you were seeing was fixed in either of these versions.

Yes, this was exactly the bug and it no longer occurs.