Bug 18057

Summary: keyDown incorrectly propagates up the frame tree
Product: WebKit Reporter: Oliver Hunt <oliver>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: ahmad.saleem792, ap, bfulgham, cdumez, gsnedders, rniwa
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: Mac   
OS: OS X 10.5   

Oliver Hunt
Reported 2008-03-24 21:26:28 PDT
keyDown should not propagate up the frame tree, this is covered by the currently disabled fast/events/key-events-in-frame.html test.
Attachments
Mark Rowe (bdash)
Comment 1 2008-03-24 22:31:59 PDT
Ahmad Saleem
Comment 2 2022-08-11 09:58:32 PDT
I took the test case of this and changed it into JSFiddle: JSFiddle link - https://jsfiddle.net/rexpy5qs/show Patch (Where test landed) - https://github.com/WebKit/WebKit/commit/12aaa3589f0a2762feb2444c5cbb45a5704fe103 From the test case documentation, I clicked on iframe and tried to press any key and keyDown etc and it didn't listed anything in the iframe or no "FAIL" text. Same was the case for all browsers (Chrome Canary 106 and Firefox Nightly 105). There were no JS Logs to indicate that the test was not working fine. I think this can be marked as "RESOLVED WONTFIX" or "RESOLVED CONFIGURATION CHANGED" since it is working as intended. I also tried to look into WPT for any such cases but couldn't find any related test (I might be totally wrong here). Appreciate if someone can mark this bug accordingly. Thanks!
Ryosuke Niwa
Comment 3 2022-08-11 12:15:07 PDT
This seems like config changed to me.
Note You need to log in before you can comment on or make changes to this bug.