Your comments

Currently, you can tap "Done" and tap on the preview button again to refresh.
Textastic offers syntax highlighting for many languages including Python, but it doesn't include compilers or interpreters due to restrictions of iOS.

You will notice that all apps that support running code - like Kodiak, Codea and PythonMath for example - do not have file download capabilities. So, if I wanted to add the ability to run code in Textastic, I'd have to remove FTP, "Open In", WebDAV, Dropbox and all other means of sharing files with other apps.

These are the relevant points in the App Store review guidelines:

2.7 Apps that download code in any way or form will be rejected
2.8 Apps that install or launch other executable code will be rejected

That's a limitation that is imposed by Apple, sorry.
Just to be sure that we are talking about the same issue: can you please attach a screenshot of the problem?

You write that you can not see the keys - I can see the keys here, so you might be talking about another problem.
Does it still happen for you on iOS 7.1? It doesn't seem to occur on my device anymore in the latest iOS version.
I'm working on an update that is going to fix this issue.
It looks like you are looking for help with Apple's Pages app. This feedback forum is for the app Textastic.

Please use Apple's support resources to ask for help with Pages: http://www.apple.com/support/ios/pages/
Thanks for the info. I didn't have this problem on my machine yet. Textastic uses the standard Cocoa mechanism (NSUserDefaults) to save its preferences.

The preference file is located at ~/Library/Containers/com.textasticapp.textastic-mac/Data/Library/Preferences/com.textasticapp.textastic-mac.plist

Please let me know if you find a way to reproduce the issue.
No, since this only works for syntax definitions and not for editor plugins.
Hello,

Textastic uses iOS's UIWebView which is the same WebKit engine as used by Safari on iPad. 

There are some differences in mobile browsers when compared to desktop browsers. For example, ":hover" doesn't make much sense on touch devices, because there is no cursor that could hover over an element. The browser doesn't know the location of the user's finger before he actually taps.