Re: [w3ctag/design-reviews] HTMLPopupElement - <popup> (#680)

> > So are you saying you'd prefer to see a proposal for many new elements, all with the same basic behavior (the three qualities I mentioned in my last comment), but different accessibility roles and semantic meaning?
> 
> Yeah, that would be one approach. Or `<popup type="x">`, but then you have a defaulting issue...
> 
> It's also worth considering how to map accessibility roles to use cases, e.g. the explainer's menus, form element suggestions, content pickers, and teaching UI. It's not clear to me whether a teaching UI is one of the three you listed (tooltip, listbox, menu), for example...
> 
> And again I'll reiterate that it's a bit surprising that those three exact behaviors (and no further behaviors) perfectly encapsulate what developers want for menus, listboxes, tooltips, teaching UIs, content pickers, and form element suggestions. E.g. at least on every operating system I'm familiar with menus and tooltips have very different focus behaviors, if nothing else.

These are very good points - there will definitely be some behavioral differences among these element types. I wasn't saying all of these elements would behave the same, I was saying that they (might?) all share the three "basic" behaviors with `<popup>`, in addition to some others. Or perhaps even some tweaks to the three.

Let's [continue the discussion within the issue](https://github.com/openui/open-ui/issues/410) - there will likely be more people who can weigh in.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/680#issuecomment-943867158