Latest 3.0, haven't tested older versions.
Calling Quit inside .onUserAbort acts like Abort (we don't quit), but when you then click Next/Install, it quits.
I'm guessing the quit message is posted but not handled until the next event.
Yes, it's silly to call Quit in .onUserAbort, so this is very low priority - but it should quit immediately, or be ignored completely.
Apologies, right now I cannot replicate this using a simple script. It's definitely happening, but it appears that something else in my script is contributing to the weird behavior, although I don't know what yet. I'll post an example when I figure it out.
Okay, replicated
I'm guessing this only happens on custom pages?
seems to work but it is a bit of a hack.
Indeed, it appears to be due to nsDialogs taking over the message loop.