6 ms·
Really neat little project! I would have loved to paid more attention but easily the most unusable website I've used in a while. Like seriously, it's awful if
by rubyn00bie 6y ago
Really neat little project!
I would have loved to paid more attention but easily the most unusable website I've used in a while. Like seriously, it's awful if you scroll up an down a couple times because you're pushing URL changes. Then because everything animates it starts chugging a long, doing weird shit, like not going back. It's a single page it doesn't need to change the fucking URL or even worse animate those changes...
On the plus side, the website looks really nice even if it is unusable.
- chris_st 6y agoWell, maybe on other browsers... on Safari, on a wide screen, I still had to maximize the window to see all the text. At a "mere" 1200px wide, half the text was under the knob.
- Hamuko 6y agoSame on Firefox at 1530 px.
- tsomctl 6y agoNot sure what pisses me off more. That, or the music autoplaying.
- jbverschoor 6y agoOr breaking the back button
- Gibbon1 6y agoBe nice if there was a DNS that blackholes websites that break the back button.
- jbverschoor 6y agoOH yeah! A DNS that would crawl the website, launch a VM with a couple browsers to see if the backbutton is broken.
- pedroma 6y agoPeople just need to know when to use replaceState instead of pushState. https://developer.mozilla.org/en-US/docs/Web/API/History/replaceState https://developer.mozilla.org/en-US/docs/Web/API/History/rep...
- splintercell 6y agopushState maybe sometimes used but replaceState should never be used. Seriously, many times I was on a website where scrawling introduce you to new article but it also replace the URL oh, now I wanted to go back to the original article because I wanted to share with you but I couldn't. at least with a push State I could retrace my steps and not rely on the developer guessing where I might have been going.
- kaushikt 6y agobreaking the back button is an absolute sin. What could be the possible use case for anyone to break the back button this way?
- teemofeev 6y agoSorry guys, I didn't expect so much interest from the audience. I've updated the website, hope it's better now :)
- quickthrower2 6y agoThank god for iOS safari. Quiet as a mouse.
- teemofeev 6y agoHey tsomctl, sorry for the inconvenience. We've updated the website. Removed the autoplay. I hope it works better now.
- hackmiester 6y agoyeah, I also cannot scroll it with my finger. I had to connect a mouse to my touch screen computer just to scroll the page.
- teemofeev 6y agoHey, We didn't expect such huge feedback, and the website was made just for fun without any testing. We know that the webpage is clunky. Moreover, we're hosting it on a limited free Firebase tier. Sorry for the inconvenience.
- CSSer 6y agoI’m sorry the parent comment was so aggressive but I think their sentiment does have merit. This is particularly true on mobile where trying to use the back buttons once I finished reading became particularly confusing because mobile browsers hide parts of the URL. If it’s any consolation, you are not the first nor will you be the last person who has ever done this. Directly mutating history has costs that are not always readily apparent. The advice not to do so is not an old wive’s tale.
- teemofeev 6y agoThank you. We've updated the website. It's a simple landing page now, and I hope it works better now.
- lokedhs 6y agoWhat about the fact that half the text not only graphic, but also covered by the graphic, so it's impossible to read. It's a pity the project itself is so neat. Makes me feel bad about referring to it as such a remarkably horrible web experience.