Created attachment 8360612 [details] [diff] [review] tab-null-fix I was debugging some stuff in the dom/browser-element code today and I get a ton of "aTab is null" errors. The problem is that these frames emit a DOMTitleChanged event that is handled by the tabbrowser element. They pass the |contentWin == contentWin.top| test because that's how <iframe mozbrowser> is supposed to work. But they're not tabs, so we get null when trying to find a tab for the window. This is a simple fix.
Is <iframe mozbrowser> something web content in the wild can and should use? Otherwise, I don't see why the DOMTitleChanged event would bubble up from one of tabbrowser's browsers.
I don't see the error anymore.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.