Navigation after top-level resource blocked sometimes results in unresponsive web view
aperezdc opened this issue · 0 comments
aperezdc commented
[…] the only issue remaining is that a web view may stop being updated in the following situation: a page was successfully loaded, then a new load is started which results in a content filter blocking the top-level resource, and finally navigation goes to another security origin (and the top-level resource is not blocked).
Both @psaavedra and myself reckon that the above corner case is a rare situation, and that is worth it to have this merged it and putting out a 1.9.91 release which we know will have the crashes tackled by this PR gone—after that we will continue working top iron out the remaining issue.
Originally posted by @aperezdc in #153 (comment)