So iOS has some major bugs with input objects in iFrames, the upshot of which is that if you use input fields in a Visualforce page in the Salesforce1 mobile app, you get to deal with those bugs.

If you put an input field in a VF page, type in it, then click to move the cursor, you'll no longer be able to type until you hide and show the keyboard. My question is has anyone found a work around for this?

ContentEditiable elements suffer from the same issues.

This page is enough to demonstrate the problem:

<apex:page standardController="Account">
        <apex:inputField value="{!Account.Name}"/>

Using window.open() to get a non-framed window does result in things working correctly, but that's not going to cut it for the majority of use cases.


Using < apex:inputText / > or HTML-5 input component < input type="text"/ > resolves the issue. I tested this out on IOS 8

  • Haven't gotten around to testing this yet, will mark accepted once I have! – Matt Lacey Sep 25 '14 at 2:14

Suggested answer from SFDCBAT does NOT work.

Two possible known workarounds are: 1. to use window.open(url), which doesn't use iframe, 2. dismiss virtual keyboard or use prev/next button to jump on next field

Reference to known issue on success.salesforce.com: https://success.salesforce.com/issues_view?id=a1p30000000T5l1AAC


I tried by adding docType="html-5.0" into and use but the problem still not resolves. Could you please give us more details?

  • Zah, since you are after more details rather than answering, i suggest to post this as a comment (but you need to earn reps for it) or raise a new question and link this one.. Thanks. – Vamsi Krishna Gosu Oct 29 '14 at 3:26

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.