[
https://issues.apache.org/jira/browse/CB-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196611#comment-13196611
]
Jesse MacFadyen commented on CB-206:
------------------------------------
This is all possible on WP7, but I am reluctant to implement them as I do not
understand the need for them.
I think the first step should be justification of their existence in the first
place.
What are the implications of this API + jQM or other JS frameworks that already
provide history management?
The current implementation on WP7 allows you to add an event listener ( via
document ) for the back button event, at which time you can simple call
javascript: history.go(-1);
The history stack is managed in the DOM already, and this only seems to make
sense to me when more than one browser is present ( via activities/views where
they cannot share history ), am I missing something?
The addition of 'exitApp' does make sense to me in cases where the history
stack is empty, as this is the default behaviour for WP7 and expected by the
user.
> No documentation for navigator.app methods
> ------------------------------------------
>
> Key: CB-206
> URL: https://issues.apache.org/jira/browse/CB-206
> Project: Apache Callback
> Issue Type: Bug
> Components: Docs
> Affects Versions: 1.3.0
> Reporter: Raymond Camden
> Priority: Minor
>
> There are a few method available in the navigator.app space, for example,
> exitApp, but there are not documented anywhere.
--
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
