Samael Wang 6d2553f61f Bug 1402689 - Clear tab's "busy" attribute on LOCATION_CHANGE_ERROR_PAGE. r=dao ...

If the busy attribute was not set by (STATE_IS_NETWORK & STATE_START), and the
loading results in an error, it's possible that the busy flag never gets
cleared. In this case we can clear it when receiving location change with
LOCATION_CHANGE_ERROR_PAGE.

When digging into this bug I found nsBrowserStatusFilter::mFinishedRequests
and mTotalRequests counters can be incorrect on parent side since we've applied
the filter on both child and parent processes. This hasn't seem to be causing
a bug yet but it's potentially problematic, so adding a warning in
nsBrowserStatusFilter.

MozReview-Commit-ID: H25R60ozGtM

--HG--
extra : rebase_source : 3b6f9b6c974e65d540fdae495017dd3b7fffdbb6

2017-10-30 17:30:56 +08:00

..

content

Bug 1402689 - Clear tab's "busy" attribute on LOCATION_CHANGE_ERROR_PAGE. r=dao

2017-10-30 17:30:56 +08:00

jar.mn

…

moz.build

…