Skip to content
This repository has been archived by the owner on Oct 8, 2021. It is now read-only.

Feature Request: Transition override by Web Server #1590

Closed
tenor opened this issue May 9, 2011 · 6 comments
Closed

Feature Request: Transition override by Web Server #1590

tenor opened this issue May 9, 2011 · 6 comments

Comments

@tenor
Copy link

tenor commented May 9, 2011

Currently when navigating from one page to another, you can specify the kind of transition you want on the markup as documented at http://jquerymobile.com/demos/1.0a4/docs/pages/docs-transitions.html

I think it would be useful if the web server/app can override the transition settings.

Let me describe a a typical scenario: User fills out and submits a form. If everything goes well, he is directed to the desired page, if he filled out the form incorrectly, he is presented the form again with the invalid fields highlighted.

If everything goes well and there is a transition to the desired page, then there is no problem but it would be a bit irritating if there is a transition to the error page which is exactly the same page he was on previously (albeit with invalid fields highlighted).

I propose a new X-JQM-Transition HTTP header which JQM would look out for and not perform transitions if set by the web server in the response.

This feature should also work properly in the case of redirected pages.

Thanks.

@jblas
Copy link
Contributor

jblas commented May 9, 2011

FYI, there is already a transition called "none". It basically pops the new page into place with no animations.

@toddparker
Copy link
Contributor

Could you add this as a feature request on this wiki page and close when done?
https://github.com/jquery/jquery-mobile/wiki/Feature-Requests

@tenor
Copy link
Author

tenor commented May 9, 2011

@jblas -- Thanks, I've updated the issue.
@toddparker -- I've edited the wiki.

@tenor tenor closed this as completed May 9, 2011
@toddparker
Copy link
Contributor

Super, thanks!

@scottjehl
Copy link

Once we expose events/callbacks for handling page response data (currently in progress), you'll be able to do this on your own. I'm guessing you could used http status codes instead of inventing a new header, but either way should be easy enough for you to do.

@tenor
Copy link
Author

tenor commented May 9, 2011

That's good to know. Thanks!

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

No branches or pull requests

4 participants