Meeting minutes
<una> https://
presesnt+
<una> https://
there was a PR opened :)
scribenick bkardell_
<una> https://
<una> Scribenick, bkardell_
una: "we discussed how badges, pills and tags might be different - and I'd like to talk about and see if we can agree about how to define and arrange them
una: which ones should we group and which ones should we have research and proposals around?
una: One thing I noticed in "badges" is that they are often numeric - things like in your inbox or messages. This seems different than what is in the pills research page that is more like "important" or something. I want to propose that badge and pills are two differnt kinds of components we could define - I dont know if those are the right names - but are they the same semantic use case or diff
<hdv> +1 to if it is a value like a number it's different from a label
<una> bkardell_: question--when you define semantics to disucss semantics, in ARIA terms is there a difference?
<una> bkardell_: maybe in some cases, when you talk semantics, is it how we agree to discuss them or to a user is ther a difference
una: I think in this case... when I think of aria roles or connections to an element... it depends. In a website I was putting together there were little indicators of "these are for beginners" and there are other ones where it is like "you have N unread messages" and I do think there is some different aria difference there
<una> bkardell_: might be an interesting excersize to build them and see what the ARIA would look like
<una> bkardell_: is this something you would intuit or would there be semantic differences?
<una> bkardell_: unclear if they would be the same or different
una: I think with badges there needs to be some link to something else that they describe - not a sort of disconnected floating value... something that provides more context. Right now I think we are seeing a disconnect between like "4" - that requires some semantic link to what it is 4 of, but that's different from some kind of content inline that is more like just a span tag that is styled
hdv: you are convincing me una. There are other things like, like a count - that might be like a live region even and need live updating even
una: I would like to propose a resolution that we have a difference between badges and tags that they are semantically different and we should define the differences
+1 that we should define the differences
una: I think we should also resolve to use badge and tag based on the discussion last week that other things like 'pill' describe a look and feel
<hdv> +1 to both
+1 to both
<zahnster> +1 to both
<melanierichards> +1, I joined late but these words make sense to me
<silverdust> +1
<una> Proposed Resolution: Badges and Tags are unique in their semantic usage, we will define the differences
<una> Proposed Resolution: Chips and Pills are style-based naming conventions, these will fall under Tags
Resolution: Badges and Tags are unique in their semantic usage, we will define the differences
Resolution: Chips and Pills are style-based naming conventions, these will fall under Tags
<una> https://
una: so the question is whether we want a full definition proposal or just research here...
una: this one is interesting because I think definitions come from research, and that is something we should continue to follow.. So what I would like to see is that we start with research and at the end of that we can decide about whether we need more
+1 to una's
<una> Tabs Research: https://
<una> bkardell_: open Tabs research PR, block of text, let's land and then chisel away / adjust
<Zakim> hdv, you wanted to say maybe in a badge it would be something that can change and needs updating (think aria-live), whereas with a 'tag' you would not ?
<una> davatron5000: i think we need some styling changes to the website to make the research pages more digestible
<una> una: IA workshop next week for this time
<davatron5000> preview URL for tabs research https://
<una> bkardell_: different organizations, ie Igalia, use taskforces, should we use a taskforce for this
<una> una: we discussed 2 sessions ago to use this time slot to do the IA workshop overview
<Zakim> melanierichards, you wanted to talk about popup
<una> melanierichards: next steps to port everything over to OpenUI space
<una> melanierichards: havent had a chance yet but will work on this w/chairs soon
<una> melanierichards: WhatWG triage presentation of <popup> today
<una> melanierichards: after incubating proposal here, WhatWG is next step
<una> melanierichards: week after IA discussion
<una> melanierichards: anchor bogged down currently, after CSSWG discussion, need to have 1-off discussion about that, need to get explainer out
<una> una: open the issues in OpenUI & discuss here
<una> una: to prevent getting bogged down and push it forward
<una> discussion around popup vs. popover, to open issue in OpenUI and discuss furter