- From: Alexander Surkov <surkov.alexander@gmail.com>
- Date: Tue, 15 Oct 2013 12:41:27 -0400
- To: Joseph Scheuhammer <clown@alum.mit.edu>
- Cc: Richard Schwerdtfeger <schwer@us.ibm.com>, "W3C WAI Protocols & Formats" <public-pfwg@w3.org>, David Bolter <dbolter@mozilla.com>
Hi, Joseph. I could misunderstand where the problem is. I thought it is in "arrange events so state change does not occur on focused item, to avoid extra selection change announcements". This requirement sounded new with me. Alex. On Tue, Oct 15, 2013 at 12:31 PM, Joseph Scheuhammer <clown@alum.mit.edu> wrote: > There seem to be two threads on this issue. Repeating what I said on > another thread... > > FWIW, way back in September, Alexander Surkhov wrote: > >> Also not >> sure whether the spec should define an event order. I think Firefox >> fires them in reverse order: statechange events and then selection >> event. > > > I agree: The UAIG should not define any order to these events. I think > that is an implementation detail. Is a specified order required? Are any > ATs expectiing a specific order? If not, I would opt for saying that the > order in which these events occur is undefined. > > > -- > ;;;;joseph. > > > 'A: After all, it isn't rocket science.' > 'K: Right. It's merely computer science.' > - J. D. Klaun - >
Received on Tuesday, 15 October 2013 16:41:53 UTC