> The weird thing to me is that you can't get it to happen in a
> different browser when CF is the one processing the info and sending
> html to the browser. Just a long shot but try it two ways... hitting
> enter to submit and actually clicking the submit button with your
> mouse. hitting enter will cause the submit form field variable to be
> undefined but clicking it will not...
>
>
> ----- Original Message -----
> From: Burns, John D
> To: CF-Talk
> Sent: Tuesday, March 16, 2004 4:50 PM
> Subject: RE: "Undefined in Form" when using MSIE
>
>
> As weird as this may sound (and possibly uneducated) is there any
> chance
> that it's CF losing the form scope somehow (or maybe it's there but
> for
> some reason CF isn't able to read it)? It seems like a lot of people
> on
> the list have mentioned this problem. Have we narrowed down the CF
> version being used when this is happening? I'd think that if IE had
> a
> problem like this that there would be a lot more people complaining
> in
> the web world. Maybe there are and I just haven't heard it. Just a
> thought.
>
> John Burns
>
> -----Original Message-----
> From: Nick Han [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 16, 2004 4:41 PM
> To: CF-Talk
> Subject: Re: "Undefined in Form" when using MSIE
>
> I have had the same problem with my sites and raised the subject in
> this
> list before. I guess there's no real fix as far as a patch to fix IE.
>
> The kluge I have to prevent the processing page from erring out on a
> post action, when this mysterious bug occurs.
>
> Before processing the submitted form, I do this.
>
> <cfif StructIsEmpty(form)>
> do a js back.
> <cfabort>
> </cfif>
>
> Nick Han
>
> >>> [EMAIL PROTECTED] 03/16/04 12:26PM >>>
> We are experiencing random occurrences of the error message "element
> XXXXX undefined in form" when using MSIE 6.0. (XXXXX represents the
> names of various form variables and is always the first form variable
> referenced in the action file.) This problem cannot be duplicated
> using
> Netscape. When the error occurs, debugging reveals the scope
> variable
> section "Form Names" does not exist and thus indicating no form
> variables are passed through. The form is submitted without error
> about
> 95% of the time and of course, debugging displays the form names and
> values. When the error occurs, we can actually refresh the screen
> and
> the form variables are present again. (Of course, sometimes we must
> refresh the page a couple of times before the form variables are
> present.) This leads us to believe the form variables exist but for
> some
> reason cannot be interpreted by MSIE at random occurrences. This
> problem is not isolated to just one form either. It randomly occurs
> on
> numerous forms i!
> n various applications.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
