{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicpgzwvnvmhqzkrhbtsywc4ahh6eljomvsydtdes3ajo7vqysqac4",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mievngos75f2"
  },
  "path": "/viewtopic.php?t=33281&p=271656#p271656",
  "publishedAt": "2026-03-31T17:38:29.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "While we still have some vestiges of e10s, it should not be considered usable or anywhere near complete.\nAs pointed out as well there are hundreds of sec issues in e10s we never adressed for being out of scope for our development. If you enable it by force you are destroying the security of your browser.\n\n\n> Working on backporting their fixes as we speak\n\nI'm pretty certain you don't know of or have access to many of the sec bugs caused directly or indirectly by e10s. I really don't think you want to do this on UXP. Your fork of course, so you can decide for yourself, but be very aware of what you are getting yourself into if you continue building on our platform for e10s use.\n\nIf it wasnt for oop plugin usage, we likely would have removed all IPC code from the platform already but as it is we still wanted it for that use... But that does not make it safe for web content and js.\n\n* * *",
  "title": "Platform Development • Re: e10s support question",
  "updatedAt": "2026-03-31T17:38:29.000Z"
}