[Sohcahtoa82]

This 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]

In 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]

Isn't that usually done with CSS?

[hluska]

What do you possibly gain from this kind of rage? It's rude and makes for an extremely low quality comment.

[Sohcahtoa82]

It 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.

[hluska]

Whether it hits a nerve or not, there are more productive ways to express that you don't agree with an implementation. You acted like a bully and that's completely unacceptable.

[is_true]

Haha. Step down a notch, pal