It is definately the onAfter that FF doesn't like in this scenario.

Reply via email to