A place for ugly, silly, or just-plain-crap JavaScript.
A dreadful and utterly painful attempt to create an interchangeable operator.
My suggestion, use a strategy pattern.
Read the story here http://stackoverflow.com/a/9989085/1173062
One of the many highlights in oafcoreR121.js:
And who needs CSS classes?
Thank goodness there’s a comment. Without it we might not understand what’s going on. Oh wait…
And awesome browser detection:
I’m not sure what’s worse - The fact that all JavaScript errors are silently ignored, doCallback2 having three callbacks and doCallback3 having two callbacks, or the use of globals (Callback1, Callback2, Callback3). The same site had JavaScript functions with names like “foo” and “bar”.
As a side note, an interesting oddity in JavaScript: When you return true in the window.onerror handler, this prevents the default event handler. This is the opposite to all the other DOM 0 events (such as onclick), where returning false prevents the default handler.
Saw these snippets on the site of a company that provides “industry leading solutions”. Firstly a snippet that was in the <head> of every page, intentionally breaking the back button:
And there was also this function which abuses exceptions for control flow (I’m not too sure why):
Working on a recent project I kept coming across anchor tags like this:
I was really curious as to what visit_url() would do, eventually I found it:
Subscribe or follow @UglyJS!
.........
Fork then send a pull request to contribute.