Closed Bug 21532 Opened 25 years ago Closed 24 years ago

Bad key-mappings for form completion.

Categories

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

x86
All
defect

Tracking

()

VERIFIED WORKSFORME
mozilla0.9

People

(Reporter: lorenzo, Assigned: bryner)

References

()

Details

(Keywords: access, helpwanted, Whiteboard: [nsbeta2-][nsbeta3-])

I've just tested M11 on my system, and have been mostly happy to see (at last!) the focus moving to the forn-post button when moving between input elements with the tab key. Now, there are two misbehaviours: first of all, you have to click on the space bar to submit, instead of the usual "Enter on the submit button" you get from Netscape on non-unix platforms, and any other browser; after you submitted the form, comes the second problem: the focus is lost, and you cannot jump between form input fields with the keyboard until you clicked on one of them.
Target Milestone: M11
Assignee: karnaze → kmcclusk
Reassigning to Kevin.
Target Milestone: M11
Assignee: kmcclusk → saari
OS: Linux → All
I'm seeing simular problems on WINNT with a 12/10/99 10:00am build. When tabbing over a submit button in test5.html then pressing return it does not depress the button. It also leaves the focus outline around each form element I have visited. If I hit the spacebar it will depress the radio button but it will not depress a button that has focus when the spacebar is hit.. I think this is a XP focus issue not specific to Linux. Setting OS to All and re-assigning to sarri for focus issues.
Status: NEW → ASSIGNED
Target Milestone: M13
Target Milestone: M13 → M15
Pushing to M15
One problem seems to be that we don't reset focus to the current document when a form submit happens. I'm not sure why that is. The other is button related, not focus.
Mass-moving most M15 bugs to M16
Target Milestone: M15 → M16
nsbeta2 6/1-. html32 behavior b.c. Also important for accessibility.
Keywords: nsbeta2
nsbeta2 6/1-. html32 behavior b.c. Also important for accessibility.
Putting on [nsbeta2+][6/15] radar.
Whiteboard: [nsbeta2+][6/15]
moving dated nsbeta2+ bugs to m19
Target Milestone: M16 → M19
Docshell is giving the focus to another docshell instead of keeping it in the document. This is the correct behavior, sometimes. Just not this time.
Cleaning up status whiteboard by marking beta2 minus (6/15 has passed) There is too much doomage to get to this for beta2 it seems.
Whiteboard: [nsbeta2+][6/15] → [nsbeta2-]
nsbeta3, should be able to keyboard navigate fully
Keywords: nsbeta3
Keywords: helpwanted
Whiteboard: [nsbeta2-] → [nsbeta2-][nsbeta3-]
Target Milestone: M19 → Future
Updating QA contact.
QA Contact: ckritzer → bsharma
Accessiblity, targeting mozilla 0.9
Target Milestone: Future → mozilla0.9
Summary: Bad key-mappings for form completion. → [access]Bad key-mappings for form completion.
-bryner, access->keyword. Brian - Chris is swamped, could you take this on?
Assignee: saari → bryner
Status: ASSIGNED → NEW
Keywords: access
Summary: [access]Bad key-mappings for form completion. → Bad key-mappings for form completion.
Status: NEW → ASSIGNED
accessibility bugs -> P1.
Priority: P3 → P1
This WORKSFORME on a current Linux build. Here's what I tried: - Bring up test #5 - tab to Submit button - press Enter, note that form submits - hit tab, note that no click is necessary to move focus to the document
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
updating QA contact to vladimire@netscape.com
QA Contact: bsharma → vladimire
verifying on build 2001-06-21-04-trunk windows 98
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.