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

Just to add a bit more detail to the answer above, I've updated the explainer with a summary section detailing "why an attribute instead of an element":

https://open-ui.org/components/popup.research.explainer#why-a-content-attribute

Here is the summary paragraph of that section:

> By having `popup` be a content attribute that purely confers behavior upon an existing element, the above problems are nicely resolved. Semantics are provided by elements, and behaviors are confered on those elements via attributes. This situation is exactly analogous to `contenteditable` or `tabindex`, which confer specific behaviors on any element. Imagine a Web in which those two attributes were instead elements: `<contenteditable>` and `<tabindex index=0>`. In that Web, many common patterns would either be very convoluted or simply not possible.

Hopefully this helps.

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

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