[aida] Back button behaviour (was Re: Scriptaculous integration)

[cdrick]

Hi Janko ;)


>  Well, let me ask you back, what is a proper back button behavior in this
>  case? From user perspective, not Seaside one! More below.
>
>  > http://www.squeakside.com/seaside/exxx   then hit flow and use the
>  > second link... you can -use/abuse back button, refresh and the result
>  > is consistent.
>
>  This behavior is wrong from the user perspective, because it undo user
>  action, not return him to previous page. And user definitely doesn't
>  expect such undo. Consider order confirmation, than go with back button
>  to previous page. Should order be canceled/undoed? Of course no!

here I don't agree because we're not talking about page. I'm ok with
the 'undo action'.
Moreover this is something configurable whether you track state or not.
Then there is also the possibility to isolate a flow (this one I find
cool). Once order is done, you can't go back. Or even if you copied
the previous url and then you try to load it again this will result in
a redirect to the last stage of the flow (try with sushy shop).


>
>  > In your counter example:
>  > -http://nico.bioskop.fr/counter.html
>  >
>  > back button behavior is equivalent to repeat the action. refresh
>  > also... so this lead to strange behavior. But, again I agree, this big
>  > flashing POST warning should prevent everybody to do that ...

This is working now. No more post message... I had that yesterday and
I think this morning too.

>
>  It could be that you tried a counter when it really didn't worked well.
>  Try it now. Both counter and multicounter should work the same now.

yep, I far prefer this behavior which is consistent.

One could argue there less possibility to manage form entries (as I
told you on irc) but that's ok to me. I can cope with that.

The think is I was surpised of yesterday bahavior.

What did you change ?

>
>  Back button let you leave the counter/multicounter page, forward button
>  let you return to the exactly the same counters. Seems good behavior to
>  me and what user would expect.

It's ok I agree...

>
>  Why is in this case so? Because multi-counter page has the same url all
>  the time so that browser hasn't anything to put into history. Seaside on
>  the other side change url all the time, and that's why they can achieve
>  that counter undo effect. Which is wrong from user perspective, as I
>  already said.
>

This is exactly why continuation were made IMO. Track state... Of
course it simpler and also elegant the way Aida do it...
The point is "this is a difference". I don't want to argue if one is
better... just I don't find wrong the behavior of seaside ;-)

See you and thanks for the answer ;)

Cédrick