You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Colin Eberhardt (Created) (JIRA)" <ji...@apache.org> on 2012/01/19 11:24:39 UTC
[jira] [Created] (CB-185) WP7 handling of URL fragments
WP7 handling of URL fragments
-----------------------------
Key: CB-185
URL: https://issues.apache.org/jira/browse/CB-185
Project: Apache Callback
Issue Type: Bug
Components: WP7
Reporter: Colin Eberhardt
Assignee: Jesse MacFadyen
Priority: Minor
Currently there is code in PGView.xaml.cs that halts navigation if the URL contains a fragment:
if (e.Uri.ToString().IndexOf("#") > -1)
{
e.Cancel = true;
}
I understand that PhoneGap couldn't easily support navigating the given page, then scrolling to the fragment location. However cancelling navigation is a bit extreme!
I would suggest removing the fragment from the URL then simply navigating to the given page.
--
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-185) WP7 handling of URL fragments
Posted by "Jesse MacFadyen (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse MacFadyen resolved CB-185.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.4.0
It was not actually doing anything ...
commit: 7884c86bf4ddc7f3390d58a8ab6929966d45d9c2
> WP7 handling of URL fragments
> -----------------------------
>
> Key: CB-185
> URL: https://issues.apache.org/jira/browse/CB-185
> Project: Apache Callback
> Issue Type: Bug
> Components: WP7
> Reporter: Colin Eberhardt
> Assignee: Jesse MacFadyen
> Priority: Minor
> Fix For: 1.4.0
>
>
> Currently there is code in PGView.xaml.cs that halts navigation if the URL contains a fragment:
> if (e.Uri.ToString().IndexOf("#") > -1)
> {
> e.Cancel = true;
> }
> I understand that PhoneGap couldn't easily support navigating the given page, then scrolling to the fragment location. However cancelling navigation is a bit extreme!
> I would suggest removing the fragment from the URL then simply navigating to the given page.
--
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