-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bikeshed: what should <popup> be called? #416
Comments
Just a gut reaction, and this is purely subjective, but I think "popup" in this case feels redundant as all the elements being proposed in the current |
I would prefer shorter and easy-to-spell names for HTML, generally. (c.f. misspellings of So, similar comment about
|
Pairing dialog to popup would necessarily mean popup contains interactive content. Like a 2 way interaction. Is that always the case? |
I think this allows for both types of content, whereas the inverse wouldn't be true.By choosing dialog it may or may not have it, but both are enabled which I think is a win. |
Hi there 👋 This item is labelled for discussion in the next teleconference. @mfreed7, as an editor of the proposal and creator of the issue, would you be available and interested in discussing this in the teleconference for additional feedback? If so, would this week or next week would best for you? I’m also curious if anyone has assembled any pro/con lists applied to |
@jonathantneal this might be stale? see Mason's pr #490 for the updated |
Thanks for the ping - this is definitely stale. In fact, I'm going to close this. There are some issues around naming, but I'm not quite ready to discuss them tomorrow. |
See this comment for more context. But the direction the
<popup>
proposal is heading is toward an accessibility mapping to role="dialog". And a proposed semantic definition of<popup>
is:Given the above, it feels like instead of "
<popup>
", the element name should better-indicate its connection to dialogs.Some starting ideas:
<popupdialog>
<transientdialog>
What other ideas do folks have?
The text was updated successfully, but these errors were encountered: