The advantage of using the DOM to bind an event is that you can assign multiple functions to a node for the same event (ie: window.onload) without running into event handler conflicts.
Browsing the forums, development articles and other resource sites raised an interesting yet recurring question: 'How do I test for the Document Object Model (DOM) employed by a browser?'" This is a question that begs answering once and for all.
While the goal of the popup blockers is almost achieved nowadays, to keep out the intrusive popups, the only alternative for fair webmasters is the usage of DHTML popups. These are not regular windows controlled by your GUI operating system component; in fact it is pure HTML controlled by the browser via JavaScript. They would also qualify as a part of the so-called AJAX technology, therefore are also named Ajax popups too.
The initial solution adopted by most developers is dynamically hide a form controls by having them lose display when the CSS menu drops. Though doing this may seem to be strange and blinky it is better than not trying to fix the problem. But site vistors might be bothered a bit by things dancing around on the webpage. It is distracting and may be a cause for dozens of emails to the webmaster.
As you can tell by the title, I intend this to be a multi-part series on using moo.fx to create better forms. In the first installment we are going to create a form that displays a hint to the user about the type of information that is expected in an input box.
Joining mailing list will entitle you
to receive occasional emails informing you of news and
updates to the site and any special offers that may be
of interest to you.