Unless you manage to implement undo/redo as back/forward which is very cool IMO.
On Fri, Jun 6, 2014 at 1:28 PM, Jens <[email protected]> wrote: > If you update the URL for every click or string the user enters the >> browser history is going to be flooded with a lot of items. This basically >> makes the browser back/forward useless. I certainly hate websites who do >> this. I try to limit history changes only when the user does actions that >> take you to a different place in the application. >> > > +1! Thats also a *very good reason* to not store every UI change. It > defeats the browsers back button. > > -- J. > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- Vassilis Virvilis -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
