Wondering why that link doesn't work.
My junior developer uses onlick instead of onclick.

Bright future is ahead of him.

@xaero I'll ask him to test it.

@DanijelH Yes, very bright

"The Future's So Bright, I Gotta Wear Shades"

.

I'm happy that I don't need to deal with this kind of bullshit using a compiled language.

I wasn't aware that input method was an option.

Using inline events on HTML is not a good practice. You should add:

DOM.addEventListener("click", function(){
//whatever
});

@LuxARTS I know about this but I never understood why. If I ever look back at the code and use inline event trigger I get a report for a broken feature, see exactly when what triggers why and have a much easier time debugging than looking through the computed listeners. The only sensible argument I come to is that they hide the internal workings but I never understood why someone would want that.

Because the "code" is not the HTML file, is the JavaScript file. If you want to get info about the event simply set a variable to send to the trigger function and read it.

DOM.addEventListener("click", function(event){
console.log(event);
});

Typos happen wtf

😛

`onlick`? Smart Ice cream in the future?