Jostein Kjønigsen
Jostein Kjønigsen
Oh my bad then. Well, the good news is you got things working, I guess?
If your extension was published anywhere, it should be easy to just redownload the ZIP/XPI and extract the old code, right? ;)
> I had built one based on the earlier boiler-plate example but that's now obsolete and has stopped working altogether. To be clear... the boilerplate works fine for me. When...
I'm including jquery, but bundling it. Once loaded, it should be easy to inject into the global DOM if you need it.
I guess this is a web-extension question in general, and not specific to GmailJS. That said I've been doing custom NPM build-tasks in their own build-scripts, custom-tailored for my extensions...
Nope. All corporate 🙂
But like I’ve said elsewhere, this is not really a GmailJS related problem, but it’s a general web extension development thing. I suggest you look up the regular places like...
Thanks for reporting. This looks weird, but as long as we have one of the IDs we should be able to make things work. I’m not sure what I think...
After testing, I've been able to reproduce this issue myself in a few threads. When I saw thew result of `gmail.new.get.thread_id()` in those threads, it evaluated to `"undefined"` (as opposed...
Thanks for the report and investigation. Can you submit this as a PR and I’ll try to test the changes to see if they work for me.