Open Bug 771411 Opened 12 years ago Updated 2 years ago

Chrome-initiated keyup events propagated to content

Categories

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

Product:
Core
Component:
DOM: UI Events & Focus Handling
Platform:
x86
Windows 7
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: fowl2, Unassigned)

Details

As described here: http://meta.stackoverflow.com/a/71116/130041

"For whatever reason, Firefox doesn't block the chrome-initiated keyup event from being propagated after it returns focus to the document. My guess would be that it acts on the keypress event, switches back to the document context, and never kills the event chain in the process."

Steps to repro: Use the context menu on a comment entry field on http://stackoverflow.com then use the enter key to dismiss.

Expected result: content should not receive a keyup event: comment should not be submitted.

Actual result: comment is submitted.

Related: Bug 452376, Bug 392555
Hardware: x86_64 → x86
Version: unspecified → Trunk
Component: Keyboard Navigation → Untriaged
Still reproduceable in just released Firefox 24 (on Windows 7 SP1 x64).
Component: Untriaged → Event Handling
Product: Firefox → Core
Component: Event Handling → User events and focus handling
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.