testcase is https://bugzilla.mozilla.org/attachment.cgi?id=222008

There is no guarentee that a control without a binding attribute will work. One of the binding attributes (@ref or @bind) are required on elements that take single node binding attributes: http://www.w3.org/TR/xforms/index-all.html#structure-attrs-single-node I believe that xf:output is the only element that doesn't have to have a single node binding attribute.

(In reply to comment #1) > There is no guarentee that a control without a binding attribute will work. > One of the binding attributes (@ref or @bind) are required on elements that > take single node binding attributes: > http://www.w3.org/TR/xforms/index-all.html#structure-attrs-single-node > > I believe that xf:output is the only element that doesn't have to have a single > node binding attribute. > At least they worked ok. And at least we should have exception in js console :) : Error: aValue has no properties Source File: chrome://xforms/content/select.xml Line: 622

Hmmm, might have been fixed by my patch for bug 355743. When I look at the testcase you point to, I see two items in the select. With an older build, I do not.

(In reply to comment #3) > Hmmm, might have been fixed by my patch for bug 355743. When I look at the > testcase you point to, I see two items in the select. With an older build, I > do not. > Right. *** This bug has been marked as a duplicate of 355743 ***