Open bwaismeyer opened 9 years ago
This is a good point that I was noticing when I was running through the examples on your previous issues. I will make a change so that tooltips and popovers will be attached to the closest .shiny-input-container
. This should help make the trigger region more consistent. That is a quick fix that at least addresses some of your issue. I will push and updates version and look at your issue more closely after I work through all the other issues. Thanks
Awesome and thanks, Eric!
Currently, the region of an element that can be interacted with to trigger a popover seem to be inconsistent. It appears to vary both by element type and trigger type.
For example, here is an example with two kinds of shiny elements (
radioButtons
v.inputSliders
) with two kinds of popover triggers (click
v.hover
).The popover for each element behaves differently. In the order the elements are presented, the popover responds to interactions with...
It would be nice if popover response was consistent across element types and trigger types.
I think having the popover occur only during interactions with non-input regions makes the most sense (as otherwise users may have to engage inputs to see desired information). But I'm biased by my project needs. :smile:
Alternatively, allowing us to choose something like
trigger_region
would work great too...Thanks again for your work and patience, Eric!!