I would suggest trying to use css backgrounds or borders in different
colors around the elements in question to try to debug what is
happening. You probably have something overlapping the button so that
it can't be clicked. If it used to work and doesn't anymore, I'm
guessing that it was a change in Firefox that is causing this behavior.
There hasn't been a ton of Mozilla xforms activity to account for it.
If you find that it is a bug (something overlapping that shouldn't be,
for example), I'd suggest simplifying the testcase so that XForms isn't
in the equation and then submitting a bug to Firefox. Our UI is just
HTML so if there is a bug affecting us, it'll affect HTML. But the
Firefox folks will worry about a bug affecting HTML a lot more :-)
Hope that this helps,
Łukasz Pytlarz wrote:
> There is a strange case with /xform:trigger/ element inside
> /xform:repeat/. When attribute /appearance/ is set to /minimal/ and also
> css rule is written with /float: left/ there is no way, using the
> trigger, to change xf-repeat-index.
> In older version of the Xforms plug-in, for example 0.8.6ff3, such
> construction has just worked fine. Now, one only way, to use trigger to
> change index is to use /display: //inline-block/ instead /float: left./
> Of course, there is a lot more way do to this, using other controls with
> different action but I have only /xform:output/ and /xform:triggers/ in
> this case.
> /Is there something I don't understand with this or is just a bug?
> By the way, when we can expect the official release of the Xforms
> plug-in for FF4, 0.8.8?