#911 Back-button loses selections

1.4
closed-wont-fix
nobody
None
5
2014-01-21
2013-12-03
Erik Huelsmann
No

Using back button in a report loses many filter settings (especially dojo widgets)

(From a list of issues sent to the development list by John Locke)

Discussion

  • Chris Travers
    Chris Travers
    2014-01-17

    Will have to talk with John about how to address this.

     
  • i think that most browsers can only cache data as received from server.
    Not locally javascript-rewritten widgets.
    I think handling back-button in browser is only possible in 1-page application.

     
  • Chris Travers
    Chris Travers
    2014-01-21

    • status: open --> pending-later
     
  • Chris Travers
    Chris Travers
    2014-01-21

    we may then have to decide between using Dojo widgets and fixing this. :-P

     
    • could we try strive to a one-page application in 1.5?
      then problem with back-button could be solved by new browser history-api calls.

      2014/1/21 Chris Travers einhverfr@users.sf.net:

      we may then have to decide between using Dojo widgets and fixing this. :-P


      [bugs:#911] Back-button loses selections

      Status: pending-later
      Created: Tue Dec 03, 2013 09:12 PM UTC by Erik Huelsmann
      Last Updated: Fri Jan 17, 2014 09:29 AM UTC
      Owner: nobody

      Using back button in a report loses many filter settings (especially dojo
      widgets)

      (From a list of issues sent to the development list by John Locke)


      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/ledger-smb/bugs/911/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       
  • Chris Travers
    Chris Travers
    2014-01-21

    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,3 +1,3 @@
    -Using back button in a report loses many filter settings (especially dojo widgets)
    + Using back button in a report loses many filter settings (especially dojo widgets)
    
     (From a list of issues sent to the development list by John Locke)
    
    • status: pending-later --> closed-wont-fix
     
  • Chris Travers
    Chris Travers
    2014-01-21

    I think this actually loses all settings.

    Also note that now we are not caching anything which means every time we hit the back button it does a round trip, repeating the request. This is usually safe because of xsrf handling, separation of duties, etc. but it isn't clear to me that content of widgets will be retained. It does mean however that clicking back in an ar/ap transaction screen has the exact intended effect.

    I am going to mark this as wontfix for now. We can always implement a solution later.