Better integration with the browser extension #374

New issue

Open

opened 2024-03-19 23:05:55 +01:00 by blacklight · 0 comments

blacklight commented

2024-03-19 23:05:55 +01:00

Owner

First of all, the browser extension needs a rework. It still contains references to removed settings (like the websocket port), it should just use a connection URL instead.
The action selector is also broken.
We need a way for the UI to communicate with the extension, so if the UI detects that the extension is running it can automatically add an e.g. Add To Extension button on the actions panel. This could be done by using a websocket connection between the extension and the UI, or with a hidden DOM element injected by the extension that the UI can write into.

- [ ] First of all, the browser extension needs a rework. It still contains references to removed settings (like the websocket port), it should just use a connection URL instead. - [ ] The action selector is also broken. - [ ] We need a way for the UI to communicate with the extension, so if the UI detects that the extension is running it can automatically add an e.g. _Add To Extension_ button on the actions panel. This could be done by using a websocket connection between the extension and the UI, or with a hidden DOM element injected by the extension that the UI can write into.