16:22:32 RRSAgent has joined #openui 16:22:32 logging to https://www.w3.org/2020/04/24-openui-irc 16:22:39 set the topic: Agenda for April 24: https://lists.w3.org/Archives/Public/public-open-ui/2020Apr/0005.html 16:23:13 Topic Agenda for April 24: https://lists.w3.org/Archives/Public/public-open-ui/2020Apr/0005.html 16:26:53 Meeting: April 24 Telecon 16:28:57 set the topic: Agenda for April 24 https://lists.w3.org/Archives/Public/public-open-ui/2020Apr/0002.html 16:31:33 Zakim, this is the April 24th telecon for Open UI; agenda is here: https://lists.w3.org/Archives/Public/public-open-ui/2020Apr/0002.html 16:31:33 got it, gregwhitworth 16:33:41 gregwhitworth has changed the topic to: Agenda for April 24: https://lists.w3.org/Archives/Public/public-open-ui/2020Apr/0005.html 16:55:39 Zakim, start meeting 16:55:39 RRSAgent, make logs Public 16:55:40 please title this meeting ("meeting: ..."), gregwhitworth 16:55:59 meeting: April 24th Open UI Telecon 16:59:49 present+ Greg Whitworth 17:01:21 stephstimac has joined #openui 17:01:42 Levi has joined #openui 17:01:43 chrisdholt has joined #openui 17:01:54 present+ 17:01:59 present+ Stephanie Stimac 17:02:00 Present+ Levi Thomason 17:02:12 present+ Chris Holt 17:02:25 scribenick: gregwhitworth 17:02:44 agenda: https://lists.w3.org/Archives/Public/public-open-ui/2020Apr/0005.html 17:03:28 Topic: Interactive elements within a select 17:03:38 https://github.com/WICG/open-ui/issues/74 17:06:16 Greg: Due to ARIA guidelines, we should not allow interactive elements inside the option elements 17:07:39 Confirming, we would still allow for styling a checkbox appearance inside the option, as in the linked github issue, we just won't allow keyboard interaction and focusable elements within the option element? 17:07:52 Greg/Chris: Confirmed and agreed 17:10:12 Levi: What about combo box and searchable lists? Do they allow interactive elements in the searchable part? Such as a list of active items. 17:10:21 Greg: Out of scope for current select proposal 17:10:50 Chris: Not a reason to overload select with combo box behavior. 17:14:04 RESOLVED: Do not allow interactive elements within an option 17:14:11 TOPIC: Select anatomy 17:14:20 https://github.com/WICG/open-ui/issues/73 17:14:44 https://onedrive.live.com/edit.aspx?resid=5ACBE28A578FB511!3053406&ithint=file%2cxlsx&authkey=!ACNTiEkb50fOYJ0 17:16:57 eisenbergeffect has joined #openui 17:17:16 Levi: there is a top part or a bottom part, can they search them or not. They all seem to be functional changes but the concept is a top and bottom parts 17:18:12 Levi: Speaking from the component teams we'll need to be able to have the tags to represent the states in the bottom options 17:20:03 Greg: Technically, the platform select element does support these things it is just difficult to use and not clear. This is probably a WHATWG conversation. 17:21:40 ACTION: gregwhitworth to open a new issue for the anatomy for button to allow for tag type selection 17:23:28 Levi: normally the design docs will have the sub-parts in the design specs 17:23:43 gregwhitworth: that's good to know because it's hard to decipher them from code 17:32:45 Levi: there currently aren't any implementations of a design system with listbox so I'm hesitant to agree with this. 17:34:05 gregwhitworth: that's a valid point, but the ones that have menu are technically for items and I primarily want to expose this container. If this was a dropdown I'd agree with the menu 17:34:55 chrisdholt: I'm curious what role/behavior comes into account when naming. They visually may be the same, function and semantics are very different. So I'd wonder, how do we hold tension between visual and function 17:35:32 Levi: yes, I can kind of see this. I'll go over the research and it may be missing something 17:37:45 ACTION: Levi to review research and provide feedback on PR 17:38:21 Levi: it would be good to understand if we should include native usage in the research 17:39:12 chrisdholt: I wouldn't want to throw out content because people use native 17:49:21 Levi: Ant is very interesting, the props and the parts in HTML are conflicting for example. All of their text refers to it as a menu 17:49:56 chrisdholt: it would be good to understand how to weight the content, is the HTML more important or are the props/api surface? 17:50:11 chrisdholt: sometimes it's compat, they desire to change but can't 17:50:40 Levi: we ran into this as well, when people are talking about it they may refer to it in a different way 17:50:55 Levi: yeah they use item and option as well as in other areas 17:51:39 chrisdholt: the platform doesn't have the same restrictions so I end up having to contain numerous other things due to having to recreate them 17:51:48 chrisdholt: so this may lead to convulution of naming 17:55:00 ACTION: Levi to add in naming support for subparts similar to specimens 17:55:05 Zakim, end meeting 17:55:05 As of this point the attendees have been Greg, Whitworth, Stephanie, Stimac, chrisdholt, Levi, Thomason, Holt 17:55:07 RRSAgent, please draft minutes 17:55:07 I have made the request to generate https://www.w3.org/2020/04/24-openui-minutes.html Zakim 17:55:10 I am happy to have been of service, gregwhitworth; please remember to excuse RRSAgent. Goodbye 17:55:14 Zakim has left #openui 17:56:53 RRSAgent, please make logs public 17:57:13 rrsagent, please create the minutes v2 17:57:13 I have made the request to generate https://www.w3.org/2020/04/24-openui-minutes.html gregwhitworth 18:09:54 rrsagent, bye 18:09:54 I see 3 open action items saved in https://www.w3.org/2020/04/24-openui-actions.rdf : 18:09:54 ACTION: gregwhitworth to open a new issue for the anatomy for button to allow for tag type selection [1] 18:09:54 recorded in https://www.w3.org/2020/04/24-openui-irc#T17-21-40 18:09:54 ACTION: Levi to review research and provide feedback on PR [2] 18:09:54 recorded in https://www.w3.org/2020/04/24-openui-irc#T17-37-45 18:09:54 ACTION: Levi to add in naming support for subparts similar to specimens [3] 18:09:54 recorded in https://www.w3.org/2020/04/24-openui-irc#T17-55-00