-
-
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
Update tooltip docs to explain potential overflow boundary issue #26844
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please revert the change on assets/css/docs.min.css
@Johann-S: I can't confirm what this documents is right, can you confirm? |
docs/4.1/components/tooltips.md
Outdated
{% capture callout %} | ||
##### Usage with overflow `auto` and `scroll` | ||
|
||
When the parent container has the CSS property `overflow` set to values `auto` or `scroll` (for example when used within `.table-responsive`) the tooltip has weird flickering behaviour. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's describe what happens instead of saying "it has weird behavior." The current suggestion indicates we have no idea why it happens.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When the parent container has the CSS property
overflow
set to valuesauto
orscroll
(for example when used within.table-responsive
) the tooltip's placement changes tobottom
but still keeps original placement's positioning.
but that sounds a bit weird as we're documenting a bug :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We describe a particular use case to help folks
Fixes #26836
Following #26842
#26836 (comment)