{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiarp2ymaasa2alz62qdeitzzpeyo64be36t7ew5adtnfgbl2rw2ee",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mm2r3fxlm6h2"
  },
  "path": "/viewtopic.php?t=33437&p=274213#p274213",
  "publishedAt": "2026-05-17T15:06:36.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "tab context menu"
  ],
  "textContent": "> If Dactyloidae is using e10s on a UXP basis then that is really dangerous because there are literally thousands of vulnerabilities in e10s that can cause exploitable crashes.\n\nBased on my own practical experience using e10s in Waterfox 56, the following applies: Should a crash occur, it will most likely affect a tab's web content process — and for a different reason entirely — rather than the entire browser, as I would expect with Pale Moon.\n\n\n> For my part, I already use the uBlock Origin and NoScript extensions to reduce the security risk with Waterfox Classic. Additionally, Container Tabs, URLVoid.com via Flagfox and in some cases Sandboxie Plus. But thanks for pointing that out.\n\n> So caution strongly advised.\n\nFurthermore, it is known that the user — at least in Firefox versions 53 through 56 — can select the option \"Open in new non-e10s window\" via the tab context menu. Therefore, it might be possible to additionally implement a user interface within the browser that allows the user to whitelist (opt-in) trusted document domains for e10s mode, while all other document domains are opened in a non-e10s window.\n\n* * *",
  "title": "Browser Support • Re: Why is Pale Moon so slow?",
  "updatedAt": "2026-05-17T15:06:36.000Z"
}