My code should be listening for a window close event to dismiss the intro and pageAction panels. This had been working prior to the memory leak fixes. What happens now is when I close a window with a panel open, the panel doesn't get properly dismissed, and when I try clicking the pageAction button on any subsequent site, it doesn't open.
Steps to reproduce:
npm run firefox forcing "fast" or "private" treatment
Go to a website like npr.org
Notice the intro panel opens
Open a new window
Close the initial window
Notice in the browser console, nothing is logged for the panel being dismissed
Visit a website in the remaining window like nytimes.com
Click the pageAction button
Notice the pageAction panel does not open; this is because it is gated on the intro panel having been properly dismissed.
The same effect happens for the pageAction panel (dismiss the intro panel in step 3, open the pageAction panel and then proceed with step 4).
My code should be listening for a window close event to dismiss the intro and pageAction panels. This had been working prior to the memory leak fixes. What happens now is when I close a window with a panel open, the panel doesn't get properly dismissed, and when I try clicking the pageAction button on any subsequent site, it doesn't open.
Steps to reproduce:
npm run firefoxforcing "fast" or "private" treatmentThe same effect happens for the pageAction panel (dismiss the intro panel in step 3, open the pageAction panel and then proceed with step 4).