[ 
https://issues.apache.org/jira/browse/CB-6754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shazron Abdullah updated CB-6754:
---------------------------------

    Priority: Major  (was: Blocker)

> Keyboard Shrink View breaks fixed header as virtual keyboard comes up. Also 
> when the input field is positioned fixed at bottom and tapped, it brings a 
> gap between soft keyboard and itself.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CB-6754
>                 URL: https://issues.apache.org/jira/browse/CB-6754
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Plugin Keyboard
>         Environment: IOS
>            Reporter: Sameer Ahmed Khan
>              Labels: Cordova, Keyboard, iOS7
>
> There are two major problems from iOS7 with cordova keyboard plugin.
> First Problem (With Fixed Headers):
> As I set "Keyboard.shrinkView(true)" to make the fixed positioned header and 
> footer available when the virtual keyboard showed up and stayed on the screen 
> as user scrolled (as it happens on Android), but nothing as such happened. 
> I also tried various combinations of meta tags for viewport but that didn't 
> help either. So I had to follow a hack and made the "fixed" positioned 
> headers "absolute" when user tapped on input text fields.
>  
> <meta name="viewport" content="width=device-width, height=device-height, 
> initial-scale=1.0, maximum-scale=1.0, target-densityDpi=device-dpi" />
> Second Problem:
> (With Input text field fixed at bottom)
> This is a major problem. When the input field is fixed at bottom and user 
> taps on it. The virtual keyboard shows up, however there is a gap between 
> keyboard and input text field. It really looks ugly. 
> The length of gap changes when you tap on input field either from the bottom 
> of page or somewhere amid the page. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to