Aren't popups not supposed to be blocked if it's in direct response to a use action, ie clicking a button? Or has that changed? I feel like Firefox has blocked popups I expected to work.
Sounds about right. The “direct” part being key. I think the framework I was using (Vue 2) was adding some “async” intermediary stuff the way I was using it between the DOM click event and the msal.js window.open call. Once it’s in a callback, it’s not “direct”.
I simplified some code, restarted everything (WebPack hot reloading has been quirky too) and it’s working now. Still took an hour or two of my evening in reading a debugging though, and not exactly sure WHY it went from broken to fixed <shrug>
Pop-up blocking is usually configurable now, with the option to allow or deny all pop-ups independent of whether it is a direct response to user action.
Different browsers unfortunately have different definitions of "direct". Chrome, as you might expect, is most aggressive about carrying that user action forward. Others will discard that interaction in more cases, and may also simply lose that interaction on certain callbacks, such as in a fetch response or indexed db response.
