Crash loading form with custom XBL component

[ebruchez]

+1 from customer

[ebruchez]

Issue:

• xforms-disabled is dispatched
• ErrorSummary processes the event
  • tries to evaluate xxf:alert from the event
  • property tries to evaluate, but fails because control is not relevant

Two issues:

• ErrorSummary should not try to evaluate xxf:alert in this case
• evaluating the alert should return it's non-relevant value, not crash

The control that is the destination of xforms-disabled, curiously, appears relevant.

We have a comment saying "Ideally, we would evaluate this lazily, but we use it in the pattern match below".

[ebruchez]

dispatchDestructionEventsForRemovedRepeatIteration() dispatches these events to controls, but they are not marked as non-relevant at this point.This is why we are not returning the non-relevant value.

Best fix would be for ErrorSummary not to try to obtain this information as it is unneeded anyway.