Closed Bug 1230420 Opened 9 years ago Closed 9 years ago

No focus event when the focused element gets removed

Categories

(Core :: Disability Access APIs, defect)

x86
Windows
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1190882

People

(Reporter: Jamie, Unassigned)

References

(Blocks 1 open bug)

Details

STR:
1. Open this: data:text/html,<button onClick="this.parentNode.removeChild(this);">Remove</button>
2. Focus the button.
3. Press it.
Expected: Focus should be fired on the document.
Actual: No focus event.

Note that:
1. document.activeElement does return the body.
2. The document accessible does get the focused state.
Blocks: eventa11y
There's no DOM focus per

data:text/html,<button onClick="this.parentNode.removeChild(this);">Remove</button><script>document.addEventListener('focus', e => console.log(e.target), true);</script>

Neil, what do you think?
Flags: needinfo?(enndeakin)
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(enndeakin)
Resolution: --- → DUPLICATE
(In reply to Neil Deakin from comment #2)
> 
> *** This bug has been marked as a duplicate of bug 559561 ***

Thanks, Neil!

I'm curious if the document should not be focused in addition to 'blur' event, since it looks like an accessibility/usability issue.

Jamie, how hard does it beat NVDA users?
While this is ultimately due to bug 559561 (no DOM blur), it doesn't seem like that bug is getting traction. An a11y work around is being discussed in bug 1190882.
You need to log in before you can comment on or make changes to this bug.