Gervase Markham [:gerv] Reporter
	Description • 24 years ago

[ This bug is one of the recommendations in the W3C's "Common User Agent 
Problems" document, URL above. One bug has been filed on each recommendation, 
for deciding whether we do it and, if not, whether we should. ]

1.7 Warn users about incomplete documents and transfers.

     Rendering an incomplete document as though it were complete is very
     likely to confuse users. Part of the document is missing, hence some
     anchors might not be present, possibly breaking some links. The user
     agent should notify the user that the document is incomplete.

     The HTTP/1.1 specification describes this behavior for caches at the
     protocol level. Partial responses should also be made obvious to the
     user with a warning.

	Matthew T (active 1999-2002)
	Comment 1 • 24 years ago

4.x writes something like `</>Transfer interrupted!' to the end of the document, 
but this doesn't work in the (frequent) case that the loading is stopped in the 
middle of a TABLE, since the text never appears.

Appropriate behavior would be to draw a box along the bottom of the canvas, 
containing the `note' icon (e.g. a face with a speech bubble on Mac OS, or an `i' 
in a speech bubble on Windows), with text explaining that the page was not 
complete and that this might be fixed by hitting Reload.

	Gervase Markham [:gerv] Reporter
	Comment 2 • 24 years ago

We do need a "transfer interrupted" message, which we don't have at the moment. 
Nominating for mozilla0.9.

Gerv

	benc
	Comment 3 • 23 years ago

mass move, v2.
qa to me.

	Doug Turner (:dougt)
	Comment 4 • 22 years ago

moving neeti's futured bugs for triaging.

	Patrick McManus [:mcmanus]
	Comment 5 • 9 years ago

we learned from the downloader that webcompat says the protocol signals of incomplete are not accurate