[Webkit-unassigned] [Bug 46856] New: [Chromium] Tabbing into page doesn't always select the first element
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Sep 29 16:49:24 PDT 2010
https://bugs.webkit.org/show_bug.cgi?id=46856
Summary: [Chromium] Tabbing into page doesn't always select the
first element
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: Platform
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: avi at drissman.com
Upstream of http://code.google.com/p/chromium/issues/detail?id=57344 :
What steps will reproduce the problem?
1. Load http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/focus/typical_page.html
2. Click in the omnibox
3. Press [tab] once
Result: search field has focus (correct).
4. Click in the omnibox
5. Press [tab] once
Result: the search button has focus (incorrect).
Every time you tab into a web view, the first element in that view should gain focus (or the last element, if you reverse-tab in).
The bug: in WebViewImpl::setInitialFocus (WebKit/WebKit/chromium/src/WebViewImpl.cpp), just a tab keystroke is fired off. That works the first time when the page is initially loaded since no page object has the focus, but in subsequent calls it just advances the focus (incorrectly).
Compare to WebKit/WebKit/win/WebView.cpp's version which explicitly calls setFocusedNode(0) to reset the focus before advancing using the focus controller.
Broken on all platforms but the Mac (in which this initial focus code is even _more_ broken; see http://code.google.com/p/chromium/issues/detail?id=49738).
--
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