v4: Mention GPU acceleration fix in docs callout

Closes #22610

1 files changed, 7 insertions, 0 deletions

diff --git a/site/docs/4.5/components/popovers.md b/site/docs/4.5/components/popovers.md
index bdd201b157..ed75627b1b 100644
--- a/site/docs/4.5/components/popovers.md
+++ b/site/docs/4.5/components/popovers.md
@@ -137,6 +137,13 @@ Enable popovers via JavaScript:
 {% highlight js %}$('#example').popover(options){% endhighlight %}
 
 {% capture callout %}
+##### GPU acceleration
+
+Popovers sometimes appear blurry in Windows 10 devices due to GPU acceleration and a modified system DPI. The workaround for this in v4 is to disable GPU acceleration as needed on your popovers. [See this issue for details and a suggested fix.](https://github.com/twbs/bootstrap/issues/22610)
+{% endcapture %}
+{% include callout.html content=callout type="warning" %}
+
+{% capture callout %}
 ### Making popovers work for keyboard and assistive technology users
 
 To allow keyboard users to activate your popovers, you should only add them to HTML elements that are traditionally keyboard-focusable and interactive (such as links or form controls). Although arbitrary HTML elements (such as `<span>`s) can be made focusable by adding the `tabindex="0"` attribute, this will add potentially annoying and confusing tab stops on non-interactive elements for keyboard users, and most assistive technologies currently do not announce the popover's content in this situation. Additionally, do not rely solely on `hover` as the trigger for your popovers, as this will make them impossible to trigger for keyboard users.