[ 
https://issues.apache.org/jira/browse/CB-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797718#comment-13797718
 ] 

Adrian Vasiliu commented on CB-4862:
------------------------------------

As far as I can see, this still holds for Cordova 3.1: even if 
KeyboardShrinksView is set to false and height=device-height is not set in the 
meta tag, the view is resized when the keyboard comes up.

On the other side, the Cordova 3.1 documentation states that 
height:device-height should NOT be used on iOS 7 (for good reasons, because it 
brings other troubles): 
"iOS 7 issues: Remove the values "width=device-width, height=device-height" 
from your meta tag "viewport" attribute' 
(http://cordova.apache.org/docs/en/3.1.0/guide_platforms_ios_upgrading.md.html#Upgrading%20iOS).
 See also https://issues.apache.org/jira/browse/CB-4323 .

Hence, I wonder if this issue shouldn't be reopen (for Cordova 3.1).



> ios 7 keyboard resizes the page even with KeyboardShrinksView set to false
> --------------------------------------------------------------------------
>
>                 Key: CB-4862
>                 URL: https://issues.apache.org/jira/browse/CB-4862
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 2.8.0
>         Environment: ipod 5th gen ios 7 and simulator for ios 7
>            Reporter: Jake Williams
>            Assignee: Shazron Abdullah
>              Labels: ios7
>
> We have a page with a fixed footer and some inputs.  In previous ios versions 
> the page would be pushed up when an input was focused and the keyboard came 
> up.  In ios 7, the page height is reduced to the available space after the 
> keyboard appears and the footer covers the input (depends on the position of 
> the footer, but it does happen sometimes).  There is also a problem where the 
> input could be beneath the keyboard if you have multiple inputs and you use 
> next/previous to move between them.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to