|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
That workaround might have worked if our app was using triggering the page transition (the use case within jQM that is failing) through some custom JavaScript event handlers etc. Unfortunately in this case, the failure is encountered in the jQuery Mobile initialization phase where the pages are enhanced and the initial page is loaded; this occurs as soon the jQM source is downloaded through yepnope, and is parsed by the JavaScript interpreter. So the workaround in theory needs to be applied to jQM itself.
Therefore I'd agree that we should provide a way to upgrade WebKit/libwebkitgtk on RHEL 6.x.