- From: Chimezie Ogbuji <ogbujic@ccf.org>
- Date: Fri, 05 Jan 2007 09:16:14 -0500
- To: "Sébastien CRAMATTE" <contact@zeninteractif.com>
- cc: www-forms@w3.org
We've run into the exact problem in our deployed FormsPlayer XForms and I would also be very interested in finding out if there is a workaround for this limitation. The general problem seems to be that IDs within repeats lose their uniqueness. In our case, activating a switch explicitly behaves unpredictably - it toggles a different block than the one from where the switch is toggled. On Fri, 2007-01-05 at 14:34 +0100, Sébastien CRAMATTE wrote: > Hello > > First of all happy to new year ! > > Well I've trie to use "switch" element inside "repeat" element with a > "toggle action" > What happens is that each "switch" case have got an ID that should be > unique ... isn't it ? > But in a "repeat" context the repeated block will have same ID o no ID > at all ... so how it possible to use "switch + toggle" inside "repeat" > context ? > Note that my XML instance have got three "qos:class" nodes and logically > the "repeat module" copy the switch block 3 times ... > Does anyone have got any ideas ? Does it possible to achieve this ? -- Chimezie Ogbuji Lead Systems Analyst Thoracic and Cardiovascular Surgery Cleveland Clinic Foundation 9500 Euclid Avenue/ W26 Cleveland, Ohio 44195 Office: (216)444-8593 ogbujic@ccf.org =================================== Cleveland Clinic is ranked one of the top 3 hospitals in America by U.S.News & World Report. Visit us online at http://www.clevelandclinic.org for a complete listing of our services, staff and locations. Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you.
Received on Friday, 5 January 2007 14:16:39 UTC