Jostein Kjønigsen

I've always been doing that anyway (making the event-handler idempotent), since thread rendering in Gmail does not seem to be entirely deterministic. It's probably for the best 😃

My suggestion above was above making changes to your own extension to make sure you, in your code, handle the event in a way where (depending on your needs), the...

Depending on how you register the event, it could be registered many times (and thus fired many times). Can you reproduce the issue using the boilerplate repo? https://github.com/josteink/gmailjs-node-boilerplate

I guess the answer is either to create idempotent event handlers (firing 1 or multiple times gives the same result), or someone fixing the event-triggering in gmailjs. I'm not able...

Might be. I didn't personally implement the latest revision of this particular code, so I'm not 100% sure. Remove it and see if it still works? If so, that sounds...

I believe the simplest way to monitor this is to check when the URL query/hash changes. That’s what I do in my extension.

There’s no API for that. But if you structure your code correctly, it should be able to work around for many scenarios. What are you actually trying to accomplish?

Then you will have to access the main compose html-element exposed by the compose instance and add your own custom DOM events on to that.

And if you can find a fairly generic way to do that… feel free to submit a PR 😉

I believe this is pretty old code, originally comitted by @KartikTalwar. He doesn't seem very active any more though, so if this is to be fixed, someone else will need...