{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihpl42zvhwdl6y3gg2fdd3o3gnmnda73s2puxvzex7fdgsi64yfjy",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3ml7hcydfkms2"
  },
  "path": "/viewtopic.php?t=33412&p=273579#p273579",
  "publishedAt": "2026-05-06T18:07:22.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": ">\n> Now, when thinking about this it actually seems that Chrome blends with system-wide Qt theme despite being compiled against a static Qt version. I have to test this some more when on Linux.\n\nSo I tried Chromium Qt integration with Chrome and it works well. Don't look at the content area, look at the Chrome menu. It adopts system-wide Qt Widget style (aka Qt theme) despite being compiled against a static Qt version. This is on Debian Trixie using Qt 6.8. The user needs to use a real Qt Widget style (there are many), but avoid the qt6gtk2 compatibility style because then Chrome won't start.\n\nIf you want to avoid \"the legacy trap\" Qt 6 is better than gtk4 in my opinion. We know that gtk5 has dropped X11 support, but we don't know yet if Qt 7 will drop X11 support. If there is a customer base (like Chrome, Brave etc.) it is possible that Qt 7 might keep an X11 back-end. Maybe it doesn't matter because I think Chromium browsers just use gtk and Qt for integration (not their real application toolkits).\n\n* * *",
  "title": "Browser Development • Re: Linux Pale Moon with Qt toolkit",
  "updatedAt": "2026-05-06T18:07:22.000Z"
}