> > Delaying a bit the creation of the webview backend will hand off the value
> > null (since
> > it has not been created at qml property eval time) to the Webapps element
> and
> > prevent
> > the webapp from doing anything (even navigating).
>
> How about, in src/app/webcontainer/WebApp.qml, lazy loading the
> UnityWebApps.UnityWebApps component when webview.currentWebview becomes not
> null? Then you could do what Alberto suggests.
totally, I can go into all sorts of ways to make it work, but
I am a bit reluctant to go there & make it more convoluted, instead of fixing it the right way ..
> > Delaying a bit the creation of the webview backend will hand off the value webcontainer/ WebApp. qml, lazy loading the UnityWebApps component when webview. currentWebview becomes not
> > null (since
> > it has not been created at qml property eval time) to the Webapps element
> and
> > prevent
> > the webapp from doing anything (even navigating).
>
> How about, in src/app/
> UnityWebApps.
> null? Then you could do what Alberto suggests.
totally, I can go into all sorts of ways to make it work, but
I am a bit reluctant to go there & make it more convoluted, instead of fixing it the right way ..