Thanks for your suggestion. The future iOS build shouldn't have this problem, since it will be a native app (instead of web). But I'll keep that in mind as an alternative input method.
