Closed Bug 255317 Opened 20 years ago Closed 8 years ago

Never lose focus if element/ancestor is hidden, destroyed or disabled

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P2)

defect

Tracking

()

RESOLVED DUPLICATE of bug 570835
mozilla1.9alpha8

People

(Reporter: aaronlev, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: access)

This is spun off from bug 255187 If any element becomes unfocusable for any reason (destroyed, hidden or disabled are the reasons I can think of right away), then the focus should automatically advance to the next focusable item.
Priority: -- → P2
Target Milestone: --- → mozilla1.9beta
We've taken care of any cases where focus/keynav is totally locked up -> minor
Severity: normal → minor
Blocks: 75324
Mass un-assigning bugs assigned to Aaron.
Assignee: aaronleventhal → nobody
QA Contact: keyboard.navigation
Depends on: 374786
When focused element becomes hidden by CSS visibility, this bug can still be reproduced on current Nightly build. > data:text/html,<input autofocus id="i"><input><script>window.addEventListener("load", function () { var i = document.getElementById("i"); i.style.visibility = "hidden"; setTimeout(function () { i.style.visibility = "visible"; }, 10000); }, false);</script> This testcase sets focus to the first <input> and hide it at load event. 10 sec later, it's shown again. Even during it's hidden, I can edit the content of <input>.
This is covered by 570835 pretty much.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Component: Keyboard: Navigation → User events and focus handling
You need to log in before you can comment on or make changes to this bug.