(In reply to comment #36)
> Gavin says he's got a plan for making the wizard code not advance a wizard
> before the page is done loading,
But the problem is that the XBL code isn't updated properly if the binding
is attached to the <wizard> element too early. Use DOMi to see what the
non-anonymous code looks inside the binding.
Maybe re-binding XBL to <wizard> when DOMContentLoaded fires could help here.
That would be an ugly hack though.
(In reply to comment #36)
> Gavin says he's got a plan for making the wizard code not advance a wizard
> before the page is done loading,
But the problem is that the XBL code isn't updated properly if the binding
is attached to the <wizard> element too early. Use DOMi to see what the
non-anonymous code looks inside the binding.
Maybe re-binding XBL to <wizard> when DOMContentLoaded fires could help here.
That would be an ugly hack though.