-
-
Notifications
You must be signed in to change notification settings - Fork 78.9k
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
Popover/tooltip selector option needs documentation #4215
Comments
I had some trouble with this too, thanks! |
I agree on this, it's confusing. |
Got confused by the documentation as well. Thought data-selector was a way to point to another element in the page so its contents are displayed inside the popover, instead of the data-content attribute contents. |
Thanks for the explanation @jakepetroules ! |
Please submit a pull request with the suggested edits and we can ge them in there. Until then, closing out. Thanks! |
Same issue here using 2.3.0 ... bootstrap is ignoring the data-trigger (atleast) when using the selector as mentioned in this bug report. |
Pull request on the docs meaning forking the javascript.html file and editing? Doing that. Is that really the preferred way? Seems like each section should live in a mustache/other template and the whole docs should be dynamically assembled. |
@jakepetroules Thanks for clearing it up. |
Read somewhere that jquery now suggests attaching ".on" to the document. (instead of the body as in this thread) So you might try... It seems to work for me. (although admittedly didn't spend a lot of time on this) |
the documentation is still cryptic for tooltips |
Thank you. It really helped me out |
The documentation for the selector option for popovers and tooltips currently states "if a selector is provided, tooltip objects will be delegated to the specified targets". This description is not very helpful and appears to confuse a good number of people, including myself until I figured out what it actually does (also see #2091).
Explanation: 'selector' is used internally in conjunction with jQuery.on in order to allow markup dynamically inserted in the DOM, to trigger tooltips and popovers. I've created an interactive jsFiddle illustrating its usage: http://jsfiddle.net/KPeKS/4/
tl;dr: selector = jQuery.on support
I therefore propose that the documentation be improved, making note that 'selector' makes the plugins use jQuery.on and a short explanation of what that does, for those who may not be familiar with the function, along with the following sample code:
I'll leave exactly how it might be worded to @mdo / @fat.
The text was updated successfully, but these errors were encountered: