See also: IRC log
<scribe> scribe: jamesn
https://github.com/w3c/aria-practices/pull/163
MK: found there were 521 code format errors
JN: not sure I agree with the spacing rule
MK: lets go through some of the
rules
... some other things that need to be fixed - and some which
were not automatically fixable
MK: changed names of files - moved to sub directories
JG: updating code to be
consistent
... each thing has its own constructor - goal is to help people
understand what they want to do
... the code being readable and understandable is
important\
... pretty much the same at runtime
... don't understand what the format is for keyboard
information
4th PR is updating the links
Jemma: the last minute change was submenu items... I added sub-sub-menu items
we are working on the focus management for the sub sub sub-sub menuitems. almost done with focus managemnt for these
MK: action item about menu orientations etc.
JG: when on a menu item with a popup. space will just toggle the display of the submenu
MK: should do the same as right arrow
activate the menu'
Jemma: in terms of schedule - can create the PRs - can do a final review.... I will miss meeting next monday
menu item has had scope creep i think
MK: I agree - should have had that in the examples
table or list'
MK: Q? how important is the consitency
JG: we have a list of functions - sometimes if a key does more than 1 thing then can see things easier
JN: do not think it is a showstopper
resolved - use table in the future
http://w3c.github.io/aria-practices/examples/listbox/listbox.html
MK: used the word attribute specifically so could include tabindex
3rd column would contain (eventually) appropriate links to the main document. So places where use roaming tabindex and activedescendent etc. would have links to things in main document
MK: maybe fix up the old ones to this format later - before next release
MK: JG - are you ok with futre work being in this format
JG: got info about the properties and states associated with that role
<jemma> I also like Jon's template since it has separate section for "property/state", not mixed with "role" section.
<jemma> why don't we allow two templates depending on examples?
<jemma> actually, I found it is hard to write everything in "usage" in Matt's template
MK: can move into a 1 per page format
all: note listbox page isn't actually working
go with JG format - in the role column just go with the role, 2nd column is attribute column, element column and usage solumn
attribute column is attribute and value
focus is not to fix everything in existence, except where we have already agreed on things
adjust as working on things
MK: going to fix .jscsrc
in order to allow varuious spacing
This is scribe.perl Revision: 1.148 of Date: 2016/10/11 12:55:14 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/menu items/sub-sub menuitems/ Found Scribe: jamesn Inferring ScribeNick: jamesn Default Present: jemmaJaeunKu, jongund, AnnAbbott, JamesNurthen, matt_king, bryan Present: jemmaJaeunKu jongund AnnAbbott JamesNurthen matt_king bryan WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Got date from IRC log name: 28 Nov 2016 Guessing minutes URL: http://www.w3.org/2016/11/28-aria-apg-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]