NEW 15166
REGRESSION: Tabbing doesn't return focus to address bar when expected 
https://bugs.webkit.org/show_bug.cgi?id=15166
Summary REGRESSION: Tabbing doesn't return focus to address bar when expected
Alexey Proskuryakov
Reported 2007-09-09 14:00:19 PDT
Steps to reproduce: 1) Open http://newsru.com/cinema/08sep2007/vene.html 2) Press Tab multiple times Focus goes from address bar to Google search field, then to a single text input on the page, and then gets lost. After a dozen more Tab keypresses, it finally returns to the address bar. Tested with r25499+Safari 3.0.3 beta. This is a regression from shipping Safari/WebKit.
Attachments
test case (543 bytes, text/html)
2008-01-07 14:21 PST, Alexey Proskuryakov 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
David Kilzer (:ddkilzer)
Comment 1 2007-09-09 16:30:57 PDT
<rdar://problem/5470384>
mitz
Comment 2 2007-09-09 21:33:17 PDT
See also bug 14490.
mitz
Comment 3 2007-09-09 22:00:54 PDT
*** Bug 14490 has been marked as a duplicate of this bug. ***
Alexey Proskuryakov
Comment 4 2008-01-07 14:21:44 PST
Created attachment 18319 [details] test case The focus is lost while it's in iframes - it's actually in inconsistent state, with keyboard input going into the latest properly focused element. Attaching a reduced test case. MSIE and Firefox do let iframes take focus, but they have a visual indication for it.
jay
Comment 5 2011-06-05 13:13:20 PDT
Version 5.0.5 (6533.21.1, r88132) OS X 10.6.7 wfm AP please check testcase, not clear that this bug should be open
Alexey Proskuryakov
Comment 6 2011-06-05 13:27:13 PDT
Certainly still reproducible with r88132.
jay
Comment 7 2011-06-06 00:52:35 PDT
ap not clear to me what is expected behaviour, nor actual behaviour reported. actual behaviour noted by me using testcase: tab key circulates normally, including address bar, and once for each iframe and input keyboard input in iframe does - not - go to previously focused element, see #4 iframe focus has no visible marker, this part is significant, apologies if this is bug spam, but currently there are 3 separate issues in this one bug.
Note You need to log in before you can comment on or make changes to this bug.