- From: Mason Freed <notifications@github.com>
- Date: Thu, 01 Sep 2022 21:13:10 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/743/1235048116@github.com>
Thanks for the review! So in OpenUI we discussed this alternative (a `<popup>` element) at length, over roughly a year and with 10+ meetings dedicated to this specific topic. What would your solution be to the [accessibility and semantic issues](https://open-ui.org/components/popup.proposal.alternatives#alternative-dedicated-popup-element) with that approach? (Our eventual conclusion was that there wasn’t a good solution, and the attribute approach was therefore superior. It also happens to be more powerful.) Also recall that the TAG closed my [design review for `<popup>`](https://github.com/w3ctag/design-reviews/issues/680#issuecomment-988119446) based on these concerns, which is when we went in the global attribute direction. I think we’d agree that this adds several new attributes, but only one (`popup`) truly confers new behavior on any element. The other two (`anchor` and `defaultopen`) simply modify that behavior. There are certainly precedents for global attributes that modify the behavior of any element, e.g. `contenteditable` or `tabindex` or even the `aria-*` attributes, right? Can you help me understand why this is different? As for limiting the list of elements, we could definitely do that. However, should we restrict that list just because we don’t have a specific use case in mind right now for `<input popup>` or even `<table popup>` or `<body popup>`? Web developers are amazingly creative people. Of course, if there is some sort of incompatibility or reason not to support the attribute on an element, a restriction would be in order. We had such a discussion about `<dialog>` on https://github.com/openui/open-ui/issues/520, and decided that even there it makes sense to allow the `popup` attribute. How would you go about deciding which elements deserve `popup` support and which don’t? Thanks again for your review! Besides the attribute vs element issue, were there any other comments on the behaviors it confers? > Hi @mfreed7 thanks for that! Do you have any additional info on feedback/support from additional stakeholders (implementers)? Some additional TAG feedback incoming from our session today. The Gecko folks have been involved in our OpenUI discussions of the feature, and have offered some great feedback which we’ve incorporated. I wouldn’t say we have official support just yet from other implementers though. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/743#issuecomment-1235048116 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/743/1235048116@github.com>
Received on Friday, 2 September 2022 04:13:23 UTC