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 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 element via javascript." From the seat of a naive user, it is unclear from this wording whether disabling an input will prevent the entire form submit from succeeding. At the risk of making the message even longer, it would be good to point out the consequences of this mistake, e.g. + " You cannot submit a form after disabling an input element via javascript - doing so will cause the entire submit to fail" or + " You cannot submit a form after disabling an input element via javascript - doing so may have unexpected results" I don't know. I don't remember exactly what the effects of this are, it's been a while since I've had the problem. If we know what damage this does though, we should state it. In any case, the changes are definately for the better. You get my +1, even with no further revisions. Regards, Jeff Bischoff Kenneth L Kurz & Associates, Inc. Mike Kienenberger wrote: > 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 disabling an input element via > javascript." > + " Consider setting read-only to true instead" > + " or resetting the disabled value back to false prior to form > submission."; > > > > On 3/29/07, Mike Kienenberger <[EMAIL PROTECTED]> wrote: >> 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 javascript. >> I don't think the error above is clear. >> >> Explanation of what's happening underneath here: >> http://webdesign.about.com/od/forms/a/aa071805.htm >> >> Perhaps it should be rewritten as: >> >> "There should always be a submitted value for an input if it is >> rendered and its form is submitted. You cannot submit a form after >> disabling an input element via javascript. Consider using read-only >> instead or resetting the disabled value back to false prior to form >> submission." >> >> I'm going to start with this, but I'd like to have someone else >> confirm that this is a better solution. >> >> https://issues.apache.org/jira/browse/MYFACES-1569 >> > > >
