Return-Path: Delivered-To: apmail-myfaces-dev-archive@www.apache.org Received: (qmail 27567 invoked from network); 29 Mar 2007 16:09:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Mar 2007 16:09:52 -0000 Received: (qmail 44150 invoked by uid 500); 29 Mar 2007 16:09:57 -0000 Delivered-To: apmail-myfaces-dev-archive@myfaces.apache.org Received: (qmail 44106 invoked by uid 500); 29 Mar 2007 16:09:57 -0000 Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Development" Delivered-To: mailing list dev@myfaces.apache.org Received: (qmail 44094 invoked by uid 99); 29 Mar 2007 16:09:57 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Mar 2007 09:09:57 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of mkienenb@gmail.com designates 66.249.90.177 as permitted sender) Received: from [66.249.90.177] (HELO ik-out-1112.google.com) (66.249.90.177) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Mar 2007 09:09:48 -0700 Received: by ik-out-1112.google.com with SMTP id b32so181156ika for ; Thu, 29 Mar 2007 09:09:27 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OcHPjJaR4ZX/aICaeGA8TZuFtFEnnGz4dZR76RS1nx+p9H4EPo404WK/YlRYLdAx0Fnh82fwpe4STDwxoem6f8vkjIGDKbRT4lbELeq14Wc98Vj6yg06MDDUtAotlTgpktemcee9LbsJh10i4e7slU6hHj71tNZtse7QMhVlPxw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=mRxgUMPoTflnw7RuneRDzE2LJJzmgioysiaTB1+rR3z25gOKxreXa/uGEtC3Exh4L9e9FOHy8vK10xoYr8/PmuIMnDmOjmbbnbAdRDFE/TNkNEBPNQtz7l+uhIofC7eV6I0Wa6FgpQkpyXRnNyctJQLJxi6OnAK1WGfeSDUmOCI= Received: by 10.114.153.18 with SMTP id a18mr299963wae.1175184566106; Thu, 29 Mar 2007 09:09:26 -0700 (PDT) Received: by 10.114.160.3 with HTTP; Thu, 29 Mar 2007 09:09:25 -0700 (PDT) Message-ID: <8f985b960703290909k375c7db7u62bcf9ff0291418e@mail.gmail.com> Date: Thu, 29 Mar 2007 11:09:25 -0500 From: "Mike Kienenberger" To: "MyFaces Dev mailing list" Subject: Re: Rewording "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." In-Reply-To: <8f985b960703290902md91e104m136e71e5f2fa2040@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8f985b960703290902md91e104m136e71e5f2fa2040@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org 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 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 >