Bug 17670 – Key events may improperly propagate from iframe to parent frame

• Component: WebCore Misc.
• Status: RESOLVED FIXED

[Rob Brackett]

A keyup event (but not keydown or keypress) generated inside an iframe can be captured on the document that contains the iframe, even though this shouldn't be possible.

This can be tested by creating a page with an iframe and adding a keyup event listener to the page's document and the iframe's document. If you give an element in the containing document focus and press a key, the document's keyup listener will fire. If you give an element in the iframe focus and press a key, both the iframe document's keyup listener AND the containing window document's keyup listener will fire.

Note: I have observed this on Mac OS X 10.4 and 10.5 on both PPC and Intel. The bug does NOT appear on Windows Vista. I have not tested Windows XP.

[Alexey Proskuryakov]

Thank you for the report!

Sounds like you already have a test case - could you please attach it (or link to it), so that we don't have to duplicate the effort?

[Rob Brackett]

Created attachment 19531 [details]
Iframe keyup event test case

Here's a test case for it -- there are three files, just open index.html. It demonstrates the problem with one iframe that is in the html, one that is added via javascript, and one that has designmode on.

[Alexey Proskuryakov]

Confirmed with r30791, nice test case.

[Oliver Hunt]

This does effect other key events as well, although in a somewhat round about method.

[Oliver Hunt]

Fix landed r31236