Though I don't normally recommend modifying the browser's default behaviors, changing the window's status bar does have its place. The window status bar can pass descriptive information about the element the user is hovering over or can hide the URL from users that don't understand source code enough to figure it out for themselves.
window.status = 'Hello! You are hovering over me.';
While synchronous code is easier to follow and debug, async is generally better for performance and flexibility. Why "hold up the show" when you can trigger numerous requests at once and then handle them when each is ready? Promises are becoming a big part of the JavaScript world...
Feature detection via JavaScript is a client side best practice and for all the right reasons, but unfortunately that same functionality hasn't been available within CSS. What we end up doing is repeating the same properties multiple times with each browser prefix. Yuck. Another thing we...
There's yet another reason to master more than one JavaScript library: you can use some of them together! Since MooTools is prototype-based and jQuery is not, jQuery and MooTools may be used together on the same page. The XHTML and JavaScript jQuery is namespaced so the...
We all joke about the days of Web yesteryear. You remember them: stupid animated GIFs (flames and "coming soon" images, most notably), lame counters, guestbooks, applets, etc. Another "feature" we thought we had gotten rid of was the marquee. The marquee was a rudimentary, javascript-like...
Thanks, but it wont work in IE7… Just IE6..
Thank you for mentioning this Selim. It looks as though IE7 has disabled this functionality.
Yes, unfortunately custom status messagges are removed from ie7. I have searched it for a month ago :)
thank you, i really appreciate all your tuts