WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED WORKSFORME
15452
REGRESSION: two tabs required to move between links containing <object>
https://bugs.webkit.org/show_bug.cgi?id=15452
Summary
REGRESSION: two tabs required to move between links containing <object>
jay
Reported
2007-10-10 10:20:27 PDT
visit the URI, and use keyboard to navigate. in opera or mozilla, one tab per link navigates the whole page. in safari one has to hit the tab key twice per link... I am pretty certain this is a regression though it's been around for quite some time. SVG may not be the right component, so please move... in fact just now opera nightly has a bug and keyboard navigation is broken...
Attachments
link off site?
(878 bytes, text/html)
2007-10-10 10:53 PDT
,
jay
no flags
Details
html-only test case
(503 bytes, text/html)
2007-10-18 02:35 PDT
,
Eric Seidel (no email)
no flags
Details
Show Obsolete
(1)
View All
Add attachment
proposed patch, testcase, etc.
jay
Comment 1
2007-10-10 10:53:01 PDT
Created
attachment 16614
[details]
link off site?
Eric Seidel (no email)
Comment 2
2007-10-10 11:46:08 PDT
This appears to be a real bug. I would start debugging here: void EventHandler::defaultTabEventHandler(Event* event, bool isBackTab) The bug relates to the presence of the <object> tag, I expect that the object is stealing focus when it should not be, but I haven't yet confirmed what element is getting the focus when the <a> loses it.
Eric Seidel (no email)
Comment 3
2007-10-10 11:50:01 PDT
Actually, the second event just seems to be dropped on the floor.
Eric Seidel (no email)
Comment 4
2007-10-18 02:34:40 PDT
This is definitely a regression. I've demonstrated it with just HTML now.
Eric Seidel (no email)
Comment 5
2007-10-18 02:35:14 PDT
Created
attachment 16720
[details]
html-only test case
Alexey Proskuryakov
Comment 6
2008-07-28 01:53:51 PDT
I cannot reproduce this with
r35406
.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug