6 ms·
Bootstrapped https://artcall.org https://artcall.org and trying to gain traction on https://ezzl.art https://ezzl.art while employed full time elsewhere.
by wilsmex 8y ago
Bootstrapped https://artcall.org https://artcall.org and trying to gain traction on https://ezzl.art https://ezzl.art while employed full time elsewhere.
- notJim 8y agoFYI, I cannot scroll down on on artcall.org.
- wilsmex 8y agoOh strange, can’t reproduce. Are you on mobile or desktop? Browser?
- thenewcoder21 8y agoI could reproduce on OS X, Desktop, using Google Chrome. Hope that helps!
- dolessdrugs 8y agoWindows, Desktop, Firefox : no issues Windows, Desktop, Chrome: Clicking the scroll bar works; mouse wheel, arrows, page up/page down do not.
- rodolphoarruda 8y agoI could reproduce it on Ubuntu with Chromium.
- neetdavid 8y agoSame for me on Chrome. There's a 'mousewheel' event listener attached to the window that is calling preventDefault()
- Sohcahtoa82 8y agoThis absolutely infuriates me to the point where I'm struggling to remain civil. My blood instantly began boiling after reading that sentence. Why the @#$% does some web designer think it's a good idea to disable mousewheel scrolling?! What does this accomplish? What feature do you gain? What was the goal? I just can't for the life of me grok what would be going through someone's brain when they decide "Hey, you know what would make this page better? Disabling scrolling with your mouse wheel!" EDIT: Maybe the intent was to do something else, like implementing smooth scrolling in JavaScript, and it's not working properly. But if that's the case, the answer is that web devs need to stop trying to mess with scrolling. Implementations rarely work correctly in every browser and it just ruins the UX. Just stop messing with scrolling!
- wilsmex 8y agoIn this case it's a bug, as I'm not trying to 'disable' the mouse, but track scrolling and then make the menu 'stick' to the header when the user scrolls down the page. A common design pattern which increases usability quite a bit.
- Sohcahtoa82 8y agoIsn't that usually done with CSS?
- is_true 8y agoHaha. Step down a notch, pal
- hluska 8y agoWhat do you possibly gain from this kind of rage? It's rude and makes for an extremely low quality comment.
- Sohcahtoa82 8y agoIt hits a nerve when a programmer or designer either tries to fix something that isn't broken and ends up making it even worse (Such as web pages that try to implement smooth scrolling), or removes functionality for the sake of simplicity and it lowers usability. Yeah, in this case it was a bug, but let's not pretend it doesn't happen deliberately sometimes.
- deleted 8y ago[deleted]
- wilsmex 8y agoThanks all! Looks like it's Chrome (was able to reproduce there). Will fix when I'm not at work. ;)
- deleted 8y ago[deleted]