http://livedocs.adobe.com/ Macromedia LiveDocs - online documentation with user feedback. Copyright 2009, Macromedia, Inc. 2009-11-25T14:20:54 en-us http://livedocs.adobe.com/coldfusion/6/CFML_Reference/Tags-pt139.htm#1095 There is a problem I have found with CFFORM and CFINPUT tags.If you set define a cfform tag on a page and define all your cfinput tags in a componenet and then calls this component with in the cfform tag, It will not compile and will generate error. While if I use html input tag instead of cfinput tag then its works. I have code which demonstrates this problem. If any one intrested, can mail me. starkami 0 0 2003-07-07T10:50:00 http://livedocs.adobe.com/coldfusion/6/CFML_Reference/Tags-pt139.htm#512 Make that three bugs. The error message generated by MX if you pass an attribute that doesn't exist lists out the attributes that the tag accepts. One of these is ENABLEJAR. This attribute isn't documented here, and I looked in the form.cfm template used by MX, and it's listed as an attribute, but it isn't implemented in the code anywhere! rbils@amkor.com 0 0 2002-07-08T03:25:00 http://livedocs.adobe.com/coldfusion/6/CFML_Reference/Tags-pt139.htm#511 Two issues here. First, the ONLOAD attribute is not a standard attribute in the HTML FORM tag. It looks like it's supposed to invoke functionality within the CFFORM tag and it's associated JS flie. However, it's broken. Setting ONLOAD="yes" always causes an error when the form is submitted as _CF_signalLoad() is never called in the cfform.js file (unless you add an onLoad to your page's BODY attribute.<br><br>The second issue is that this documentation lists METHOD as an attribute. This implies you can specify GET or POST. This is not the case as POST is hardcoded into the CFFORM tag.<br><br>If you need a test case for bug number 1 above, email me and I'll be happy to work with your engineers. rbils@amkor.com 0 0 2002-07-08T03:23:00