Bugzilla

After the fallback in D128310, untangling this from bug 1735899, and testing after Fission was rolled out to everyone in Firefox 96, i believe this is only happening when we rapidly create and destroy <browser>s for the popup _in anticipation_ of a click on a browser action.  By the time the child process asks for FrameData, the browser is already being torn down in the parent, so no answer arrives.  This is similar to the warning from layout we get while scrubbing the mouse over browser actions buttons without clicking:

> Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content.

Unless anyone has actual issues of extension popups not actually working still, I'm closing this as fixed.  The warning is still here, but possibly only because we added explicit code to log the error in such cases, these conditions were probably happening before bug 1708243, only hidden behind the `|| {}` fallback.

I never see the warning in one of my profiles, and in the other only after I spend 10+ seconds of moving my mouse over (multiple) browser actions.  So I'm closing this as "fixed", and if the warning is too common for others, please open a separate bug to consider dropping it.

After the fallback in D128310, untangling this from bug 1735899, and testing after Fission was rolled out to everyone in Firefox 96, i believe this is only happening when we rapidly create and destroy <browser>s for the popup _in anticipation_ of a click on a browser action.  By the time the child process asks for FrameData, the browser is already being torn down in the parent, so no answer arrives.  This is similar to the warning from layout we get while scrubbing the mouse over browser actions buttons without clicking:

> Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content.

Unless anyone has actual issues of extension popups not actually working still, I'm closing this as fixed.  The warning is still here, but possibly only because we added explicit code to log the error in such cases, these conditions were probably happening before bug 1708243, only hidden behind the `|| {}` fallback.

I never see the warning in one of my profiles, and in the other only after I spend 10+ seconds of moving my mouse over (multiple) browser. If the warning is too common for others, please open a separate bug to consider dropping it.