Is sub-pixel anti-aliasing supported in qtwebkit?



  • Is sub-pixel anti-aliasing font rendering supported in qtwebkit, under windows? How to enable it if yes?



  • Isn't that enabled by default? I can't think of a rendering path without anti-aliasing.

    If you are using QWebView, you can enable/disable rendering attributes with QWebView::setRenderHints().



  • Thanks for your reply!

    I found that it's applying the system default font rendering algorithm there, say if the cleartype is enabled qt will use cleartype, if standard font smoothing is enabled then that will be that, and so is to none smoothing mode. I found this because I was using remote desktop in WindowsXP, in which cleartype is always disabled.

    I though the webkit has its own font smoothing engine, isn't it? or does qtwebkit bring this with it or not?

    I wonder if there could be a secret trigger to let the qtwebkit using its own engine rather then the system's current setting.

    Regards
    old9



  • I though the webkit has its own font smoothing engine, isn’t it? or does qtwebkit bring this with it or not?

    WebKit does not have its own font rendering algorithm on any port. You might have been confused by Safari on Windows, which uses a port of the algorithm used on Mac.



  • oh, thanks for pointing that out... sad to know that there isn't any...

    Yes safari is kind of confusing me on this, but I once successfully triggered a different rendering mode by adding text-shadow css property, to Google Chrome. Since Chrome is also based on webkit...

    oh, and another thing, webkit has it's own css property -webkit-font-smoothing "[google link]":http://www.google.com/search?hl=en&source=hp&q=webkit+font+smoothing ,these all together made me think that there would be a hidden render engine there.



  • The property -webkit-font-smoothing is a very special case. It has been introduced by Apple and is only used by them (for both their Mac and Windows port). All the other ports ignore this parameter.


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.