RE: UAIG Menu events

I looked at it, and it's fine.  We can add another case about how to handle author errors that don't close menus in 1.1

From: Joseph Scheuhammer [mailto:clown.idi@gmail.com]
Sent: Wednesday, October 30, 2013 2:02 PM
To: Cynthia Shelly; Joseph Scheuhammer; Richard Schwerdtfeger
Cc: W3C WAI Protocols & Formats; Alexander Surkov
Subject: Re: UAIG Menu events

On 2013-10-30 4:54 PM, Cynthia Shelly wrote:
Maybe.  I was asked to combine them, and that seemed the simplest way.

Ideally, I'd leave line 6 there.  If you take focus out of the menu and menu mode is still on, I think the user could get into a bad state.  Why do we need to remove it?


Well, I've officially turned into a pumpkin, and a day early -- hallowe'en is tomorrow.  As I have run out of time, I've published the latest table as an editors'  draft, and if it's wrong, either someone else will have to fix it, or it will have to wait until tomorrow.

The reason for removing it is we based the scenarios on one of Alex's replies to this thread, and there were only five such scenarios, not six.  In a previous version of the table (also in this thread -- yes I know it's long), I tried to keep row six, but I couldn't line things up anymore.  My best guess was to combine it with five.  If that's wrong, my best guess was wrong, I guess...

Quoting Alex:



If we wanted to describe what Firefox does then the following would describe it:



1. Menubar is deactivated (i.e. focus moves out of the menubar) then

MENUEND event on the menubar

2. Menubar is activated (i.e. focus goes into menubar, i.e. menu item

within the menubar gets focus) then MENUSTART event on the menubar

3. Menu item is focused then FOCUS on menu item

4. Menu is open then MENUPOPUP_START

5. Menu is closed then MENUPOPUP_END



Thanks.

Alex.

--

;;;;joseph.





'A: After all, it isn't rocket science.'

'K: Right. It's merely computer science.'

             - J. D. Klaun -

Received on Wednesday, 30 October 2013 21:10:59 UTC