I wonder if having the GetManifest() and Start() actually makes any sense in the Firefox. Could be sufficient enough to pass the manifest lookup and parsing to the portal and from the Firefox side only use CreateSession(requested_webextension_name, extension_id)->GetPipes()->Close() methods?
We've been discussing this with swick regarding to https://github.com/flatpak/xdg-desktop-portal/pull/705 - because it also have to parse the webextension json files. He also brought idea to have webextension itself in the flatpak where we hit that the json files won't be accessible from the host system. The webextensions then will have to implement dbus interface to pass pipes (as it works with this patch) and the flatpak portal could stay in between to make it happen. From the Firefox point of view it won't require any additional changes. Only portal have to do all the lifting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
