-
-
Notifications
You must be signed in to change notification settings - Fork 79.1k
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
v4: Mention GPU acceleration fix in docs callout #30811
Conversation
Why not include the workaround right here? |
Personally I hadn't tested it and wasn't sure if we'd want to include some JS snippet here. I'm down to do that though if folks would prefer it. |
The snippet in #22610 (comment) assumes a bundler AFAICT. We need a snippet to cover all cases. |
This snippet cover all cases @XhmikosR because if you import Popper.js with a so we can change it, to just that line: Popper.Defaults.modifiers.computeStyle.gpuAcceleration = !(window.devicePixelRatio < 1.5 && /Win/.test(navigator.platform)); |
Cool, let's move the snippet to the docs and not link to an issue. |
site/docs/4.5/components/popovers.md
Outdated
{% 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). |
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.
"in Windows 10" or "on Windows 10 devices", but not "in Windows 10 devices".
@Johann-S can you push your proposed snippet to this branch please? |
done @XhmikosR 👍 |
4a7ab6e
to
2317ea7
Compare
Still reproduced on 4.6, |
Closes #22610
Preview: https://deploy-preview-30811--twbs-bootstrap.netlify.app/docs/4.5/components/popovers/#usage