Ulrich-Matthias Schäfer
Ulrich-Matthias Schäfer
There is a version selector at the top of the docs page. The docs currently show 3.0 by default (which is also a bug). You can check against the 3.1...
That's exactly how I handled it. Thanks for the confirmation!
@nouvist also solved another problem with its solution: the transpilation to es5 which broke my code since it introduced helper functions that are not available in the function itself. Thanks...
What you probably want to try is `ev,stopImmediatePropagation()`. This will stop any other listener after the current one to be executed. However, I am not sure in which order listeners...
Always bind it before and check for a flag you set in videoConferenceJoined. If it is set, you call `ev.stopImmedatePropagation()`
The correct solution would be to be able to completely disable jitsis automatic unload bindings so you can do it manually. That way you would have full control
The same problem people are having with beforeUnload can be applied to the unload event. So making jitsi not binding to any event and giving us the functions that need...
Don't ask me. The error is coming from jitsi. Maybe, you are overwriting the old room with the new one and the event is handled by the new room instead...
@garyhuntddn you could add the typings as `@typings/lib-jitsi-meet` but that would somehow mean that it's independent of this project. The other possibility would be to generate a d.ts file automatically...
Disable `draggable` when you start resizing and enable it again when you are done. Thats the simplest solution here I guess