16:59:24 RRSAgent has joined #aria 16:59:28 logging to https://www.w3.org/2023/10/05-aria-irc 16:59:28 RRSAgent, make logs Public 16:59:29 please title this meeting ("meeting: ..."), jamesn 16:59:36 meeting: ARIA WG 16:59:38 chair: JamesNurthen 16:59:43 agendabot, find agenda 16:59:43 jamesn, OK. This may take a minute... 16:59:45 agenda: https://www.w3.org/events/meetings/ecffaf8b-8aa7-4acc-b238-6088a86cf12f/20231005T130000/ 16:59:45 clear agenda 16:59:45 agenda+ -> New Issue Triage https://bit.ly/3tfQQqC 16:59:45 agenda+ -> New PR Triage https://bit.ly/3F3cOQg 16:59:46 agenda+ -> WPT Open PRs https://bit.ly/ARIA-WPT 16:59:57 agenda+ -> Seeking clarity on name property with div https://github.com/w3c/accname/issues/202 16:59:57 agenda+ -> Consider allowing searchbox as a child of listbox / menu https://github.com/w3c/aria/issues/2051 16:59:59 agenda+ -> Consider allowing combobox to open menus https://github.com/w3c/aria/issues/2050 17:00:02 agenda+ -> Consider creation of a fieldsize/maxlength property https://github.com/w3c/aria/issues/1119 17:00:05 agenda+ -> Monthly PR Triage https://bit.ly/all-aria-prs - Will reserve at least last 15 mins for this 17:00:20 Adam_Page has joined #aria 17:01:20 StefanS has joined #aria 17:01:51 present+ 17:02:03 present+ 17:02:07 present+ 17:02:25 scribe: Adam_Page 17:02:34 regrets+ PeterKrautzberger 17:02:47 regrets+ AndreaCardona 17:02:54 zakim, next item 17:02:54 agendum 1 -- -> New Issue Triage https://bit.ly/3tfQQqC -- taken up [from agendabot] 17:03:01 giacomo-petri_ has joined #aria 17:03:03 present+ 17:03:19 jamesn: 6 new issues 17:03:42 ... #2055 17:04:13 ... need to wait until spectranaut is back, will agenda for later 17:04:27 ... accname #205 17:05:16 melsumner has joined #aria 17:05:31 present+ 17:07:08 jamesn: there’s a whitespace project in accname, including #83 which is applicable 17:07:13 Francis_Storr has joined #aria 17:07:25 jcraig: maybe the resolution here is to not test this particular case in WPT 17:07:36 present+ 17:07:59 sarah_h has joined #aria 17:08:06 present+ Daniel 17:08:11 BryanGaraventa: we agreed to change the spec and browsers already did that work speculatively 17:08:29 ... so browsers are actually doing it correctly, but the spec hasn’t been updated yet 17:08:57 Bryan is correct about Chromium: https://wpt.fyi/results/accname/name/comp_name_from_content.html?diff&filter=ADC&run_id=5147990542516224&run_id=5101898094346240 PR preview 17:08:59 jamesn: this accname #168 issue sounds like what you’ve described, and it just hasn’t been merged 17:09:22 ... so this PR needs to get resolved so we can merge it, then write some tests 17:09:57 jcraig: I’ll pull accname #205 back; BryanGaraventa is right about this 17:10:28 ... and I’ll file a WebKit bug 17:10:49 BryanGaraventa: I’ll go back and look at accname #168 17:10:55 melsumner: I’ll help with that 17:11:08 GautierC has joined #aria 17:11:21 jamesn: next issue, accname #204 17:12:06 jcraig: needs CSS spec update 17:12:45 jamesn: would anyone like to take this? 17:12:48 melsumner: I will 17:13:24 jamesn: next issue, accname #203 17:13:38 CurtBellew has joined #aria 17:14:07 scotto has joined #aria 17:14:18 present+ 17:15:00 ... anyone want to work on this? 17:15:26 ... is it urgent? 17:15:30 jcraig: no, it can wait 17:15:40 ... will tackle in October 17:15:49 jamesn: next issue, html-aam #505 17:16:09 scotto: encountered this when defining popover mappings 17:16:24 agenda? 17:16:53 ... popovertargetaction has toggle behavior 17:17:36 ... should we let users know when a close button will actually do nothing? 17:18:26 q+ 17:18:40 ack me 17:18:49 jamesn: why does this close button even exist if the popover is already closed? 17:19:06 scotto: there could be times when you have both an open and a close button in the UI, as siblings in the primary document 17:19:18 jamesn: then one or the other should be disabled 17:19:30 q+ 17:20:16 q+ 17:20:33 ack sarah_h 17:20:34 MattKing: if you have two buttons, then you shouldn’t be using expanded/collapsed 17:20:54 q+ to say this is identical in functionality in not disabled, just not doing anything. 17:20:59 sarah_h: I don’t think we should automatically disable them since it’s not intuitive for authors 17:21:34 ... a good example is a button that always has show behavior — it would be weird to disable that when the popover is open 17:21:53 ack me 17:21:57 ack me 17:21:57 jcraig, you wanted to say this is identical in functionality in not disabled, just not doing anything. 17:22:01 MattKing: since this is just triage, we need to agenda it for next week 17:22:16 jcraig: I agree with sarah_h 17:22:26 jamesn: me too, now that I understand the example better 17:22:34 ... will agenda for next week 17:22:36 ... next issue, aria #2052 17:22:55 ... scotto, will you own this? 17:22:59 scotto: we should agenda this too 17:23:10 jamesn: okay, will do 17:23:13 zakim, next item 17:23:13 agendum 2 -- -> New PR Triage https://bit.ly/3F3cOQg -- taken up [from agendabot] 17:23:35 jamesn: html-aam #504 17:23:44 scotto: I’d like jcraig’s review on this 17:23:52 jcraig: I will 17:24:22 jamesn: next PR, aria #2054 17:24:34 ... I’ll add MattKing for review 17:24:46 CoryJoseph: I’ll review also 17:25:11 jamesn: next PR, aria #2053 17:25:14 ... editorial change 17:25:22 ... pkra has already reviewed it 17:25:31 ... I think that’s enough 17:25:42 ... if anyone else would like to review, please feel free, otherwise I’ll merge 17:25:43 zakim, next item 17:25:43 agendum 3 -- -> WPT Open PRs https://bit.ly/ARIA-WPT -- taken up [from agendabot] 17:25:52 jamesn: WPT open PRs 17:26:00 ... there are 11 here, jcraig — do any need attention? 17:26:16 jcraig: yes, we’re trying to figure out focus areas for Interop 2024 this week 17:26:21 jamesn: okay 17:26:28 ... #42234 17:26:50 jcraig; every form element has an embedded control 17:26:59 ... it’s a long one, but not difficult to review 17:27:15 jamesn: I’ll review this one 17:27:22 ... next, #42203 17:27:34 jcraig: this is effectively editorial 17:27:39 ... quick, easy review 17:27:45 ... good first review 17:27:55 Rahim: I’ll review 17:28:10 jamesn: next, #42093 17:28:22 jcraig: we can pass, already approved 17:28:29 jamesn: next, #42013 17:28:34 Rahim: I’m still working on this 17:28:43 jamesn: next, #42011 17:28:59 jcraig: this is a manual test, leave for spectranaut 17:29:11 ... ditto for #41522 17:29:36 ... we’re good on all the rest 17:29:45 zakim, next item 17:29:45 agendum 4 -- -> Seeking clarity on name property with div https://github.com/w3c/accname/issues/202 -- taken up [from agendabot] 17:30:00 jamesn: accname #202 17:30:03 ... can we close this? 17:31:36 jcraig: assign it to me and I’ll close it after chewing on it some more 17:31:41 q+ 17:33:13 q+ 17:33:13 giacomo-petri_: as an author, I may want to use the title and let the browser use it as a “fallback” 17:33:25 MattKing: I think this is a case where accname should say title should *not* be a fallback for accname 17:33:34 GautierC has joined #aria 17:33:35 ... so authors can use it to be a mouse tooltip, but it wouldn’t be the accname 17:34:05 MattKing: we probably should also prohibit aria-describedby on a generic 17:34:16 jcraig: let’s file an issue on accname 17:34:22 ... giacomo-petri_, would you? 17:34:34 giacomo-petri_: yes, I’ll file an issue 17:34:46 BryanGaraventa: should we have a deep dive? 17:35:09 I almost feel like we could just clarify as an editorial thing. WDYT? 17:35:29 jamesn: let’s discuss this after the issue is created 17:35:36 zakim, next item 17:35:36 I see a speaker queue remaining and respectfully decline to close this agendum, Adam_Page 17:35:58 ack scotto 17:36:02 scotto: I also think there’s an html-aam issue here, I’ll file one 17:36:06 ack giacomo-petri_ 17:36:08 zakim, next item 17:36:08 agendum 5 -- -> Consider allowing searchbox as a child of listbox / menu https://github.com/w3c/aria/issues/2051 -- taken up [from agendabot] 17:36:20 jamesn: scotto? 17:37:02 scotto: we have common patterns where a button will invoke a popup, and that popup is a listbox but there’s a textbox at the top 17:37:34 ... typeahead to filter the list of options 17:37:46 ... per current allowance, I’d normally recommend that popup be a dialog 17:37:51 ... and then associate the text input with the listbox 17:38:14 ... we’re coming up with a new select element over in open UI, this being one of the use cases 17:38:26 ... it would require the browser to juggle the DOM 17:39:04 ... so I’ve wondered can we just allow the searchbox as a first child of listbox? 17:39:17 MattKing: I don’t get it — isn’t this just a combobox? 17:39:28 scotto: it’s not as simple as that 17:39:43 ... I’m talking about the *button* that opens the popup, where the text field is inside the popup 17:40:00 q+ 17:40:06 q+ 17:40:08 MattKing: I’m talking about just the select 17:40:14 ... I agree that the popup should be a dialog 17:40:15 agenda? 17:40:45 ... I’m just saying that the contents of the dialog; the combination of the textbox with listbox, *that* is just a combobox 17:41:30 rrsagent, make minutes 17:41:31 I have made the request to generate https://www.w3.org/2023/10/05-aria-minutes.html jamesn 17:41:48 scotto: yes, we could treat the original element as a plain button, but then if that dialog is being dynamically injected, how do we express the button? 17:41:57 ack sarah_h 17:42:02 ack me 17:42:04 ack Rahim 17:42:29 Rahim: in terms of structure of this widget, does it make sense for the search to be outside the listbox? 17:42:34 ... as a sibling? 17:42:42 scotto: per current rules, yes, it would be a sibling 17:42:45 FWIW, JS engineers in my world get this wrong ALL THE TIME 17:42:53 ... just trying to open the question of whether that’s necessary 17:43:21 ... in my own experiments, it seemed that enclosing the text box in the listbox wasn’t a huge problem 17:43:33 ... what do we gain by prohibiting it? 17:43:34 q? 17:44:02 BryanGaraventa: I’m familiar with this kind of control in Firefox 17:44:13 ... the issue I had was with virtual cursor context 17:44:46 ... you can’t see that there *is* an input 17:44:56 ... when I went looking for it, I had to turn off the virtual cursor and had to tab through instead 17:44:58 ... irritating 17:45:12 ... because a listbox is intended to be a one-line widget 17:45:20 jamesn: how do we move this forward? 17:45:33 ... create some examples and see what actual problems we encounter if we were to pursue this? 17:45:39 sarah_h: I have an example of it in a menu 17:46:14 MattKing: fundamentally, it seems like an a11y tree issue 17:46:41 ... text boxes and list boxes should stay separate 17:46:55 jamesn: path forward to prototype some cases? 17:47:01 BryanGaraventa: I can certainly test 17:47:05 zakim, close this item 17:47:05 agendum 5 closed 17:47:06 sarah_h: I’ll make some examples 17:47:07 I see 3 items remaining on the agenda; the next one is 17:47:07 6. -> Consider allowing combobox to open menus https://github.com/w3c/aria/issues/2050 [from agendabot] 17:47:15 zakim, take up item 8 17:47:17 agendum 8 -- -> Monthly PR Triage https://bit.ly/all-aria-prs - Will reserve at least last 15 mins for this -- taken up [from agendabot] 17:47:40 jamesn: need to get through some old PRs across all repos 17:47:50 ... oldest first, from 2019 17:47:56 ... accname #60 17:48:00 ... this can be closed, right? 17:48:04 BryanGaraventa: yes 17:48:20 jamesn: next, accname #66 17:49:06 jcraig: there will be conflicts 17:49:11 jamesn: yes 17:50:09 jcraig: I think we should just use a standard HTML example 17:50:38 ... I’ll take assignment of this PR 17:50:43 jamesn: who wants to review? 17:50:46 BryanGaraventa: me 17:51:08 jamesn: next, accname #90 17:51:41 ... why hasn’t this been merged? 17:52:19 ... looks like this can be merged by editors 17:53:00 jcraig: I’m suspicious of one change; I’ll add a comment 17:53:12 jamesn: next, aria #1413 17:53:21 ... I’m just going to close this, there was never agreement 17:53:27 ... and will leave the underlying issue open 17:53:47 jamesn: next, aria #1494 17:54:07 ... I thought this was done? 17:54:17 ... very simple change 17:54:23 ... something to drive validators on 17:54:58 scotto: definitely remember talking about this, maybe we just never brought it back up for re-review 17:55:47 jamesn: did we handle this with an authors MUST NOT statement in section 9. Handling Author Errors? 17:56:00 ... volunteers for review? 17:56:15 JaunitaGeorge: I’ll review 17:56:27 melsumner: I’ll also review 17:56:58 jamesn: next, html-aam #359 17:57:22 scotto: I’ve been requesting UIA help on this 17:57:51 ... mappings for UIA don’t make sense 17:58:08 jamesn: will re-ping 17:58:15 jamesn: graphics-aria #9 17:58:27 ... just needs to be merged — right, dmontalvo? 17:58:34 dmontalvo: yep, we can merge 17:58:44 jamesn: done, merged 17:58:53 jamesn: next, html-aam #395 17:59:04 scotto: this one goes along with a PR I just merged 17:59:09 ... I need to check on this 17:59:11 ... we have reviewers 17:59:16 ... just need some double-checking 17:59:23 jamesn: next, html-aam #396 17:59:38 scotto: yep, I’ll take this 18:00:06 zakim, end meeting 18:00:06 As of this point the attendees have been Rahim, StefanS, Adam_Page, giacomo-petri_, melsumner, Francis_Storr, Daniel, CurtBellew 18:00:08 RRSAgent, please draft minutes 18:00:09 I have made the request to generate https://www.w3.org/2023/10/05-aria-minutes.html Zakim 18:00:16 I am happy to have been of service, Adam_Page; please remember to excuse RRSAgent. Goodbye 18:00:16 Zakim has left #aria 18:00:18 melsumner has left #aria 18:05:13 bkardell_ has joined #aria