Antonio Davide

Mmmmmh, it's very dirty but we can avoid the execution of the devicepixelratiohack in that specific website :) I agree with @llelectronics: QtWebKit bugs remains there because it is replaced...

I have noticed this "undocumented" parameter that it seems to affect the web page scaling. I have tested in this way: ``` experimental.customLayoutWidth: Screen.width / 1.5 ```

It seems to work good! ``` experimental.customLayoutWidth: Screen.width / 1.5 experimental.overview: true // What is overview?!? ``` I will make some extended tests **_EDIT**_ Something keeps rescaling the website during...

No it's disabled. Websites looks like with Pixel Ratio Hack enabled (without the "double rescale" effect) Desktop website seems to ignore that setting (they use preferredContentWidth)

Yes I can reproduce it in DiaspEU too :(

The "scrolling resize" seems to be related to experimental.preferredMinimumContentsWidth I have made a "quick and dirty" test by doing: ``` experimental.preferredMinimumContentsWidth: Screen.width / 1.5 experimental.customLayoutWidth: Screen.width / 1.5 ``` **EDIT**...

Ok, conclusion: I will keep customLayoutWidth property set along with PixelRatioHack.js so the "double resize" effect will be hidden to the user :)

Some info. experimental.customLayoutWidth: https://github.com/mer-packages/qtwebkit5/pull/5 experimental.overview: https://github.com/mer-packages/qtwebkit5/pull/9

How did you managed to compile QtWebKit and test it in Webcat?!? I have tried lots of times but it was too slow to compile inside MerSDK's VM. About your...

Mmmh, if I remember correctly the (unfinished) chromium backend, QuickSilver used some patches in order to use the hardware acceleration in Wayland. QuickSilver (Next branch): https://github.com/tworaz/quicksilver/tree/next Ozone on Wayland: https://github.com/tworaz/ozone-wayland...