-
Notifications
You must be signed in to change notification settings - Fork 8
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
A popover implementation #1583
Comments
Some notes from our initial discussion:
|
Looking at it some more, I think most of our requirements are met by
I suspect I can work around the second issue, but I'm not sure about the first. |
@kroeschl could you elaborate on your question? Are you asking how to set the Also, just in case you hadn't seen, the |
Edit: I didn't realize that we can set attributes exposed by the wrapped
Yeah, we're currently doing Nimble version bumps manually so we can check for breakages on incubating components. |
When a Nimble component is derived from a fast-foundation component, the FAST API will typically work on the Nimble one. We aim to document the supported API in the Nimble docs so if it's not documented it means either it's not officially supported or we forgot to document it. In the cases where we don't officially support it, it's usually because we provide (or plan to provide) an opinionated setting for the API and want to discourage clients from customizing it. I'm not sure which case the |
Sounds good, thanks for the explanation! With that info, I think we can just use at least the current |
I'll close this for now and we can revive it or reference it if another request comes in for similar functionality. |
😯 Problem to Solve
My app, which is in the process of migrating from AngularJS and Bootstrap to Angular and Nimble, uses popovers in several places. This is currently missing from both Nimble and Angular Material despite being included in the Material spec (as a rich tooltip). See for reference:
Examples of our usage
💁 Proposed Solution
Some solution exists to provide popover content. This would likely be either a distinct
nimble-popover
attribute or an extension of the existingnimble-tooltip
. Specifically, we're looking for programmatic open/close and configurable element positioning.This request might also just be closed and rolled into #309.
The text was updated successfully, but these errors were encountered: