18057 2008-03-24 21:26:28 -0700 keyDown incorrectly propagates up the frame tree 2022-08-11 12:15:07 -0700 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) Mac OS X 10.5 RESOLVED CONFIGURATION CHANGED InRadar P2 Normal --- 1 oliver webkit-unassigned ahmad.saleem792 ap bfulgham cdumez gsnedders rniwa oldest_to_newest 75057 0 oliver 2008-03-24 21:26:28 -0700 keyDown should not propagate up the frame tree, this is covered by the currently disabled fast/events/key-events-in-frame.html test. 75070 1 mrowe 2008-03-24 22:31:59 -0700 <rdar://problem/5818038> 1890615 2 ahmad.saleem792 2022-08-11 09:58:32 -0700 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! 1890653 3 rniwa 2022-08-11 12:15:07 -0700 This seems like config changed to me.