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

Hello there,
We reviewed this today in a breakout, and we are quite concerned with the amount of attributes and methods this is adding on every single element. We believe this would add a lot of additional complexity (e.g. what happens when `<body>` is a popup? Or when table elements are popups? Or when form elements are popups? Or replaced elements?) that is not actually required for addressing the use cases that popup is meant to address. Furthermore, this makes the API itself clunkier and more verbose, as now names need to be distinct from any other global name, not just names on the same element. It is also inconsistent with the rest of HTML, which typically defines new elements for things like that (e.g. we didn't add a `dialog` attribute to `HTMLElement`, we added a `<dialog>` element). We understand that this design enables some possibilities that having a separate element does not, but on balance, we don’t think the tradeoff is worth it.
We would prefer to see the popup functionality as one or more separate element(s). Any attributes specified on the popup trigger (`popuptoggletarget`) could be global attributes.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/743#issuecomment-1233130208

You are receiving this because you are subscribed to this thread.

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

Received on Wednesday, 31 August 2022 16:01:56 UTC