I suppose this is a limitation of qtwebkit currently. Unless the W3C specification makes that behavior mandatory I don't think that it is a genuine bug. However, you should test with the Oxide engine coming soon, as it will probably resolve this issue.
I suppose this is a limitation of qtwebkit currently. Unless the W3C specification makes that behavior mandatory I don't think that it is a genuine bug. However, you should test with the Oxide engine coming soon, as it will probably resolve this issue.