diff options
author | Varunram Ganesh <vrg2009@ymail.com> | 2018-05-15 22:59:51 +0300 |
---|---|---|
committer | Patrick H. Lauke <redux@splintered.co.uk> | 2018-05-15 22:59:51 +0300 |
commit | d6ee126713545ad729969a5a093ab50300372dc2 (patch) | |
tree | 210356911ad0ca308f851be25805744b21e9680a | |
parent | f42ef5fa690e1a36764dceef983f15e72ea822be (diff) |
[trivial] Rewording in tooltips. Closes #26467 (#26521)
-rw-r--r-- | docs/4.1/components/popovers.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/4.1/components/popovers.md b/docs/4.1/components/popovers.md index 14a1ac9b37..f781c7162f 100644 --- a/docs/4.1/components/popovers.md +++ b/docs/4.1/components/popovers.md @@ -18,7 +18,7 @@ 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 anchors that wrap across multiple lines, popovers will be centered between the anchors' overall width. Use `white-space: nowrap;` on your `<a>`s to avoid this behavior. +- When triggered from anchors that wrap across multiple lines, popovers will be centered between the anchors' overall width. Use `.text-nowrap` on your `<a>`s to avoid this behavior. - Popovers must be hidden before their corresponding elements have been removed from the DOM. Keep reading to see how popovers work with some examples. |