See also: IRC log
<scribe> agenda: this
<joanie> scribe: joanie
JS: Bogdan had missed our emails.
He apologized profusely, and is now back on track.
... One of the issues was how to deal with this business of
cached and current property names.
... He sent the proposal to me, Rich, Joanie, and Michael
Cooper.
... He explains the difference between current and
cached.
... While cached is faster, there's the danger that the
property has not been cached yet.
... Bogdan proposes we explain the difference in some
section.
... But that we do not specify that level of detail of the
mapping table.
RS: It would be nice to know which to use.
JS: Both will always work, but there's a danger that you will have to make two calls.
RS: We should probably just get the current, and will know it's always going to be right.
<clown> scribenick: clown
JD: for my platform, I think
there is some confusion around setters and getters.
... I think both the implementor and the tester need to use the
getter.
<richardschwerdtfeger> stepping out a second
<joanie> scribe: joanie
JD: (Technical discussion about why in general it is the getter and not the setter user agent implementors implement)
JS: I like the idea of a preamble and then just using the property name.
https://developer.gnome.org/atk/stable/AtkObject.html
atk_object_ref_state_set ()
JD: I don't want to actually
change this in the Core AAM.
... As I indicated last week.
JS: Bogdan has emailed us with
three proposals.
... We need to get back to him on what we think.
... I have already replied that I like the preambled section,
followed by specified the preable and property.
RS: What I'm saying is that you
can say at the top that UIA has a notion of current and cached
versions of the properties.
... And that in this specification, we'll refer to the property
name without specifying current or cached.
... But for the purpose of automated testing, we'll use
current.
JS: That's close to what I've
already said.
... However, I would like you and Joanie to reply.
RS: But you replied?
JS: Yes.
RS: Has Bogdan replied back to you?
JS: Not yet.
... And unfortunately, Bogdan's email was not sent to the
mailing list, so it is quasi-private.
RS: But, again, for the ATTA, we'll use the current value; not the cached.
JS: Ok.
RS: I'll reply to him saying that then.
<clown> https://github.com/w3c/aria/pull/533
JS: Rich had indicated we needed interfaces for ATTAs.
<clown> https://rawgit.com/boggydigital/aria/patch-2/core-aam/core-aam.html#focus_state_event_table
JS: Bogdan provided a pull
request (see URL above)
... There is a new Microsoft UIA column (see the rawgit URL
above).
... Note that he's using current here.
... Is this fine? If not, I suggest you comment on the pull
request itself.
RS: I have no problem with that.
JS: By the way, Bogdan also
indicated he was looking for someone from Microsoft to join us
at these meetings.
... Anyway, are you ok with what he did for the focus table so
I can pull it in?
RS: Sure.
<clown> https://github.com/w3c/aria/pull/532
JS: There is a pull request from
Bodgan for this as well.
... He says to use localized control type of heading.
<clown> https://rawgit.com/boggydigital/aria/patch-1/core-aam/core-aam.html#role-map-heading
<clown> https://lists.w3.org/Archives/Public/public-aria/2017Mar/0010.html
JS: See urls above.
... In an email he sent to the public list (URL above), he
stated that he's requested control types for heading and header
and the like.
... So you're ok with that pull request for the heading
change?
JD: Question, is it accurate that the pull request is for a mapping to UIA API which Bogdan has requested, but which does not yet exist for his platform?
JS: Yes.
JD: Can we update the Core AAM based on that?
JS: We've done it
before....
... How much longer will we be writing testable statements?
RS: I'm making progress, but there are still quite a few remaining.
JS: How is Joanie doing on the mappings?
RS: She said she'd be done in a week?
JD: That's for the ATTA.
JS: If there's no progress that's alright.
RS: I think she's focusing on the bridge first.
JS: Do you mind me brining it up every week?
JD: It doesn't matter either way.
17: 01:50 <joanie> ASSERTION: property
AXRoleDescription is alert dialog
... 01:50 <joanie> STATUS: FAIL
... 01:52 <joanie> ACTUAL VALUE: web alert dialog
JD: The above came from the ARIA channel.
<clown> https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#role-map-alertdialog
JD: Should I do a pull
request?
... Should I file something first?
JS: I'd like something filed first.
JD: OK
https://lists.w3.org/Archives/Public/public-aria-test/2016Sep/0007.html
https://lists.w3.org/Archives/Public/public-aria-test/2016Sep/0010.html
https://lists.w3.org/Archives/Public/public-aria-test/2016Sep/0011.html
<richardschwerdtfeger> you win
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) Found embedded ScribeOptions: -final *** RESTARTING DUE TO EMBEDDED OPTIONS *** Default Present: Joanmarie_Diggs, Joseph_Scheuhammer, Rich_Schwerdtfeger, Bryan_Garaventa Present: Joanmarie_Diggs Joseph_Scheuhammer Rich_Schwerdtfeger Bryan_Garaventa Found Scribe: joanie Inferring ScribeNick: joanie Found ScribeNick: clown Found Scribe: joanie Inferring ScribeNick: joanie ScribeNicks: clown, joanie Found Date: 14 Mar 2017 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]