I experienced this same problem when using WebKit Nightly Builds, so my guess is that this might be an issue related with the new WebKit engine. Before this is recognized (and fixed by either side, or both), maybe our only solution is to use browsers that use older WibKit engines (such as Safari 3), or those which use different engines (like Firefox or Camino).
