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

I want to echo @domenic's point about the semantics of <popup>. In general, this feels more like an abstract base class for popup-type elements than a concrete element in itself. (I'm also not a fan of <popup type="...">, I don't think <input> elements set a precedent we want to follow.)

But this leads me to a larger question of what the OpenUI group is trying to achieve. If you're trying to make high-level, semantic elements that can be styled, then <popup> isn't the right approach, you should be focusing on the specific types of popup elements you want. However, if OpenUI is trying to make generic UI building blocks that WC authors can use to compose custom UI elements (or can be used to explain behavior of existing elements), then a set of functional-but-not-semantic elements starts to make sense.

But looking at the set of elements OpenUI is considering, it's not clear that either approach is being deliberately taken. What I don't want to see is a half-and-half ad-hoc approach. Either focus entirely on high-level semantic elements, or deliberately choose a layered approach and create a new class of functional-only elements that are not meant to be used stand-alone, and then create high-level semantic elements that can be explained in terms of the generic building blocks (and polyfilled using them).

-- 
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-946019920