From bceab2e61f159a5118e919c8d4011bbfd3ccedde Mon Sep 17 00:00:00 2001 From: "rpotts%netscape.com" Date: Sun, 8 Nov 1998 09:03:02 +0000 Subject: [PATCH] propagate abnormal stream termination correctly... git-svn-id: svn://10.0.0.236/trunk@14263 18797224-902f-48f8-a5cc-f745e15eee43 --- mozilla/gfx/src/nsImageNetContextAsync.cpp | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/mozilla/gfx/src/nsImageNetContextAsync.cpp b/mozilla/gfx/src/nsImageNetContextAsync.cpp index ffe7026e79f..ce43ed101a3 100644 --- a/mozilla/gfx/src/nsImageNetContextAsync.cpp +++ b/mozilla/gfx/src/nsImageNetContextAsync.cpp @@ -277,6 +277,10 @@ ImageConsumer::OnStopBinding(nsIURL* aURL, PRInt32 status, const nsString& aMsg) NS_RELEASE(mTimer); } + if (NS_BINDING_SUCCEEDED != status) { + mStatus = MK_INTERRUPTED; + } + // Since we're still holding on to the stream, there's still data // that needs to be read. So, pump the stream ourselves. if((mStream != nsnull) && (status == NS_BINDING_SUCCEEDED)) {