21536 - Dogfood: Navigation keys not working in text fields

Status: VERIFIED FIXED

(Core :: Layout: Form Controls, defect, P2)

Description

[Alex]

Tab, arrow keys, home/end keys, and page up/down keys not working in text
fields. They work with other non-text form elements (radios, pulldowns, etc).

Build tested as 1999121208

Comment 1

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Moving to HTML Form Controls and reassigning.  I see this in Linux build, same
date.  Marking All/All and major.

Comment 2

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Really changing the component this time...

Comment 3

[karnaze (gone)]

Steve, is this your's or EricP's

Comment 4

[rubydoo123]

assigning this one to akkana for tracking of key binding breakage

Comment 5

[Akkana Peck]

They work in text fields, but everybody thinks they don't because of the focus
problem (having to click in, out, in, in the text field before focus is really
there).  This is saari's bug.

Comment 6

[Peter Trudelle]

targetting p2 for m12, putting on dogfood radar, shortening summary to fit.

Comment 7

[leger]

Putting on PDT+ radar.

Comment 8

[saari (gone)]

Akkana, I'm *not* seeing the focus problem. I click one and can navigate with
the arrow keys just fine. I've tried this on MacOS and Windows.

Comment 9

[Akkana Peck]

Perhaps this bug should be marked fixed.  I think we still had the "have to
click four times even to get arrow keys" bug when this was filed, whereas now
that bug only applies to overlays.

Comment 10

[Peter Trudelle]

Not fixed in today's opt comm bits.  In a form, on all platforms, these keys
affect the page rather than the text field.

Comment 11

[Peter Trudelle]

clarification: multi-line text fields

Comment 12

[saari (gone)]

Fixed it

Comment 13

[leger]

Updating QA Contact for verification.

Comment 14

[ckritzer (gone)]

Marking VERIFIED FIXED on:
	- MacOS86 2000010308 commercial
	- Linux6 2000010308 commercial
	- Win98 2000010308 commercial