Home/ Questions/Q 6528423
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T09:31:59+00:00

I think that focus event doesn’t work with JQuery mobile: here is my code.

  • 0

I think that focus event doesn’t work with JQuery mobile: here is my code. (when I delete the call to the library jquery mobile, it works)

<!DOCTYPE html>
<html>
    <head>
        <link rel="stylesheet" href="http://code.jquery.com/mobile/1.0b2/jquery.mobile-1.0b2.min.css" />
        <script src="http://code.jquery.com/jquery-1.6.2.min.js"></script>
        <script src="http://code.jquery.com/mobile/1.0b2/jquery.mobile-1.0b2.min.js"></script>
    </head>
    <script type="text/javascript">
        $(document).ready(function() {
            $('#acceuil').live('pagecreate', function(event) {
                $('#declencher').click(function() {
                    $('#cache').focus();
                });
                $('#declencher').trigger('click');
            });
        });
    </script>
    <body>
        <div data-role="page" id ="acceuil" >
            <div data-role="header" data-theme="a" ><h3>aaa</h3></div>
            <div data-role="content">
                <input id="cache" type="input">    
                <input type="button" id="declencher" value="declencher">
            </div><!-- content-->
            <div data-role="footer" data-theme="a" data-position="fixed"><h3> Footer </h3></div>
        </div>
    </body>

</html>
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    pagecreate event fires before JQM does some changes to DOM so I suppose the focus is lost then.

    Try switching to pageshow, especially because you want to get the focus everytime user gets to a page.

    If it still doesn’t work (there was such a case) wrap the code that triggers focus in a timeout (yes, it’s a hack 🙂 )

    setTimeout(function(){
 $('#cache').focus();
},0);

    This is a hack, but it does not depend on waiting a time interval. setTimeout() adds the function to rendering thread’s queue (which is what runs javascript and page rendering in the browser) after the given time. So in this case the function is added instantly, so it runs after the current flow of javascript code finishes. So it’s a way to make some code run right after the event handler ends. So this is not as hacky as one might think. I call it a hack, because it’s using knowledge about how the browser works and it obscures the flow of code execution.

    I recommend reading about how javascript execution and page drawing are handled by the same queue in a single thread. To anybody working with more than 20 lines of javascript.

    I am quite sure that there is only one better solution – fix it in jQuery Mobile framework itself.

    • 0