Firefox is not a GTK application by the way. They use their own XUL/XPCOM framework and are in the long-running process of porting everything to HTML/JS/CSS.
There must be GTK somewhere, gtk3 is a dependency on Arch and the GTK_USE_PORTAL env var strongly suggests GTK has something to do with the file chooser. If they’re going to have to reimplement the latter, I hope it’s going to be less horrible than the GTK one but knowing Mozilla I’m not that faithful…
It does use the GTK file-open dialog by default (although distributions can swap that out).
It also takes inspiration from the GTK theme for drawing buttons and whatnot, so they fit into the OS. KDE generates a GTK theme, though, so that’s rarely a problem.
Firefox is not a GTK application by the way. They use their own XUL/XPCOM framework and are in the long-running process of porting everything to HTML/JS/CSS.
There must be GTK somewhere,
gtk3is a dependency on Arch and the GTK_USE_PORTAL env var strongly suggests GTK has something to do with the file chooser. If they’re going to have to reimplement the latter, I hope it’s going to be less horrible than the GTK one but knowing Mozilla I’m not that faithful…It does use the GTK file-open dialog by default (although distributions can swap that out).
It also takes inspiration from the GTK theme for drawing buttons and whatnot, so they fit into the OS. KDE generates a GTK theme, though, so that’s rarely a problem.