Comment 2 for bug 668528

I've duped sladen's new bug to this one. Adding in sladen's comments here.

Sometimes a timetable screen gets "stuck" and doesn't update. When this happens it is not possible to know that the display has not been automatically updated.

One possible solution would be to add a pure-Javascript timer that states somewhere visible:

  "Last refresh XX minutes ago"

and have this updated by the page. Should the page fail to update it would be obvious to the viewer that the display might be several tens or hundreds of minutes out-of-date.

I think this is a more practical fix. I'll scape my current fix.