Open Bug 1850405 Opened 2 years ago Updated 2 years ago

Cannot insert tab character using alt-09 on Windows in Firefox

Categories

(Firefox :: Keyboard Navigation, defect)

Firefox 116
Desktop
All
defect

Tracking

()

Tracking Status
firefox-esr102 --- affected
firefox-esr115 --- affected
firefox117 --- affected
firefox118 --- affected
firefox119 --- affected

People

(Reporter: pxtl, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/116.0

Steps to reproduce:

On Windows 10

Go to https://bugzilla.mozilla.org/

Click the "Search Bugs" box.

Hold the ALT key and type 09.

Actual results:

Nothing

Expected results:

A tab character should be inserted into the search text box.

Confirmed that MS edge does not show this behavior. Since FF gobbles the tab key itself, being able to use alt-codes to enter tabs when using code editors is vital.

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

Component: Untriaged → Tabbed Browser

Managed to reproduce this on Windows 10/11 x64.
It's also reproducible on Chrome and Edge.

Severity: -- → S4
Status: UNCONFIRMED → NEW
Has STR: --- → yes
Ever confirmed: true
OS: Unspecified → All
Hardware: Unspecified → Desktop
Component: Tabbed Browser → Keyboard Navigation

Bot misclassified as tabbed browser. I've reclassified as keyboard navigation because it's a keyboard navigation key being blocked from entry.

@Hani, that's not consistent with my experience on Edge, on Edge I am able to use alt-codes to insert the Tab character.

Did you turn on NumLock?

(In reply to Masatoshi Kimura [:emk] from comment #4)

Did you turn on NumLock?

Yes, numlock is on. As I said, I can confirm that the alt-code for tab works in Edge and Notepad, but not in FF.

< -- I just inserted this tab character in Edge, where I made this comment.

Hm, markdown mangled that. Well, here it is again: <-- 3 tab chars here, done in Edge.

You need to log in before you can comment on or make changes to this bug.