We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Definitely a need for a back button (and maybe forward to get back to where you were when you went back :) )
The text was updated successfully, but these errors were encountered:
Do the forward/back actions need to be logged as well?
Sorry, something went wrong.
Nope, they have no impact on the actual call, just there for hte user to navigate easier
So let me ask you this, if you click on the back button several times, and then choose a response that differed from the original, what happens?
Not trying to be a PITA, but I just need to know how the app should behave =)
for now - lets just say the buttons are grayed? for hte future it would be nice to just take the different path.
On Tue, Mar 26, 2013 at 10:33 AM, Jason Nichols notifications@gh.neting.ccwrote:
So let me ask you this, if you click on the back button several times, and then choose a response that differed from the original, what happens? Not trying to be a PITA, but I just need to know how the app should behave =) — Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-15461572 .
— Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-15461572 .
No branches or pull requests
Definitely a need for a back button (and maybe forward to get back to where you were when you went back :) )
The text was updated successfully, but these errors were encountered: