As noted in https://bugs.webkit.org/show_bug.cgi?id=30311, my original patch introduced an error. However the patch in 30311, while accepted is still produces faulty behaviour.. Basicly changing the global default encoding, has no effect unless the local encoding is set to "", (it defaults to latin1). I think a better solution would be to either only use the default value in the global option. Or to substitute the empty string by latin1 in QWebSettings::apply. The first is not easy to implement the latter will break the first test, also implemented by the 30311 patch. I think the second solution would be more in line with other QWebSettings settings, where the default empty settings signifies using a lower level webkit default?
There is no problem, my bad.