Back button is broken


  • Winner of the 2016 Presidential Election

    I have Unread set as my default page. From there I click on a topic, then click back when I'm done to get pack to the unread page.

    The URL changes to /unread, but the screen just goes back to where I entered the topic. This has only started happening this morning.

    Win7, Firefox 46.0b10


  • Winner of the 2016 Presidential Election

    @Jaloopa No repro on Opera 36.0/Chrome 49.0



  • No repro.
    W7 Chrome ... wait let me check that version ... noooo chrome ... this isn't a good time to update ... well I guess it worked on 49



  • @Luhmann
    Still works on Chrome 50 :grin:



  • No repro. OSX. Chrome 50.



  • No repro:

    Enter topic.
    Scroll down with scroll button.
    Click back

    Repro:

    Enter topic.
    Click the scroll to bottom double chevron.
    Click back.

    W7 FF 43.0.1



  • @Boner No repro for that either.


  • Winner of the 2016 Presidential Election

    Looks like a FF specific issue then? @aliceif and other Firefox users, can you confirm?



  • I've experienced this for a day (or possibly two) now. OSX/Conkeror (Derivative of Firefox some version or other), as well as IOS/Safari.



  • @Jaloopa
    Seems to be a FF issue. I didn't get the blank page but I couldn't go back to the topic list with FF.

    FF 45 on W7



  • @Luhmann Yeah repro on OSX Firefox too.

    It's after it updates the URL while scrolling.


  • Winner of the 2016 Presidential Election

    Ah, yes, the risks of using the history API, it's a bit... weird how it works, on any browser. Guess that FF changed the way it handles it. The problem is, with the way it's defined and the way that browsers chose to implement it, I'm not even sure if FF is doing it wrong or right at this point.



  • I was seeing this yesterday, too.



  • @Onyx said in Back button is broken:

    I'm not even sure if FF is doing it wrong or right at this point.

    Firefox is doing it wrong.


  • Winner of the 2016 Presidential Election

    It only seems to happen if there's nothing else to go back to before /unread. If I click on categories, then unread, going back works fine. If I middle click unread, that tab is fucked.



  • @Jaloopa It's been broken for ages.

    Start typing a post, hit Back, then hit Forward-- your post is gone. And 90% of the time you're staring at a blank page which is just a header and footer and nothing inbetween.



  • @blakeyrat Nah, this is something different to that (which does, as far as I'm able to tell, manage to save your post, but hides it away1 in some discodiscoverable "draft" status that comes back when you hit "reply" again.)

    What we're talking about here is (for example) navigating to this thread, hitting the "back" button, and seeing the displayed URL change but nothing else. Seems to be pretty easily triggerable by hitting the back button and scrolling the page at the same time. It's the usual AJAX shite of having to rewrite browser functionality in Javascript because your "web app" breaks it.

    The sort of thing "modern" web "developers" don't even consider a bug. Because they are clueless fuckknuckles who don't understand, let alone create, usability - they wouldn't recognise it, even if it was shoved up their fucking arseholes with great prejudice. The kind of minor but immensely annoying shite we are now destined to live with, because our forum is all buzzcunt compliant. Fuck that shit with a barbed-wire-wrapped pole.

    1 - Although I now find, on testing that I'm right saying that, that I'm wrong, and hitting the "back" button takes the displayed URL to the index page, but leaves the rest of the page contents, thread and reply box up as before. Then the "forward" button does nothing discernible apart from changing the URL in the title bar.


  • sockdevs

    @tufty said in Back button is broken:

    It's the usual AJAX shite of having to rewrite browser functionality in Javascript because your "web app" breaks it.

    Yep, and it's a right PITA to get it working right; I know from experience



  • @RaceProUK said in Back button is broken:

    @tufty said in Back button is broken:

    It's the usual AJAX shite of having to rewrite browser functionality in Javascript because your "web app" breaks it.

    Yep, and it's a right PITA to get it working right; I know from experience

    Is it fuck. Just don't break it in the first place.


  • sockdevs

    @tufty Normally I wouldn't. But when one of the directors of the company says it should be an SPA, you don't have a lot of wiggle room…



  • @tufty said in Back button is broken:

    (which does, as far as I'm able to tell, manage to save your post, but hides it away1 in some discodiscoverable "draft" status that comes back when you hit "reply" again.)

    That's what Ben L told me, but I couldn't get it to work at all.



  • @RaceProUK said in Back button is broken:

    But when one of the directors of the company says it should be an SPA, you don't have a lot of wiggle room…

    people ignore direct orders from the CEO all the time. the guy would come around when I am distracted and tell me to do things the X way. I talk to manager next day and he dismiss that and tell to do it Y way.

    One month later manager comes here and tell we're gonna do X.

    Fucking manager from hell.



  • Repo both on ios/safari and mac/chrome



  • @blakeyrat I think it more than likely the behaviour you're seeing is browser-specific. And potentially somewhat non-deterministic based on the whims of the network gods.

    This time I managed to get the page content to change using the 'back' and forwards' buttons with an edit box up, but as long as I stayed on site, the edit box stayed up.

    'back'ing off the site and then forwarding got me to a state where the edit box had gone away. No indication that I had ever tried replying, but hitting a 'reply' button on a post brought my post back (but didn't add an @summon, although it probably should have). Hitting a 'quote' button also brings back the edit box, but similarly, doesn't actually quote the post you just clicked on. It does make the post "in reply to" that post, though.

    That's one of the behaviours I'm seeing on Chromium / Chrome on the Mac. I find it altogether believable that it might happen differently on other browsers or platforms.

    Did I mention how much I like the "modern" web?


  • Impossible Mission Players - A

    Repro.
    0_1460755130896_upload-7d4072a9-8512-446f-af49-c2f32628d8bc

    Though, truly, if I ever encounter a site that considers itself a "Web App", I pretty much ignore all web browser features such as Back and Forward, URL/bookmarking, etc.

    If I wanted to go back to the topic list, even if I pressed the Back button, the Unread list would get refreshed (losing my theoretical place) anyways, making the end result the same as if I click the "Unread" button (or whatever) like it expects me too.

    Still broken, but I'm a good little doggy that's obedient to the insanity that defines my interactions...



  • @loopback0 said in Back button is broken:

    No repro. OSX. Chrome 50.

    No repro again. Windows 10. Chrome 50.



  • @loopback0 said in Back button is broken:

    No repro again.

    Repro, Windows 10, Chrome 50. Had to test with /recent, not /unread (since I caught up/marked a bunch as read) but I got the same result as others got on /unread.

    1. Right-click on Recent, open in new tab.
    2. Choose a topic that has at least a few posts.
    3. Scroll some, to trigger the URL/history changing (doesn't even need to try and load in more posts).
    4. Hit the Back Button.


  • @ChaosTheEternal said in Back button is broken:

    Right-click on Recent, open in new tab.
    Choose a topic that has at least a few posts.
    Scroll some, to trigger the URL/history changing (doesn't even need to try and load in more posts).
    Hit the Back Button.

    This repro'd once, then worked fine (starting with a new tab each time).



  • @loopback0
    It happens to me every time I try it, every browser I try it in (Chrome 50, IE11, Edge 25, Firefox whatever, all on Windows 10, and even Chrome 49 on Android 4.4).

    I've yet to have it not repro when I follow the steps I laid out. The key things are starting in a new tab (with /unread or /recent as the new tab page) and making sure the URL changes before hitting Back.


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.