Hijacking the back button to lock me on the page is an unacceptable violation of my browser functionality. Don't do that. It's bad. When I click the back button, I want to go away from where I am, back to where I was before. I don't click the back button to remain in the same place.
I wanted to watch the demo video again; even if it's only on the initial signup page, the hijack is irritating. If it's intentional, that's offensive.
Looks interesting to me - I am using the mouse button on the left side of the mouse which is bound to back by default. That just flickers the login page. Actually clicking the back button on the browser UI works, though (Edge Win10/64).
Video didn't play on Firefox. I had to hit the "pop-out" icon to show it separately, at which point it showed the regular video controls (which should have shown in the first place, right?). If I didn't read the comments here, I wouldn't have realized this was a video.
An audio track narrating what's happening would be nice, although it's pretty clear from the video what's happening, which is great!
One question: how do you display functions that are more than a dozen lines long? Do they get shown in a scrollable window, or does the window get auto-sized to show the entire function (which, IMHO, would be bad if the function was huge)?
They are scrollable. We try to be smart with how we capture scroll/touchpad interactions for zoom/scroll so that they feel natural. Thanks for the feedback!
The back button seems to work fine for me, at least in Chrome. Could you provide more specific repro steps? Are you sure it's not just the OAuth redirect dance?
Having worked as a frontend web developer, I can assure you that the back-button hijacking is sheer incompetence of the developers. They have to be mutating your browser history in a careless way to achieve this. That or they somehow picked a really bad client-side routing library. (Even just following a basic tutorial for react-router wont cause this behavior. It's almost always sloppy state management causing this)
Well in this case it's the frontpage. That makes little sense. If it's further inside the application, it can become very difficult, but this is just when you click start now and you are stuck. That makes no sense.
I wanted to watch the demo video again; even if it's only on the initial signup page, the hijack is irritating. If it's intentional, that's offensive.