Hi,
I am experiencing some issues with nested <xforms:group> constructs being used in Orbeon 3.7.1. The behaviour that I have observed is that when the outer group toggles from disabled to enabled, it will by default show the inner <xforms:group>, even when the group is disabled. In my example I have a label and an input control being controlled inside the nested group. When the outer group is disabled and re-enabled, the label inside the inner group will appear, even when the nested condition for the group is not true. I have enclosed an demonstration of this happening in the link below. http://www.screencast.com/users/murraymaleschuk/folders/Jing/media/5e73c90e-a32c-4cc2-bb82-4769171ff0ff Is this a known issue or is this a possible Orbeon bug? Do I need to rethink of how I am doing this and not use the nested <xforms:group> construct? Many thanks, Murray |
Hi Murray, The specification says that the group model allows a form author to aggregate other form controls into a single, aggregate user interface component. http://www.w3.org/TR/xforms11/#ui-group-module Also, the xforms-enabled (disabled, relevant) event is not cancelable and bubbles. So I would presume this means that enabling a group will descend to children. That said, perhaps it does not need to be a child. I have forms that, when one case is toggled, they send a message to case in another switch (and area of the form) to enable: <widget:tab id="a-tab"> <xforms:action ev:event="xforms-select"> <xforms:toggle case="events-case"/> </xforms:action> ... The tab widget is an embellished case. HTH, Hank On Jul 15, 2009, at 5:18 PM, Murray M wrote: > > Hi, > > I am experiencing some issues with nested <xforms:group> constructs > being > used in Orbeon 3.7.1. The behaviour that I have observed is that > when the > outer group toggles from disabled to enabled, it will by default > show the > inner <xforms:group>, even when the group is disabled. > > In my example I have a label and an input control being controlled > inside > the nested group. When the outer group is disabled and re-enabled, > the label > inside the inner group will appear, even when the nested condition > for the > group is not true. > > I have enclosed an demonstration of this happening in the link below. > > http://www.screencast.com/users/murraymaleschuk/folders/Jing/media/ > 5e73c90e-a32c-4cc2-bb82-4769171ff0ff > http://www.screencast.com/users/murraymaleschuk/folders/Jing/media/ > 5e73c90e-a32c-4cc2-bb82-4769171ff0ff > > Is this a known issue or is this a possible Orbeon bug? Do I need > to rethink > of how I am doing this and not use the nested <xforms:group> > construct? > > Many thanks, > Murray > -- > View this message in context: http://www.nabble.com/problem-with- > nested-%3Cxforms%3Agroup%3E-tp24508120p24508120.html > Sent from the ObjectWeb OPS - Users mailing list archive at > Nabble.com. > > > -- > You receive this message as a subscriber of the [hidden email] > mailing list. > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > OW2 mailing lists service home page: http://www.ow2.org/wws NEES@UCSB Institute for Crustal Studies, University of California, Santa Barbara 805-893-8042 -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Administrator
|
In reply to this post by Murray M
Murray,
This doesn't look right. Can you share with us the example you were showing in that screencast, so we can run it in the XForms sandbox? Alex |
Alex, Here is the example application from the demo I showed. I have one outer group with three nested groups in this example. An interesting point is that the input control seems to have the correct behaviour, it's only the labels that have the problem. Thanks for your help. example.xhtml |
Administrator
|
Murray,
Good catch. I managed to reproduce this in a simpler example and created a bug for this: http://forge.ow2.org/tracker/index.php?func=detail&aid=314052&group_id=168&atid=350207 Alex |
Administrator
|
Murray,
BTW, this is not an easy one to fix, so most likely not one we'll do very soon. I'd recommend you don't use nested groups around <xhtml:tr> or around <xhtml:td>. Alex |
Administrator
|
This was an interested one to fix / implement, but it is now done. So you can use nested <xforms:group> in a table around a <xhtml:tr> or <xhtml:td>, just as you could before (and still can!) everywhere else. Alex |
Free forum by Nabble | Edit this page |