On Tue, Jan 29, 2013 at 09:15:20AM -0300, Alexis Menard wrote: > Apps maybe not, a Browser yes. > > Here is a given scenario : Large text field where I write my blog > post, lot of text, no auto saving of draft (very common), and then the > WebProcess becomes unresponsive. What WebKit2 will do? reloading the > page automatically? Sounds goods but you loose all what you typed in > the text field...Today Safari ask you if you want to reload the page > because the WebProcess can't respond, so you have the choice to > cancel. Actually the popup even tell you that you can loose some data > if you reload. > > In the other hand the "i could kill it" from the Apps is not a good > argument to expose this mechanism. I believe it is handled gracefully > today.
That's a good use case, I guess that exposing processDidBecomeUnresponsive and processDidBecomeResponsive signals should be enough to let the user agent prompt the user for a reload. _______________________________________________ webkit-qt mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-qt
