Tab data disappears after left-clicking DuckDuckGo search result.

• Temporary Containers Version: 1.3
• Firefox Version: Nightly 72.0a1
• Operating System + Version: Fedora x64 + Kernel 5.3.6-100
• Non-default Options/Preferences in Temporary Containers: N/A
• Other installed Add-ons + Version: uBlock Origin, Decentraleyes, MAC, CAD

Actual behavior

Search tab becomes blank, URL disappears, unable to reload page

Expected behavior

search tab remains the same, nothing happens to it, i can go back and forth with ease

Steps to reproduce

1. Visit www.duckduckgo.com
2. Search for anything your heart desires
3. Left-click on any result to go to new tab with your search result (middle click doesn’t produce this behavior)
4. Go back to the Duck Duck Go tab and find that it’s blank, the URLbar is empty and the only remnant that you were ever there is the title of the tab never changed.

Notes

If I disable Isolation globally, this doesn’t happen. I left click on a search result and it opens the result in the same tab, I can go back to the search page and click on another result.

Browser Console shows the following right after left-clicking a search result:

Unchecked lastError value: Error: Frame not found, or missing host permission context-menu.js:280
    activateDomain moz-extension://599ee7bc-01ab-4997-a29f-52b17fccb2ab/data/context-menu.js:280

TypeError: document.body is null contentscript.js:1:1

SecurityError: Permission denied to access property "document" on cross-origin object ExtensionContent.jsm:401

SecurityError: Permission denied to access property "removeEventListener" on cross-origin object ExtensionCommon.jsm:415

The first one is from CAD, the second one is from Temporary Containers, and the last 2 are from Firefox, probably because of blocking something from loading via uBlock.

[cpeterso]

The Firefox bug linked above is about a Firefox automated test failure (that is no longer reproducible). Since this Temporary Containers extension problem is reportedly still reproducible, I filed a new Firefox bug specifically for this problem:

https://bugzilla.mozilla.org/show_bug.cgi?id=1648211

[stoically]

Ah, interesting. Didn’t know about fission, thanks for letting me know. With that enabled I can reproduce indeed, though can’t do anything about it. So hopefully they sort it out before they deploy it.