[Webkit-unassigned] [Bug 27099] Elements with display none still gets focues and take part in the tab order
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Jul 10 15:41:13 PDT 2009
https://bugs.webkit.org/show_bug.cgi?id=27099
Erik Arvidsson <arv at chromium.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|webkit-unassigned at lists.web |arv at chromium.org
|kit.org |
--- Comment #2 from Erik Arvidsson <arv at chromium.org> 2009-07-10 15:41:12 PDT ---
It seems like the following change works:
bool Node::isFocusable() const
{
return renderer() && hasRareData() && rareData()->tabIndexSetExplicitly();
}
It checks if the Node has a renderer before it claims to be focusable. This
works because display: none has no renderer. I'm not sure that this is
sufficient or if it might have other side effects?
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list