Right now, XUL errors show up as asserts, we really should either print them out to stdout or throw up an error dialog, like JavaScript does for 4.5. What we have kinda sucks, asked most of the people on the CC line here and they all agreed. Hyatt suggested that I file a bug to waterson, here you go Chris. Any ideas?

I can easily change ASSERT to printf() or PR_LOG(). Other suggestions are welcome.

Ugh. This is just way too open ended. Milestone shuffle -- ACTIVATE!

This looks to be a subset of bug #6211 and might be worth marking as a duplicate of that.

On second thoughts, most of 6211 would use XUL, so this might not be a dupe as such. But it should probably still use the same errors API.

Can we break this bug into pieces that wouldn't be stuck at m15?

BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL. XUL component will be deleted.

marking wontfix.