I use a rather obscure browser full time (qutebrowser) and they use Qt native bindings.
Due to compatibility issues Qt has _two_ backends for rendering HTML content.
One is based on webkit (qt-webkit), the other (unintuitively called qt-webengine) is actually chrome underneath.
Why chrome? because the web is now owned by chrome.
Before qutebrowser I was a heavy firefox user, but I always had chrome installed for those sites which rendered bizarrely and were obviously only tested in chrome. Too much market share is toxic in this industry I feel.
I'll try, but as usual I'll probably have a lot of things I want to do :D I'm usually at the Swiss Chaos assembly FWIW, and there might be a qutebrowser meetup as self-organized session some day.
I use a rather obscure browser full time (qutebrowser) and they use Qt native bindings.
Due to compatibility issues Qt has _two_ backends for rendering HTML content.
One is based on webkit (qt-webkit), the other (unintuitively called qt-webengine) is actually chrome underneath.
Why chrome? because the web is now owned by chrome.
Before qutebrowser I was a heavy firefox user, but I always had chrome installed for those sites which rendered bizarrely and were obviously only tested in chrome. Too much market share is toxic in this industry I feel.