-
Notifications
You must be signed in to change notification settings - Fork 33
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
Graphics error on Intel videocards #428
Comments
I cannot confirm this on my latest Version 14.0b Browser, you should add a link to a page, where such exists. |
try to disable |
Certainly error with the graphics, did you read release notes, I think not otherwise this posting will be not needed. |
Doesn't matter where anyway, because it happened everywhere. (It is the DuckDuckGo image search in case you must know.) solved the problem. Thanks. Feodor2, I read your release notes, but I did not realize this would happen. I thought that what you meant was something other than this. May I suggest that you write the release notes in Russian, but in a careful writing style, plus the normal English release notes? The computer I used at this time is ThinkPad X201i, and the graphics chip it uses is "Intel HD Graphics." I have been hospitalized since a few weeks ago, and I will probably stay hospitalized for another several weeks unless I perish here. Until then I cannot test this browser on any of my other computers. So, the small and light-weight X201i is the only one with me right now. |
So this is about Intel only and I know an option that fix this but hinders performance
Please don't :I see russian aliexpres always fails miserably, and it makes me laugh, yes my english may be bad too, but that release notes I have written myself and think good enough, if you never seen graphics errors then you know it now. Once a great meme |
From 68.14.1 Intel for Direct9 are blacklisted, but you can enable it by layers.acceleration.force-enabled |
It looks like images and texts are extended downwards in a funny way on Mypal68 Version 68.14.0b. This seems to happen everywhere not just at Duck, but every website and blog.
The text was updated successfully, but these errors were encountered: