WebEngineView freezing
-
If I hide the main application window the WebEngineView freezes, doesn't update the page and stops accepting any mouse hovering actions while javascript still can be ran in the background and mouse clicks can interact with the page mostly.
It only freezes if the window was shown and the window.visible = false was set and any function which marks it as visible false, if the window start with visible = false and then it's set true it works normaly until the first cycle of hidden / visible.
I have tested this on Ubuntu with Unity 7 and a clean Xubuntu installation, both of them experiencing the same issue.
Any ideeas on forcing the view to "restart"? I have looked into bug reports and the issue is similar to a supposedly fixed bug.Reloading the page doesn't solve anything, neither setting focus to the view.
I am using Qt 5.6.2, 64 bit version(online installer version). -
Hi
Can you reproduce this in a small sample?
I mean, will et also freeze with default GUI app and a WebEngineView.
It sounds a bit strange so would be good to test without much code. -
Hi
Can you reproduce this in a small sample?
I mean, will et also freeze with default GUI app and a WebEngineView.
It sounds a bit strange so would be good to test without much code.@mrjj said in WebEngineView freezing:
Hi
Can you reproduce this in a small sample?
I mean, will et also freeze with default GUI app and a WebEngineView.
It sounds a bit strange so would be good to test without much code.Sorry I haven't responded, I haven't had any time to make an example, will try this evening to make one and make it available.
-
Hi
Can you reproduce this in a small sample?
I mean, will et also freeze with default GUI app and a WebEngineView.
It sounds a bit strange so would be good to test without much code.@mrjj
Hi and sorry for the long time it took to post, I really didn't had time to create a working simple example until today and after I finished making it I noticed I couldn't replicate the issue.
After some testing and a shower, it struck me, I forgotten I was also calling window.close() from the html tag and it was that which created this whole mess.
To be fair I am not sure why this even is a problem, but at least I know now that I do not have to reset the source of the WebEngineView in order to restore to UI's functionality.
To explain a bit more, when I was hitting "X" button from inside the UI(frameless window), the button had onClick="window.close();" attribute on html tag and I was also calling window.title = "close" from inside javascript code, I was using the window.title method to check for close request and totally forgot about the close request from inside html code.
So using onClick="window.close();" to close to tray froze the WebEngineView. -
@mrjj
Hi and sorry for the long time it took to post, I really didn't had time to create a working simple example until today and after I finished making it I noticed I couldn't replicate the issue.
After some testing and a shower, it struck me, I forgotten I was also calling window.close() from the html tag and it was that which created this whole mess.
To be fair I am not sure why this even is a problem, but at least I know now that I do not have to reset the source of the WebEngineView in order to restore to UI's functionality.
To explain a bit more, when I was hitting "X" button from inside the UI(frameless window), the button had onClick="window.close();" attribute on html tag and I was also calling window.title = "close" from inside javascript code, I was using the window.title method to check for close request and totally forgot about the close request from inside html code.
So using onClick="window.close();" to close to tray froze the WebEngineView.
