Setting nabMsg twice causes the 2nd to get stuck on screen

[calexander]

Setting nabMsg app var to 'message 1' then immediately firing off a local event that then changes nabMsg app var to 'message 2', will launch both of the popup messages, but clicking OK to dismiss will only work on one of the popups and the other will become unresponsive to the OK button. I've also had this happen with a form widget popup and a single nabMsg popup and the nabMsg popup will be unresponsive.

[Johnny Major]

This will be fixed in the next 6.3 update. Thank you for letting us know