Our actions dispatch events to the model to "make things happen". That's actually wrong. F.x. for rebuild: "This action causes the processing of xforms-rebuild to happen, bypassing the normal event flow." [http://www.w3.org/TR/2006/REC-xforms-20060314/slice10.html#action-rebuild] Note "bypassing the normal event flow". So the action should be performed no matter what. So we need to tell the model to do the action directly, without the event. This is probably needed for bug 300591 also, so it might happen as part of that.
Oh, and: "Actions that directly invoke rebuild, recalculate, revalidate, or refresh always have an immediate effect, and clear the corresponding flag. The XForms Actions in this category are: rebuild recalculate revalidate refresh " [http://www.w3.org/TR/2006/REC-xforms-20060314/slice10.html#action-action]
Hmm, just discovered that anything inside an action block should _never_ send events -- including the action block itself. That seems weird (wrong) to me. I've written to the WG: http://lists.w3.org/Archives/Public/www-forms/2006May/0129.html
(In reply to comment #4) > Hmm, just discovered that anything inside an action block should _never_ send > events -- including the action block itself. That seems weird (wrong) to me. > > I've written to the WG: > http://lists.w3.org/Archives/Public/www-forms/2006May/0129.html > current thinking: http://www.w3.org/MarkUp/Forms/Group/Drafts/Sources/REC-xforms-10-2ndEdition-errata.html#E5a