Open Bug 260668 Opened 20 years ago Updated 1 year ago

Form controls should get focus when the caret moves from adjusent content in the caret browsing mode

Categories

(Core :: DOM: UI Events & Focus Handling, enhancement, P5)

Product:
Core
Component:
DOM: UI Events & Focus Handling
Type:
enhancement

Tracking

()

People

(Reporter: nian.liu, Unassigned)

References

(
URL
)

Details

(Keywords: access, Whiteboard: sunport17) 

1.create a textbox with null content
2.move from the content end before textbox or content beginning after textbox

expected result: focus is in textbox and ready for input
actural result: caret skip textbox and move to next content

this bug only happens after my fix of 241160
Ginn, is it okay for you to assign caret navigation bugs to yourself and just cc me?
Assignee: aaronleventhal → ginn.chen
Blocks: caretnav
Assignee: ginn.chen → nian.liu
Summary: in caret browse mode, caret skip brframe in textbox → in caret browse mode, caret skip brframe in textbox/textarea
Whiteboard: sunport17
QA Contact: keyboard.navigation
Component: Keyboard: Navigation → User events and focus handling

The bug assignee is inactive on Bugzilla, so the assignee is being reset.

Assignee: nian.liu → nobody

Once a form control gets focus, anyway users need to use Tab key to move outside of it. Therefore I don't think it's reasonable to make caret move set focus to form controls too. You can use Tab key to focus form controls.

URL: data:text/html,abc<input>def
Severity: normal → S4
Type: defect → enhancement
OS: Linux → All
Priority: -- → P5
Hardware: x86 → All
Summary: in caret browse mode, caret skip brframe in textbox/textarea → Form controls should get focus when the caret moves from adjusent content in the caret browsing mode

The patch for bug 1384606 will make you impossible to move caret into form controls. Instead, your caret won't be caught in form controls only with navigating with arrow keys.

Depends on: 1384606

The following field has been copied from a duplicate bug:

Field Value Source
Keywords access bug 376369

For more information, please visit auto_nag documentation.

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