- From: Ronald van Kuijk <rvkuijk@intercommit.nl>
- Date: Tue, 31 Aug 2010 12:08:28 +0200
- To: e-letter <inpost@gmail.com>
- CC: www-forms@w3.org
- Message-ID: <4C7CD49C.1060405@intercommit.nl>
Op 31-08-10 11:59, e-letter schreef: > On 31/08/2010, Ronald van Kuijk<rvkuijk@intercommit.nl> wrote: >> In betterForm I get this error (after switching ' to " and vice-versa) >> >> xforms-binding-exception: property 'relevant' already present at model item >> *URL: *http://127.0.0.1:8080/betterform-trunk/forms/e-letter.xhtml >> *Element causing Exception:*/html[1]/head[1]/xf:model[1]/xf:bind[2] >> * >> *This is not allowed according to the spec and an error should be >> thrown... Personally I always have 2 different XForms processors >> (BetterFORM and Orbeon, but I always use the former) that I use to >> check if I'm wrong or the engine. >> >> So if Mozilla XForms does not complain, it is in violation of the spec >> (see point 2 in http://www.w3.org/TR/xforms11/#evt-rebuild) >> >> It can be solved by changing it to one bind: >> >> <xf:bind nodeset="stage" relevant="../purpose='ewbrl' or >> ../purpose='nibrf'" /> >> > What to do if the disable function is required for more than 1 > condition (as described previously)? That is what is done in what I proposed... there is an 'or'.... You can use any xpath(2) depending on the engine
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Tuesday, 31 August 2010 10:08:57 UTC