As long as you don't change form elements, you can use traditional javascript/jquery. So it would be OK to hide/show or disable/enable the CVV field in your example.
If you change them (for example, by adding in a CVV field, or by changing the options in a select) then form validation will fail. That's the case where you're forced into AJAX(D7)/AHAH. If you find you need to do AHAH, there are working examples in the Examples module (http://drupal.org/project/examples), and there is a tutorial at http://randyfay.com/ahah, which also has references to other information. -Randy On Sun, Nov 22, 2009 at 1:37 PM, Jeff Greenberg <[email protected]>wrote: > Haven't delved into AHAH yet, this might force the issue. > > > Using an easy (=less typing) example. A credit card form. When the credit > card type is selected from a select, the selection needs to fire a > javascript function that will disable fields that don't apply to that card > type (such as CVV). > > > Normally, I would have an onchange event for the select, and noticed that > in the form api, while there is an attribute section to add miscellaneous > attributes, the doc doesn't mention events as examples. And if putting an > event there is legitimate, there isn't a mention of how to include the > responding js function in the form. > > > If AHAH is the way I'm supposed to handle this, I'd appreciate being > pointed to a good similar example, because I'm a bit unclear from the AHAH > entries in the form reference docs, for example, how to relate the > myhandler/js entry to a physical location of the function, and how the > function gets there. > > > Thanks! > > -- Randy Fay Drupal Development, troubleshooting, and debugging [email protected] +1 970.462.7450
