Re: [w3ctag/design-reviews] The Popup API (Issue #743)

Thanks for the great F2F discussion just now. I think we better understand your concerns, which is helpful. I hope we were able to answer at least some of them in the meeting.

As mentioned, I wrote up a [fairly detailed document](https://open-ui.org/components/popup.proposal.alternatives) that goes through a nearly-complete design for each of 3 approaches: `<popup>` element, CSS, and Javascript.  (It also talks about an old version of the content attribute.) Note that this document is somewhat rough, as it was developed while OpenUI was discussing the best fix for the problems with the `<popup>` element approach. However, I think it's still fairly illustrative of what the API would look like in each case.

But in particular, I want to point out [the CSS version in that doc](https://open-ui.org/components/popup.proposal.alternatives#alternative-css-property), since that's what came up during the meeting. That section details what a CSS-based pop-up API would look like, and walks through the big issues. In my view at least, the CSS approach is the **most fundamentally broken** of the four approaches in that doc. But take a look and see what you think.

Quick side note: your questions are all great. They're ones that the OpenUI also asked, and it took us significant conversation and exploration to get where we are today, with the content attribute approach. I'm happy to walk you through how we came to that conclusion for any piece of the API, to double-check that we made the right decisions along the way.

At this point, we'll wait here and try to address any followup questions you have. If you feel it'd be useful to have another high-bandwidth F2F to discuss this, we're more than happy.

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

Message ID: <w3ctag/design-reviews/issues/743/1289350269@github.com>