-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
feat: Add popover types #4378
feat: Add popover types #4378
Conversation
Should be all bueno here, rts might need a fix up for the reflected attrs, depending on whether we consider that an issue |
| 'toggle' | ||
| undefined | ||
| SignalLike<'hide' | 'show' | 'toggle' | undefined>; | ||
popoverTargetAction?: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will set the property whereas popoverTarget will set the attribute due to the fact the property is actually popoverTargetElement (and takes an element reference rather than an idref string).
This mismatch might be confusing to people?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've just remembered I think the property for action reflects to the content attribute so it might be fine?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, should actually be okay because of that.
Reference:
popover="hint"
hasn't yet landed in the spec and as such is perhaps questionable. It seems likely that it will and I figure jumping the gun on implementation might be slightly better than needing to be pinged to add it later (as it's not a spec I'm watching), but happy to remove it if it's undesirable.