<Dorothy> Dorothy +
<scribe> scribe:Stefan
<Dorothy> Dorothy+
James: issue #1038
... Not a 1.2 issue
... iOS 13 seems to have implentation of this
<jamesn> https://github.com/w3c/aria/issues/1035
James: proposal is to eleminate the "should" from the spec
<jamesn> https://github.com/w3c/aria/pull/1037
James: could be a 1.2 milestone
https://github.com/w3c/aria/issues/1034
James: what should we do with this?
Joanie: presentation pulls the semantics out
Matt: very interesting
title
... I will talk with the issue opener
James: We have meeting with other
WGs
... we want to talk with them but before we should align
Matt: we should have a discussion with them
James: we should come to a conclusion first
Matt: any AT devs out there?
James: not from the attendee list
Janina: James Craig is there? James: yes
James: any objections to
merge?
... ok we will merge
James: I like to have people to look at this .. any comments on the pull request?
Matt: its a bandwith thing to take care of that
<joanie> https://github.com/w3c/aria/pull/1023
James: I'm conservative side: some we believe should not be global should be explicitly named
Matt: I wonder if we dont want do do all changes in one pull request, can we break up in several categories?
James: currently 4 attributes
pull request deals with
... creating separate pull for aria-haspopup make sense
... I will do that
Matt: there is already one
James: removing it from global means also used with HTML elements it won't work, 2nd if somebody has used them on role presentation role will be problematic too
<Zakim> joanie, you wanted to suggest starting with widget (superclass) rather than specific roles
James: using superclass when possible
joanie: does an input sublcass widget?
Matt: yes
joanie: if we use superclasses for that there is a danger of new roles in other tech(svg) that others will not support aria-disabled because now there are global
Matt: like aria-invalid on option role, makes no sense
(all): discussion about roles and applied properties / consequences doing thta
James: there are caveats of
moving them to a higher level role
... we would like to get the spec clean not messy
Mat: i don't want to explain stuff in APG that does not make sense
James: disabled link exists
Scott: in HTML links cannot be disabled
James: if we remove that we break
people
... best to create a separate pull request for that
... role parity means that you can do the same, not have
to
... we do separate pull request
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 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/1.2/Not a 1.2/ Succeeded: s/puss/pulls puss/ Succeeded: s/pulls puss/pulls/ Succeeded: s/aby /any aby/ Succeeded: s/aby/any aby/ Succeeded: s/any any aby/any / Present: jamesn Stefan Joanmarie_Diggs Scott_O MichaelC jongund CurtBellew janina irfan mck Regrets: MarkMcCarthy MelanieRichards BryanGaraventa JemmaKu PeterKrautzberger HarrisSchneiderman Found Scribe: Stefan Inferring ScribeNick: Stefan Found Date: 22 Aug 2019 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]