Hi Dave,
This seems to be an old issue with WebkitGtk, maybe it's not fixed yet ?
Here is a link to the discussion about it: