In fact, it is not a Webix bug - sorry for misguiding you.
However, Webix catches mouse events with one document object, while the iframe contains another - it is the expected behaviour.
As a solution, you need to track the mousemoveevent in the nested iframe as follows:
Not a practical solution when dealing with same-origin policy iframes. Have a case that the iframe has Same-Origin protection and is not possible to get mousemove event from it.
Comments
Hello!
Thank you for the issue. We will fix it
Hi. Does it fixed?
In fact, it is not a Webix bug - sorry for misguiding you.
However, Webix catches mouse events with one
document
object, while the iframe contains another - it is the expected behaviour.As a solution, you need to track the
mousemove
event in the nested iframe as follows:https://snippet.webix.com/bmyr8jgo
Thanks.
Not a practical solution when dealing with same-origin policy iframes. Have a case that the iframe has Same-Origin protection and is not possible to get mousemove event from it.
Hello there. Does it fixed?