RESOLVED WORKSFORME 16212
REGRESSION (2.0.4-r11976): pressing space twice while focused on a checked radio input should not scroll container 
https://bugs.webkit.org/show_bug.cgi?id=16212
Summary REGRESSION (2.0.4-r11976): pressing space twice while focused on a checked ra...
Brian
Reported 2007-11-30 13:36:35 PST
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head> <title>Safari v3 bug</title> <!-- Safari v3.0.4 (523.12.9) Windows XP Safari v3.0.4 (523.12) Mac OS X 10.4.11 Bug: REGRESSION: pressing space while focused on a checked radio input should not scroll container. To reproduce: Press TAB to focus radio input. Select radio with SPACE. Press SPACE again. Expected: Container should not scroll if checked radio input is the event target. Focus should not shift. works as expected in Safari v2.0.4. and current versions of Opera, Firefox, and IE. --> </head> <body> <div style="height:300px; overflow:auto"> <form action=""> <fieldset style="margin-left:1em;border:0"> <input type="radio" name="input-p1q1-1" />answer1<br /> <input type="radio" name="input-p1q1-2" />answer2<br /> <input type="radio" name="input-p1q1-3" />answer3<br /> <input type="radio" name="input-p1q1-4" />answer4<br /> </fieldset> <p style="height:300px">&nbsp;</p> </form> </div> </body> </html>
Attachments
example page (1.15 KB, text/html)
2007-11-30 13:37 PST, Brian 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Brian
Comment 1 2007-11-30 13:37:23 PST
Created attachment 17611 [details] example page
David Kilzer (:ddkilzer)
Comment 2 2007-12-02 13:12:44 PST
Confirmed. Bug reproduces with the earliest WebKit nightly, r11976, with Safari 2.0.4 (419.3) on Mac OS X 10.4.11 (8S165).
Alexey Proskuryakov
Comment 3 2008-07-28 02:01:03 PDT
I cannot reproduce this with shipping Safari 3.1 or a locally built r35406. I suspect that this was fixed when correcting keydown/keypress handling.
Note You need to log in before you can comment on or make changes to this bug.