This is probably due to a dpi webview issue with the older Webkit implementation. This will go away as soon as we switch to Oxide.
This is probably due to a dpi webview issue with the older Webkit implementation. This will go away as soon as we switch to Oxide.