+1 - even though there is some other options why this message would
show up, but this is probably the most common one.
form submission will still happen, by the way, it's just an undefined
state for value processing.
regards,
Martin
On 3/29/07, Mike Kienenberger <[EMAIL PROTECTED]> wrote:
I d
I don't know the answer either. However, I suspect as soon as someone
gets the error, they'll find out -- it'll either be a warning or a
fatality :-)
On 3/29/07, Jeff Bischoff <[EMAIL PROTECTED]> wrote:
Mike,
It's great that you're working on this. I was definately a bit confused
the first ti
Mike,
It's great that you're working on this. I was definately a bit confused
the first time I ever ran into that error message. I think your
revisions are a big improvement.
I see only one bit of ambiguity in the new message, the line:
+ " You cannot submit a form after disabling an input
After reading the source code again, here's my revised message:
= "There should always be a submitted value for an input if it is
rendered,"
+ " its form is submitted, and it was not originally rendered
disabled or read-only.";
+ " You cannot submit a form after disablin
If the input for a component is set to disabled via javascript, the
following warning occurs.
"There should always be a submitted value for an input if it is
rendered, its form is submitted, and it is not disabled or read-only."
This is not true if the component is set to read-only via javascrip