This issue is due to default values being considered for bind/@readonly
and bind/@relevant in consecutive bindings in r494.
r496 should fix this: it's OK with the test case and some variations of it.
Thank you for your feedbacks!
-Alain
Le 27/03/2011 00:03, Leigh L. Klotz, Jr. a écrit :
> bind/@readonly and bind/@relevant work if it is the only or second bind
> on a node, but not if it is the first.
>
>
> If the second bind assigns readonly, relevant, or type, then the first
> bind (readonly or relevant) fails.
>
>
> <?xml version="1.0"?>
> <?xml-stylesheet type="text/xsl" href="/xsltforms/xsltforms.xsl"?>
> <?css-conversion no?>
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:xf="http://www.w3.org/2002/xforms"
> xmlns:ev="http://www.w3.org/2001/xml-events"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> <head>
> <title>bind example</title>
>
> <model xmlns="http://www.w3.org/2002/xforms">
>
> <instance id="main">
> <data xmlns="">
> <title/>
> </data>
> </instance>
> <!-- swap the order of these binds and readonly will work -->
> <!-- drop the second bind and readonly will work -->
> <!-- use relevant instead of readonly in the first bind and the same
> problems occur -->
> <bind nodeset="title" readonly="false()" />
> <bind nodeset="title" type="xsd:string" />
> </model>
> </head>
> <body>
> <group xmlns="http://www.w3.org/2002/xforms">
> <input ref="instance('main')/title">
> <label>Title:</label>
> </input>
> </group>
> </body>
> </html>
>
|
