Now, this probably won't be a high priority bug, since relatively few people use this browser. Also the dev is switching to QtWebEngine which is pretty much chromium based, probably won't have this issue. I just leave this here for reference since I don't know if this bug is WH specific or a QtWebKit's known bug.
Keep up the good work with this site, loving it.