[Webkit-unassigned] [Bug 75478] <summary> is not keyboard accessible

Mon Feb 6 00:41:40 PST 2012

https://bugs.webkit.org/show_bug.cgi?id=75478

Arko Saha <nghq36 at motorola.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nghq36 at motorola.com

--- Comment #10 from Arko Saha <nghq36 at motorola.com>  2012-02-06 00:41:39 PST ---
Hi Morita, Thanks for the review and guidance. Please find my comments below:

(In reply to comment #6)
> Here is my thought:
> - Without focus, it's not so easy to send a key events to the specific element.
>    So it would be great if we can make <summary> focusable.
>    There are some elements which support gaining focus and it would be good starting point to follow their way.

Yes. You are right. We can make <summary> element focusable. But I am not sure whether we should make <summary> or <details> as focusable. As per the spec http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#the-details-element <details> element is interactive content. So, here I am little confused. Please let me know if I am missing something.

>    I guess we can handle DOMActivate event.
> - On testing, please use EventSender instead of dispatchEvent(). Each of these two goes different code path, 
>    and EventSender is suited for emulating user behavior.

Ok, I will use EventSender in the test-case.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.