It crashes Explorer 5 Mac when you use the script too much (a few changes is OK).
Opera sends all form fields to the server, also those in the waiting room.
I have heard, but not tested, that Safari 1.1.1 does the same.
In quirks mode Opera cannot handle nested select boxes, though in strict mode it can.
Explorer 6 Windows hides this floating div as soon as you add or remove form fields.
The script does not work on <label>
tags in all browsers. This is dependent
on whether the click event of a form
field fires when the user clicks on the label. I need to write a workaround for this,
but don't have the time right now.
On this page I give the download link and some extra information on the Usable Forms script. This script is meant to show and hide form fields based on user actions. I explain this script in great detail in my Digital Web Magazine article Forms, usability and the W3C DOM.
Download the script. Current version: 1.0 . For further instructions see my article.
Safari update: The 1.0 release supports this script also in Strict mode.
This is the only script on my site that contains a copyright notice, because it's more special and ground-breaking than any of my scripts. You may do whatever you like with it, as long as this copyright notice remains intact. If you extend the script, please also extend the notice to explain what you've done.
The script adds and removes form fields based on user actions. Try the form below.
The script works as follows:
relation
attribute.id
value as the relation
value of the removed TR. This marker
is for returning the TR's to their correct places in the form later on.show
attribute, the appropriate TR's are shown.onclick
event handler to the entire document.Now the script waits for user input.
show
attribute. If it isn't, nothing happens.show
attribute, the script looks for TR's having the same
value for their relation
attribute. It gathers them and puts them back in the form, using the marker to determine the exact spot.'none'
for the show
attribute, it doesn't show any new TR's. It does
hide the TR's related to the other form fields in the group, though.A few WDF-DOM members gave some good feedback. There were two points of critique: