Bug #3470

[Workbench] Ajax updated pages don't interact correctly with browser history.

Added by Peter Amstutz almost 3 years ago. Updated 3 months ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Workbench
Target version:-
Story points1.0
Velocity based estimate-

History

#1 Updated by Peter Amstutz almost 3 years ago

  • Subject changed from Ajax updated pages don't interact correctly with browser history. to [Workbench] Ajax updated pages don't interact correctly with browser history.
  • Category set to Workbench

I get the following behavior on Firefox/Iceweasel 30.0

  1. Run a pipeline to completion. The page auto-refreshes until it is successful.
  2. Click on a link to go to another page, such as visiting an output collection.
  3. Click the back button
  4. You'll be back at the pipeline page, but it will show the state of the pipeline as not started instead of finished. This is because the browser cache is displaying the version of page that was initially downloaded, not the page presented to the user with subsequent ajax updates.

#2 Updated by Ward Vandewege almost 3 years ago

  • Target version set to Arvados Future Sprints

#3 Updated by Tom Clegg almost 3 years ago

  • Story points set to 0.5

#4 Updated by Tom Clegg almost 3 years ago

  • Story points changed from 0.5 to 1.0

#5 Updated by Tom Clegg 3 months ago

  • Status changed from New to Closed

#6 Updated by Tom Clegg 3 months ago

  • Target version deleted (Arvados Future Sprints)

Also available in: Atom PDF