{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiexaxmzlxn7cbzxnchlqsaw7mehs7vstyhx7qfspqzjlllaf3gpr4",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mlc6laf3fl62"
  },
  "path": "/viewtopic.php?t=33412&p=273655#p273655",
  "publishedAt": "2026-05-07T21:25:15.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> Someone will need to test QT with NPAPI plugins obviously. I don't think it will work. That being said NPAPI plugins don't work most of the time on Linux for me anyways without a bunch of hacky workarounds. I had lightspark working a few weeks ago but it started crashing for me so I have no working NPAPI plugin on this particular machine to test.\n\n**Off-topic:**\nThe only way it might work is if plugin-container is built against GTK2. Doesn't matter so much what the browser itself is built against as long as plugin-container is built against the same thing as the plugin.\n\nBut yeah, overall it seems like NPAPI support in Linux is not reliable. I did actually get Java working perfectly without GTK2 at all. I wasn't really able to test Lightspark's ability to run on my GTK2-free NPAPI setup, though, because I couldn't get it to run even on normal unmodified Pale Moon with GTK2 available.\n\nSo the best plugin to test with NPAPI is the final version of Java that included the plugin. I think Netscape used to bundle Java ages ago, so that's probably among the original use cases for NPAPI, and why it's so resilient.\n\n* * *",
  "title": "Browser Development • Re: Linux Pale Moon with Qt toolkit",
  "updatedAt": "2026-05-07T21:25:15.000Z"
}