The feature to resize and drag the Callout breaks, when the mouse enters another frame, because it doesn’t get any further mouse events. In <PROJECT_NAME>, we are using an iframe to render another part of the application. When our user tries to resize (or drag) the Callout, it can lead to an unexpected state/behaviour.
I can’t see a benefit for us, that the user can resize and drag the popup, so the easiest solution would be to disable the feature. The Widget library already supports not-resizable Callouts, so, would it be possible to have a toggle from outside of the form engine library?
I am open to other solutions!
Hi @alexander-pure-wind,
i have no concrete solution in mind.
But ti have searched a little bit and maybe you could achiev a working callout on iframe based site by adding allow=“fullscreen” or legacy allowfullscreen dynamically to your iframe when callout appears. Then you have to specify an inner container which stays in the size of the iframe before fullscreen and you have to set background to transparent. Again this is just an idea no concrete solution.
For moment i will create a requirement ticket for you that requests a disable resize/drag feature for the callout that can be set from outside the form-engine.
You can find it here: A12-11983
Hey @markus-agile-fog !
I was also thinking about a workaround to use an unvisible element in the main frame that covers up the iframe to catch all the mouse events. But I don’t really understand, why you think the Fullscreen API should be used?
The problem of the workaround is to get noticed when the overlay should be rendered. If it is rendered, when the callout is opened, it would break our usability in the iframe. So, we would have to listen to the begin and the end of the resize or drag action, and this is simply not possible from outside. Plus, it feels so hacky that I don’t dare to start a requirement for that.
i just did an brief research before so it was not that detailed plan. After new research i came to conclusion fullscreen is what it says..the whole screen not the whole browser.
So please forget about 
Other idea:
how about making the iframe 100vh 100vw for that moment and display the regular content in an size-fixed inner box (if you are able to calc size and position)? Or will the callout stay for a while and will not disappear on loss of focus?
When implementing a workaround, the question is not how to manipulate the DOM to keep the behaviour of the resize & dnd feature. The issue is where the manipulating handler could be integrated.
…for that moment…
It is quite hard to determine the right moment and currently not possible to get notified when the callout opens/closes or when the user starts to drag/resize the callout. And even if there were any intern actions, I wouldn’t want to rely on them from our projects perspective. Nor would I raise a requirement to supply an API to attach a custom handler, because it would lead to a hacky workaround. 