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

Andrey Kurdyumov commented on CB-6444:
--------------------------------------

Even this is looks like not Cordova issue, but issue with underlying WebView I 
think this is enough important for Cordova users to be fixed by Cordova.

I have following solution for that issue particularly.
1. Add Keyboard plugin
2. setup handler for onhinding event
Keyboard.onhiding = function() {
    document.body.scrollLeft = 0;
}

And what I want is add that to the actual Keyboard plugin and not keep it as 
well-known problem with given solution. To have backward compatibility with 
already existing code where scrolling to top is not intended behaviour we could 
add switch which is off by default and all users which have this issue could 
enable. This switch should be also documented, so people would be more aware 
about issue when looking on the plugin. 

If this is sounds good, then I could do all necessary lifting with the code and 
create pull request.

> iOS issue with fixed positioned elements and keyboard
> -----------------------------------------------------
>
>                 Key: CB-6444
>                 URL: https://issues.apache.org/jira/browse/CB-6444
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS, Plugin Keyboard
>         Environment: iOS 7.0, iOS 7.1, iOS 6.1
>            Reporter: Andrey Kurdyumov
>
> 1. Create blank Cordova application.
> 2. Made following changes:
> index.hmml
> Replace content of div with id="deviceready" with following content
> <input type="text"/>
> <input type="checkbox"/>
> js/index.js
> comment line
> app.receivedEvent('deviceready');
> css/index.css
> in the class .app
> change position:absolute to position: fixed
> 3. Build app and launch it
> 4. Touch text box. Keyboard should popup
> 5. Touch checkbox. Keyboard is shown, but all page moved a bit bottom.



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

Reply via email to