From 1a569bab3f5f7c9711dfdb0ecd134fc7f9c1c32d Mon Sep 17 00:00:00 2001 From: Mark Otto Date: Wed, 18 Oct 2017 14:22:26 -0700 Subject: [PATCH] few popover docs changes to clarify things mentioned in #24005 --- docs/4.0/components/popovers.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/4.0/components/popovers.md b/docs/4.0/components/popovers.md index b8356b0d20..c4034da98a 100644 --- a/docs/4.0/components/popovers.md +++ b/docs/4.0/components/popovers.md @@ -19,10 +19,10 @@ Things to know when using the popover plugin: - Specify `container: 'body'` to avoid rendering problems in more complex components (like our input groups, button groups, etc). - Triggering popovers on hidden elements will not work. - Popovers for `.disabled` or `disabled` elements must be triggered on a wrapper element. -- When triggered from hyperlinks that span multiple lines, popovers will be centered. Use `white-space: nowrap;` on your ``s to avoid this behavior. +- When triggered from anchors that wrap across multiple lines, popovers will be centered between the anchors' overall width. Use `white-space: nowrap;` on your ``s to avoid this behavior. - Popovers must be hidden before their corresponding elements have been removed from the DOM. -Got all that? Great, let's see how they work with some examples. +Keep reading to see see how popovers work with some examples. ## Example: Enable popovers everywhere @@ -132,7 +132,7 @@ sagittis lacus vel augue laoreet rutrum faucibus."> ### Dismiss on next click -Use the `focus` trigger to dismiss popovers on the next click that the user makes. +Use the `focus` trigger to dismiss popovers on the user's next click of a different element than the toggle element. {% callout danger %} #### Specific markup required for dismiss-on-next-click -- 2.47.2