Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JQM dialog integration #4

Open
gcutrini opened this issue Aug 26, 2012 · 1 comment
Open

JQM dialog integration #4

gcutrini opened this issue Aug 26, 2012 · 1 comment

Comments

@gcutrini
Copy link

If you open a dialog from the index and then close it with jquerymobile close button (not the one on the template instantly navigates), the dialog gets first dismissed and afterwards the navigation is made from index to index.
The jqm page gets removed from dom, then recreated, and then $.mobile.changePage fails because its trying to make a transition from a page that no longer exists to the one recently created.
This has to do with jqm dialog dismiss button.

I have another issue about dialog usage. If included as a route outcome, a dialog page is retained in the navigation history.
A dialog only relates to the page that created it; back a forth navigation should bypass a dialog.
I am not sure what would be the right approach to solve this issue, what do you think?

@raDiesle
Copy link
Owner

Hi,
About 1.
I forgot about to put this to todo.
Can you do it and fix it, please?
See the source links below.
I think one of them solves it.
I'm going to spend some time next weekend.

Good idea!
In my big app I prefer dialog in history, where i m able to restore values
and coming back from login page to proceed the authorized form submit.
Additionally I'm planning to use breadcrumbs.

May you want to add e.g. removing last history, if dialog was opened , if
property flag was not overidden?

Thanks for contributing
Am 26.08.2012 17:38 schrieb "gcutrini" notifications@github.com:

If you open a dialog from the index and then close it with jquerymobile
close button (not the one on the template instantly navigates), the dialog
gets first dismissed and afterwards the navigation is made from index to
index.
The jqm page gets removed from dom, then recreated, and then
$.mobile.changePage fails because its trying to make a transition _from_a page that no longer exists
to the one recently created.
This has to do with jqm dialog dismiss button.

I have another issue about dialog usage. If included as a route outcome, a
dialog page is retained in the navigation history.
A dialog only relates to the page that created it; back a forth navigation
should bypass a dialog.
I am not sure what would be the right approach to solve this issue, what
do you think?


Reply to this email directly or view it on GitHubhttps://github.com//issues/4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants