You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Greg Hrebek (Created) (JIRA)" <ji...@apache.org> on 2011/12/07 02:20:40 UTC
[jira] [Created] (CB-106) Navigation in JQuery Mobile that use
Single Document MultiPage Layouts
Navigation in JQuery Mobile that use Single Document MultiPage Layouts
------------------------------------------------------------------------
Key: CB-106
URL: https://issues.apache.org/jira/browse/CB-106
Project: Apache Callback
Issue Type: Bug
Components: WP7
Affects Versions: 1.2.0
Environment: Windows Phone 7.1 SDK & Emulator, PhoneGap 1.2.0 (pulled from GitHub on 12/02/2011), JQuery Mobile 1.0
Reporter: Greg Hrebek
Assignee: Jesse MacFadyen
Priority: Critical
The navigation and page loading of PhoneGap apps that use JQuery Mobile (JQM) for its UI will not work when a single document multipage layout is used. JQM allows for div blocks to be treated as pages or scenes within a single document [(Details Here)|http://jquerymobile.com/demos/1.0/docs/pages/page-anatomy.html]. When a page transition is triggered either through a link or programmatically using the $.changePage method the ProxyXHR shim will throw a File Not Found error.
>From looking at the underlying C# code this occurs because the ProxyXHR is attempting to open the link as a text file and return the raw HTML as the response. JQM however passes in the URL as x-wmapp1:/the/path/to/the/index.html#myPageRequest which is not a valid file path as far as the isolated storage is concerned. Even if a shim is created looking for the x-wmapp1:/ that redirects to apps/www/index.html#myPageRequest the #myPageRequest still corrupts the file path to isolated storage.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-106) Navigation in JQuery Mobile that use
Single Document MultiPage Layouts
Posted by "Jesse MacFadyen (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse MacFadyen resolved CB-106.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.4.0
84a6fed4e64216f8b7c8bb801d08aa0041843a9d
> Navigation in JQuery Mobile that use Single Document MultiPage Layouts
> ------------------------------------------------------------------------
>
> Key: CB-106
> URL: https://issues.apache.org/jira/browse/CB-106
> Project: Apache Callback
> Issue Type: Bug
> Components: WP7
> Affects Versions: 1.2.0
> Environment: Windows Phone 7.1 SDK & Emulator, PhoneGap 1.2.0 (pulled from GitHub on 12/02/2011), JQuery Mobile 1.0
> Reporter: Greg Hrebek
> Assignee: Jesse MacFadyen
> Priority: Critical
> Labels: JQueryMobile, WP7,
> Fix For: 1.4.0
>
>
> The navigation and page loading of PhoneGap apps that use JQuery Mobile (JQM) for its UI will not work when a single document multipage layout is used. JQM allows for div blocks to be treated as pages or scenes within a single document [(Details Here)|http://jquerymobile.com/demos/1.0/docs/pages/page-anatomy.html]. When a page transition is triggered either through a link or programmatically using the $.changePage method the ProxyXHR shim will throw a File Not Found error.
> From looking at the underlying C# code this occurs because the ProxyXHR is attempting to open the link as a text file and return the raw HTML as the response. JQM however passes in the URL as x-wmapp1:/the/path/to/the/index.html#myPageRequest which is not a valid file path as far as the isolated storage is concerned. Even if a shim is created looking for the x-wmapp1:/ that redirects to apps/www/index.html#myPageRequest the #myPageRequest still corrupts the file path to isolated storage.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CB-106) Navigation in JQuery Mobile that use
Single Document MultiPage Layouts
Posted by "Jesse MacFadyen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse MacFadyen closed CB-106.
------------------------------
> Navigation in JQuery Mobile that use Single Document MultiPage Layouts
> ------------------------------------------------------------------------
>
> Key: CB-106
> URL: https://issues.apache.org/jira/browse/CB-106
> Project: Apache Cordova
> Issue Type: Bug
> Components: WP7
> Affects Versions: 1.2.0
> Environment: Windows Phone 7.1 SDK & Emulator, PhoneGap 1.2.0 (pulled from GitHub on 12/02/2011), JQuery Mobile 1.0
> Reporter: Greg Hrebek
> Assignee: Jesse MacFadyen
> Priority: Critical
> Labels: JQueryMobile, WP7,
> Fix For: 1.4.0
>
>
> The navigation and page loading of PhoneGap apps that use JQuery Mobile (JQM) for its UI will not work when a single document multipage layout is used. JQM allows for div blocks to be treated as pages or scenes within a single document [(Details Here)|http://jquerymobile.com/demos/1.0/docs/pages/page-anatomy.html]. When a page transition is triggered either through a link or programmatically using the $.changePage method the ProxyXHR shim will throw a File Not Found error.
> From looking at the underlying C# code this occurs because the ProxyXHR is attempting to open the link as a text file and return the raw HTML as the response. JQM however passes in the URL as x-wmapp1:/the/path/to/the/index.html#myPageRequest which is not a valid file path as far as the isolated storage is concerned. Even if a shim is created looking for the x-wmapp1:/ that redirects to apps/www/index.html#myPageRequest the #myPageRequest still corrupts the file path to isolated storage.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira