also see retain GET query when signing in
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.
I would say AJAX is a secondary concern. First is getting the representation and the simple cases right.
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.
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
is there a PR for this?