Among other issues, Otter displays blurry text with QtWebEngine backend on my Windows 7. This is not ClearType on/off, ClearType is always on, but seems like Blink uses own algorithm or ClearType settings, giving more blur as result. But WebKit-based Otter gives the same anlialiasing as the system itself, Opera 12 and Firefox, which makes it usable.
This is not just Otter problem, QupZilla-QtWebEngine has it too. If QtWebEngine is the future of Otter, I afraid to that future.
Could you please provide at least two screenshots of how it should look (one) and what you actually see (another)?
QtWebEngine (blurry)
(https://dndsanctuary.eu/imagecache.php?image=http%3A%2F%2Fi78.fastpic.ru%2Fbig%2F2016%2F0712%2F3f%2F63a9db9767419f15016908930c1d0f3f.png&hash=2cb9d039c64e286f437d8c20732a0602" rel="cached" data-hash="2cb9d039c64e286f437d8c20732a0602" data-warn="External image, click here to view original" data-url="http://i78.fastpic.ru/big/2016/0712/3f/63a9db9767419f15016908930c1d0f3f.png) (http://fastpic.ru/)
QtWebKit (normal)
(https://dndsanctuary.eu/imagecache.php?image=http%3A%2F%2Fi78.fastpic.ru%2Fbig%2F2016%2F0712%2F2d%2F438afd764c0d938d7957c8247f94802d.png&hash=88f9e60d8e4e5d0b0a6c256f9ce480dc" rel="cached" data-hash="88f9e60d8e4e5d0b0a6c256f9ce480dc" data-warn="External image, click here to view original" data-url="http://i78.fastpic.ru/big/2016/0712/2d/438afd764c0d938d7957c8247f94802d.png) (http://fastpic.ru/)
Well, you should try the beta version of Chrome. Chromium developers are removing GDI support and use DirectWrite as a replacement. This causes blurry fonts on Chromium/Blink-based browsers. See if you experience the same level of blurriness with a beta release of Chrome (https://www.google.com/chrome/browser/beta.html). You wrote that Opera didn't produce the blurriness. I would also give Opera beta (http://www.opera.com/computer/beta) a try.
If both Opera beta and Chrome beta produce the same kind of blurriness, welcome to the greatest manifestation of developer idealism idiotism, when some maniacs, that always demand progress and don't want to maintain a little more amount of code, can even oppose common sense (and eyesight). If this is the case, please make your voice heard on the forums below.
No option to disable DirectWrite - Google Product Forums (https://productforums.google.com/forum/#!topic/chrome/Q6QGBRvULbQ)
Keep the "Disable DirectWrite" option (GDI font rendering) - Opera forums (http://forums.opera.com/discussion/1873942/keep-the-disable-directwrite-option-gdi-font-rendering)
Keep GDI font rendering as an alternative to DirectWrite - Google Groups (https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/WzivQg8_drw)
Are you serious about forcing DirectWrite upon us? - Goolge Groups (https://groups.google.com/a/chromium.org/forum/#!topic/chromium-discuss/ZVBgeMwHycQ)
Meanwhile, some Otter developer could confirm if this change in Chromium will affect Otter in the future or not.
@Freeman, at the moment revived QtWebKit (https://github.com/annulen/webkit/wiki/Comparison-with-QtWebKit-5.6) (available as -qtwebkitng packages right now) seems to be our future as default backend.
QtWebEngine simply has limited APIs, and it's not going to change anytime soon...
@Emdek, drinking a cup of tea for your health! :up: