return directly to interrupted actions+discussion

also see retain GET query when signing in

--John Abbe.....2013-05-06 03:16:07 +0000

I would say that one is a subset of this one.

AJAX is probably the best solution to this, but maybe it needs several approaches. If the action is reloading the browser page, it probably works a bit better to let the server handle it, since the server knows how/why it got interrupted, but if the action is going to be processed in AJAX ways, it will be hard to get back without AJAX help. I think the tricky part will be that it needs to do the sign-in/signup, etc. within a frame or slot, and I don't think sign-in/signup works that way now.

--Gerry Gleason.....2013-06-08 22:25:36 +0000

I would say AJAX is a secondary concern. First is getting the representation and the simple cases right.

--Ethan McCutchen.....2013-06-10 05:13:02 +0000

in other words, I don't think an ajax-only solution makes sense, but it would be cool if the ajax and non-ajax behaviors were pretty close to the same.

--Ethan McCutchen.....2013-06-10 15:55:17 +0000

I implemented a simple solution: when an action is interrupted by a sign-in I save the uri in the session and return to that uri after the sign-in

--Philipp Kuehl.....2014-10-09 11:42:36 +0000

is there a PR for this?

--Ethan McCutchen.....2014-10-09 17:05:01 +0000

sharks

monkeys

platypuses

everyone

return directly to interrupted actions+discussion