Especially when the scrollbar you invent doesn't work in Chrome.
Especially when the scrollbar you invent doesn't work in Chrome.
Yes, it can be worthwhile to borrow successful concepts from other disciplines. But in many cases, the concrete implementation NEEDS to be reinvented in order to apply the abstract concept to a new purpose.
We're better off only for the reinventions that were actually improvements. Most of the reinventions weren't improvements.
Different is a disadvantage, a cost, that is worthwhile only in specific cases when the difference produces some advantages that more than make up the difference.
It's not even the same sport..
Edit to respond to your revised comment that replaced its content with the title of your article (wow, way to be accepting of criticism, dude! When you do usability testing and a user finds a bug or complains about something, do you tell them they're an idiot, too?):
Even if it's a bug in Chrome's rendering engine, you have an IE7 specific stylesheet, assumedly to support the bugs in its CSS rendering engine. And considering IE7 usage is 11.7% while Chrome's is 10.8% [1], you've just alienated a fairly large portion of your potential readers.
[1] http://www.w3schools.com/browsers/browsers_stats.asp (orderedlist's statistics may be different; being a usability-oriented blog, it probably has a higher portion of Chrome users than the general public)
Calling someone an asshole is asshole behavior. Knowingly forcing your users into a broken usability situation is asshole behavior.
I wouldn't think that calling someone out on it would be considered idiot behavior.