Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
I'm not sure if this is a bug or a limitation, but it's potentially confusing.
When you request a page (page #1) the block correctly starts counting down (I'm using JStimer with Auto Logout). If you go to another page (page #2), it'll restart; again, that's fine. But if you then use the "back" button to return to page #1, it'll restart again.
This isn't correct, is it? I'm guessing that the page is reloaded from the browser cache rather than from the Drupal server, so the system will still be counting as of page #2.
Feel free to tell me if I'm completely wrong here...
Comment | File | Size | Author |
---|---|---|---|
#6 | autologout-back_button_support-809928-7486042.patch | 3.95 KB | johnennew |
#2 | autologout-back_button_support-809928.patch | 1.84 KB | johnennew |
Comments
Comment #1
johnennew CreditAttribution: johnennew commentedYou're not wrong (even after 3 years)!
I have confirmed the behaviour in head. It affects all the JS timers including the one that challenges you to remain logged in on the 4.x branches. So, pressing back you get logged out before the timer and popups tell you you are logged out.
Fix here looks like:
http://stackoverflow.com/questions/829046/how-do-i-detect-if-a-user-has-...
Moving to head, note this won't be back ported to 2.x - only 4.x is supported.
Comment #2
johnennew CreditAttribution: johnennew commentedPatch for the 7.x-4.x branch attached.
Comment #4
johnennew CreditAttribution: johnennew commented#2: autologout-back_button_support-809928.patch queued for re-testing.
Comment #5
johnennew CreditAttribution: johnennew commentedCommitted to 7.x-4.x branch, setting 6.x-4.x for backport.
Comment #6
johnennew CreditAttribution: johnennew commentedPatch for 6.x-4.x branch
Comment #7
johnennew CreditAttribution: johnennew commentedTests pass - committing to 6.x-4.x