This seems to be a standardised way to tell the type of a javascript object. Why?
A little tweak with Chrome Console
This strange behaviour with console is worth paying attention to: it updates the object when you expand it. Say we have:
jQuery: Difference between bind, live and on
Equivalent:
$('button').bind('click', fn);
$('button').on('click', fn);
Equivalent:
$('button').live('click', fn);
$(document.body).on('click', 'button', fn);
Facebook: Share, Like, Comment
This is how to utilise the Facebook JavaScript SDK to add Share, Like and Comment for your site:
MAMP: 403 Forbidden – You don’t have permission to access x on this server
If you see this:
The order of the events triggered will be in the order they’re added. So when the order of two events makes a difference, and they’re in separate files, pay extra attention to which one gets load first. Especially when the page loads extra slow.
Order of On Events
Compatible Audio Playing Across All Platforms
It seems like:
- With HTML5 audio tag, if the audio is less than 500ms, the volume in Safari might fluctuate with all formats
- With HTML5 audio tag, the delay with Safari is obvious with all formats
- With flash audio player, the delay with Safari is obvious with
*.wav, but it’s fine with*.mp3 - IE9 doesn’t support native audio tag
- Firefox’s audio sounds terrible when html5 audio tag is used with
mp3/oggformat, but is okay withwav. - Firefox is fine with flash audio player
jQuery: keyup, keydown, keypress?
In normal cases, go for keyup:
$(document).keyup(function(e){
console.log(e.which);
});Reasons:
keydownkeeps firing when user holds the keys down, whilekeypressandkeyupfire only once.keypressdoesn’t detect special keys (e.g.SHIFT),keydownandkeyupdo.