> What comes to mind is have an external application handle .my_extension
> files and open them in Firefox. One the file is opened in a tab, the
> content script can take care of it. That would only work if the file is
> plain text or some other format Firefox supports.
Interesting, thanks.
You gave me this idea: the job could be splitted into 2 parts.
*** part 1: one native app doing this:
<xxx.my_extension file> => format conversion => <xxx_my_extension.html> +
open Firefox with <xxx_my_extension.html>
<xxx_my_extension.html> would be a do-nothing html/JS file with the initial
<xxx.my_extension> file content put into a JS array or just a big JS string.
*** part 2: loading the <xxx_my_extension.html> file into Firefox
Loading the external web ressources through a WebExtension, and, first,
read the JS input "buffer" (array or string) as a first step.
Well, that being said:
1) I don't see how not to do a format conversion as Firefox supports only
html (as the single format one could inject into JS behaviour through
WebExtension)
2) I am a bit frustrated that [part 1] has to be a native app (and could
not be done through Firefox), so a heavy app
3) and still, having to sign such [part 2] extension with an _external_
org. Mozilla for just injecting some _internal_ (url) web ressources looks
like awkward to me.
But, again, thanks for the idea.
On second thoughts, if I write [part 1] native/heavy app, I could make the
format conversion, but also inject the external web ressources into
<xxx_my_extension.html>.
Then, no need for [part 2]-WebExtension doing web ressources injection.
So, in the end, let's wrap up:
* I didn't see how to implement my use case with WebExtension only
* if WebExtension alone can't do the job, let's put in a native app to do
part of the job
* but if a native app is used, such app could do all the job, even the job
of WebExtension side, so let's forget about WebExtension
WebExtension KO for my use case, back to native/heavy app: bad luck.
Dominique