GTK: use portals to open URLs instead of xdg-open

[jcollie]

Did you see https://flatpak.github.io/xdg-desktop-portal/docs/doc-org.freedesktop.portal.OpenURI.html? Seems like we should use that and then fallback to xdg-open.

Originally posted by @tristan957 in #5988 (comment)

[jcollie]

I'm wondering if we should have a "global" indicator on the GTK App structure to indicate if portals are in use on the system running Ghostty. I'd prefer not to repeat the "slowness" accusations that we had because we were using a synchronous dbus call to get the system theme. With a global like that we could failover fast to calling xdg-open.

[tristan957]

I'm wondering if we should have a "global" indicator on the GTK App structure to indicate if portals are in use

How would you determine that?

[jcollie]

I'm wondering if we should have a "global" indicator on the GTK App structure to indicate if portals are in use

How would you determine that?

That I'm not sure about yet. Probably send a query to the portal at app init and if we don't get a response or get an error set the indicator to false.

[tristan957]

I don't think people are going to complain about their open_url taking a few milliseconds longer 🤷

[jcollie]

I don't think people are going to complain about their open_url taking a few milliseconds longer 🤷

On some people's systems it takes seconds for the DBus call to timeout instead of erroring out nearly instantly. That's why we had problems with the dark/light detection when we went public. Don't care to repeat that. Just saying that this will take some investigation.

[tristan957]

I don't think people are going to complain about their open_url taking a few milliseconds longer 🤷

On some people's systems it takes seconds for the DBus call to timeout instead of erroring out nearly instantly. That's why we had problems with the dark/light detection when we went public. Don't care to repeat that. Just saying that this will take some investigation.

I'm pretty sure libadwaita already has a synchronous dbus call in the init path, fyi