[Webkit-unassigned] [Bug 62358] New: Needs a unified way to handle a case when a shadow host is focused.
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Jun 8 23:37:49 PDT 2011
https://bugs.webkit.org/show_bug.cgi?id=62358
Summary: Needs a unified way to handle a case when a shadow
host is focused.
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: HTML DOM
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: hayato at chromium.org
CC: dglazkov at chromium.org, rolandsteiner at chromium.org,
tkent at chromium.org, dominicc at chromium.org,
morrita at google.com
Let me summarize the current status here:
* <input type=text> element, and <textarea> element
- They use a shadow root internally. They have a focusable element, <DIV>, in their shadow root.
- They do extra works in their focus() method. Due to their extra works, a FocusController should treat them specially.
- Tab traversal also treats them specially. Tab traversal doesn't look for a focusable element in their shadow root.
* <kengen> elements, as a representative of usual shadow host elements.
- <keygen> elements has a focusable 'select' element in the shadow root.
- <keygen> element doesn't do any extra works in focus() method, so even if we call keygenelement.focus(), a internal 'select' element cannot get focused. Which means we can not change the value by keyboard, <Up> or <Down>.
- Tab traversal can find a internal <select> element and can focus it. Which means that once we focus it by <Tab> key, we can change the value by keyboard, <UP> or <Down>.
It is nice to get rid of this 'gap'. Let me update this bugzilla entty once I have some ideas to handle this gap nicely.
--
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