(I also cross-posted this to the script’s GitHub page)

$(”#contact-form label.inField”).inFieldLabels();

Wait, scratch that–each label/input duo needs a relatively positioned container, so that container would get the class, and it wouldn’t affect other inputs/labels not using infield. But I still think applying the class to the labels themselves is cleaner and more future-proof for possible changes to the script.

Great work though, I really like this plugin.

I’m using this for a very complex form (mainly as input hints), and I need to have other labels & controls appear or disappear based on various conditions.

I’m also using a few other plugins, so the conditional coding is getting pretty gnarly :P

Great plugin – just need this flexibility.

Thanks

I propose that you add some of the new HTML5 input types (”email”, “url”, “tel” & “time”) to the two types your already targetting (”text” & “password”).

Thank’s

E.g.-
$(”#somefield”).keyup(function() {
if (!jQuery(this).val()) {
jQuery(this).change();
}
}

Leave the css to the css files… In the , just check for “if (document.getElementById) … ” and document.write your “js.css”. If/when JS fails to load and/or is turned off, the CSS specific to your plugin (and other JS code/plugins) won’t apply itself.

IMHO, I think it is important to separate as much presentation from the JS logic if/when at all possible.