<MichielBijl> https://www.paciellogroup.com/blog/2017/05/the-paciello-group-joins-vfo/

<scribe> scribe:Jemma

Carolyn MacLeod's questions about menubar mouse behavior

<jamesn> https://github.com/w3c/aria-practices/issues/144#issuecomment-298280680

<mck> https://github.com/w3c/aria-practices/issues/144#issueproblem-298280680

mck: Carolyn will fix the problem

<MichielBijl> +1 to car’s point

mck: matt, Michiel and James agree with Carolyn's suggestion

carolyn's comment -" So, if you agree that instead of closing on timeout, we should close on click, then that is what I will implement. "

james: mouse out will close previous menu

<MichielBijl> MB: I would argue that menu’s shouldn’t open on hover, unless, you’ve already activated an option in the menubar.

<MichielBijl> MB: To clarify, once you open a menu option and move your mouse to another option in the menubar, the previous menu option should close and the one you moved to should open.

james: Discussed 5/1/2017 in APG meeting. We agree with the substance of @carmacleod comments. 2 additional clarifications. we would argue that menu’s shouldn’t open on hover, unless, you’ve already activated an option in the menubar. To clarify, once you open a menu option and move your mouse to another option in the menubar, the previous menu option should close immediately and the one you moved to should open

Modal Dialog

<mck> http://w3c.github.io/aria-practices/#dialog_modal

<MichielBijl> https://github.com/w3c/aria-practices/issues/325

<sirib> I put my comments for 325

<sirib> by bda it meant 321

<sirib> My bad I meant 321

Because marking a dialog modal by setting aria-modal to true can prevent users of some assistive technologies from perceiving content outside the dialog, users of those technologies will experience severe negative ramifications if a dialog is marked modal but does not behave as a modal for other users. So, mark a dialog modal only when: Application code prevents all users from interacting in any way with content \outside of itside of it.side of it.side of it. Visual styling obscures the co[CUT]

jemma: I copied both edits for comparison. Original When a dialog closes, focus typically returns to the element that had focus before the dialog was invoked. This is often the control that opened the dialog. In circumstances where that element no longer exists, focus is set on an element that supports a logical work flow. Revised edit: When a dialog closes, focus is set on an element that supports a logical work flow. If the element that had focus befor[CUT]

original: When a dialog closes, focus typically returns to the element that had focus before the dialog was invoked. This is often the control that opened the dialog. In circumstances where that element no longer exists, focus is set on an element that supports a logical work flow.

revised: When a dialog closes, focus is set on an element that supports a logical work flow. If the element that had focus before the dialog was invoked still exists, that element is usually the most appropriate choice.

ann: I like original the better.

<sirib> I like original one too

<jamesn> i am ok with the original too

<mck> https://github.com/w3c/aria-practices/issues/321

http://w3c.github.io/aria-practices/examples/dialog-modal/dialog.html

michiel: I am working on revising css for example pages

micheil: i am rewriting the code for modal from bottom up.

<MichielBijl> For example: http://w3c.github.io/aria-practices/examples/button/button.html

<MichielBijl> https://moiety.me/research/dialog-modal/dialog.html

michiel: I can be done by next Monday

group discussion: there will be comment on small device view in coding example css file

in regards to modal dialog example

Treeview

<sirib> issue #?

Issue 380: Place examples after the introduction text

<mck> https://github.com/w3c/aria-practices/issues/380

<MichielBijl> http://w3c.github.io/aria-practices/#keyboard-interaction-5

mck: I support this proposal

michiel: proposal was putting the coding example link under pattern intro

<jamesn> me too

mck: we can coordinate this work.

rrsagents, make minutes

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/comment/problem/
Succeeded: s/comment/problem/
Succeeded: s/mouse over/mouse out/
Succeeded: s/out/ \outside of it./
Succeeded: s/out/outside of it./
Succeeded: s/out/outside of it/
Succeeded: s/intero/intro/
Present: jamesn AnnAbbott MichielBijl MattKing JaEunJemmaKu shirishaBalusani Bryan_Garaventa
Found Scribe: Jemma
Inferring ScribeNick: jemma
Got date from IRC log name: 01 May 2017
Guessing minutes URL: http://www.w3.org/2017/05/01-aria-apg-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.