Open Bug 1774128 Opened 3 years ago Updated 2 years ago

Provide a way to fetch container names from the outside

Categories

(Core :: Security, enhancement)

Firefox 103
enhancement

Tracking

()

People

(Reporter: sindresorhus, Unassigned)

References

Details

Steps to reproduce:

I maintain this browser picker app and I would like to integrate it with Firefox containers, so users can define that certain links should open in specific containers. However, I need to be able to fetch a list of containers so the user can pick one in the user-interface.

Possible solutions:

  • AppleScript (preferred)
  • Bundled command-line tool
  • x-callback-url: firefox+container:x-callback-url/list?x-success=velja://x-callback-url/container-list

I'm aware I can already build a Firefox add-on that uses browser.contextualIdentities.query() and sends it back to my app, but it's a lot of work to implement, and it means every app that wants to fetch these have to do the same. It's just not something I would personally choose to do.

I think it would be natural to expose containers to AppleScript.

Thank you for submitting this enhancement. I'll set this to NEW and waiting for the developer's opinion about it.
If this is not the correct component, please feel free to change it to a more appropriate one. Thanks.

Status: UNCONFIRMED → NEW
Component: Untriaged → Networking
Ever confirmed: true
Product: Firefox → Core
Component: Networking → General
Product: Core → Firefox

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Networking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: General → DOM: Networking
Product: Firefox → Core
Component: DOM: Networking → Security

This is already something possible by using the Native Messaging API. I don't think the developers will expose this directly so it's probably your only viable solution.

(In reply to Danny Colin [:sdk] from comment #3)

This is already something possible by using the Native Messaging API. I don't think the developers will expose this directly so it's probably your only viable solution.

I'm aware and I already addressed that in the issue body.

Agreed that this would be very beneficial to expose to AppleScript for us as well, it would provide one unified interface for developers without us all having to write our own extensions that all of our users have to manually install.

Any news on that issue so Velja and Choosy Developers can implement it ?

See Also: → 1774127
You need to log in before you can comment on or make changes to this bug.