Office.context.document.removeHandlerAsync unexpected behavior during development with live-reload about office-js

[kbrandl]

@carruthe apologies for the lack of response on this. Are you still having trouble? The Office.js API and platform has evolved quite a bit since this issue was opened, as have the docs, so this may no longer be an issue. I'm going to close this issue, but please feel free to re-open it or log a new issue in the OfficeDev/office-js repo if you're still having trouble.

[RXminuS]

Yes this issue still exists; could we re-open? I have the exact same behaviour but using FuseBox HMR.

Also...I don't understand how Office.context.document.removeHandlerAsync is supposed to work...it takes in a "string" as a function name? But the handler that we pass to Office.context.document.addHandlerAsync takes a function. In my case I pass in an arrow function...which is unnamed; how would you remove that one. If I call the Office.context.document.removeHandlerAsync without any function name then the callbacks don't get called at all anymore!

[kbrandl]

@RXminuS thanks for reaching out about this. I'll re-open this issue and then I'm going to transfer it to the OfficeDev/office-js repository (which the members of the product team monitor for Office JS API issues like this).

[serjant]

I also encountered this issue lately and it still persists

[grangeryy]

Hi, @serjant and @RXminuS, does this issue still reproduce to you?

[grangeryy]

Close this since no more update. We can reopen if it still persists.