See also: IRC log
<scribe> scribe: MichaelC
<clown> \o/
<clown> https://github.com/mathiasbynens/jquery-details
Fork of the details summary polyfill has been incorporated into the main branch
So we should use https://github.com/mathiasbynens/jquery-details/blob/master/jquery.details.min.js
until browsers have native support
<scribe> ACTION: Michael to see if https://github.com/mathiasbynens/jquery-details/blob/master/jquery.details.min.js should be added to W3C script repository, and what the update policy is [recorded in http://www.w3.org/2016/05/04-aria-editors-minutes.html#action01]
<trackbot> Created ACTION-2060 - See if https://github.com/mathiasbynens/jquery-details/blob/master/jquery.details.min.js should be added to w3c script repository, and what the update policy is [on Michael Cooper - due 2016-05-11].
if doesn´t work out to put in central repositry, we can still put that version in common
Practices had difficulty migrating branches, so merged pending edits into master and just abandoned other branches
though that may have been a choice, not a technical limitation
other specs we may need all the branches
need to make sure everybody knows to have pushed everything to the server before doing a migration
nice to have issues just for specs you care about
<ShaneM> I just note that we keep pushing this out.
might be cleanest to do with the next publication
means an editing freeze both to publish and do the split
need to test out the publication process by removing APG from aria repo to be sure we don´t accidentally include stuff
MC to do a pretend publication of APG to test it out
rough plan: rip-off-the-bandaid with all the specs at once, during a week-long editing freeze at the time of the next publication (ARIA pseudo-LC) (June)
<Zakim> ShaneM, you wanted to ask about the web service
MC had concerns with stability of the web service used by the script
SM says it should be stable, Echdina uses it, ask in #pub if seems not true
if ok to continue with that service, can make live for Practices
then can put in the other repos after the split
but make live in practices sson
FYI this exists, but no plans yet for developing
currently thinking one AAM for all of CSS
though because CSS adds lots of stuff, could get hard to maintain
might be there are just a couple modules that realistically need it
maybe it needs to document anti-practices too, know of a couple strange mapping implementations
<clown> https://w3c.github.io/aria/aria/aria.html#supportedState
<clown> https://w3c.github.io/aria/aria/aria.html#role_definitions
<clown> Would this do: https://www.w3.org/TR/wai-aria-1.1/
<clown> ?
<Matt and Shane sort things out with peanut gallery comments from others>
Should put password role into spec now
(but turns out it´s there now)
just needs mapping
mainly based on HTML mapping
Next meeting is 18 May
regrets for that from clown
and from tzviya
This is scribe.perl Revision: 1.144 of Date: 2015/11/17 08:39:34 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/topic: Password role// Found embedded ScribeOptions: -final *** RESTARTING DUE TO EMBEDDED OPTIONS *** Found Scribe: MichaelC Inferring ScribeNick: MichaelC Present: MichaelC Fred JamesN Joanmarie_Diggs Joseph Matt Rich Shane Tzviya Agenda: https://lists.w3.org/Archives/Public/public-aria-editors/2016May/0002.html Got date from IRC log name: 04 May 2016 Guessing minutes URL: http://www.w3.org/2016/05/04-aria-editors-minutes.html People with action items: michael WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]