Throbber starts when using document.writeln




17 years ago
17 years ago


(Reporter: mkaply, Assigned: jst)



Firefox Tracking Flags

(Not tracked)





17 years ago
Go to URL.

Click on either left or right click me.

Note that throbber continues and there is an hourglass over middle frame.
That would be because you never call document.close()....  we keep waiting for
more input.  This is correct behavior, imo.
Assignee: asa → jst
Component: Browser-General → DOM Level 0
QA Contact: doronr → amar
In particular, try clicking left, then right.  The throbber behavior should make
more sense then...

Comment 3

17 years ago
So this is yet another "Works on IE, doesn't work on Mozilla"

Man that list is getting long.

Comment 4

17 years ago
OK, is there any way to add text to a frame rather than replace it.

The behvior that the person who gave this to me was expecting was that you 
could have a frame that did logging where you just keep document.writelning to 
it, and it shows a new entry.

With Mozilla, it does not appear possible to do that. If you document.close(), 
you lose the previous data.
The way to add text is the following:

If you don't call .open() then writeln() seems to do that for you.  Then while
the document is open one can keep appending data, but that also means that the
document is not done loading (obviously -- data is still coming in) so the
throbber is active.  Once you call close() the document is done loading so the
throbber goes inactive, but at this point open() will naturally wipe the
document clean (that's what open() does).

How does the IE behavior differ from ours?  Does it not animate the throbber at
all for writeln()?  Does it animate but stop it even though the document is not
closed (hence still loading)?

Comment 6

17 years ago
IE doesn't ever animate the throbber at all no matter what you are doing.

This means that with IE, you can put text in the middle from both the left and 
the right frame easily.

On Mozilla, you cannot because the throbber continues until you call 
document.close, and once you have called document.close, the next 
document.writeln will replace the content.

I've uploaded a better testcase that allows more control.
So the real "bug" here is that we start the throbber at all in these
circumstances, no?  Why is the throbber running a big problem in these

Note that IE's approach does not allow you to tell whether anything is happening
at all (eg if I add a slow-loading image via document.writeln() you may not
realize that you should wait for it because the throbber is inactive).

Not arguing for one behavior or the other, just suggesting things that should be
Summary: Throbber never stops when using document.writeln → Throbber starts when using document.writeln

Comment 8

17 years ago
Actually it does animate on IE if you put a slow image in because that creates a 
network connection.

I've added this to the testcase.

Comment 9

17 years ago

describes the throbber behavior among other stuff

Comment 10

17 years ago
I'm sure this is a dup of one of my bugs, but I can't find the bug...

Comment 11

17 years ago
Dup of bug 81980 " without doc.close() does not stop
throbber". Please reopen if you don't agree.

*** This bug has been marked as a duplicate of 81980 ***
Last Resolved: 17 years ago
Resolution: --- → DUPLICATE

Comment 12

17 years ago
verified that this is a dupe of bug # 81980
You need to log in before you can comment on or make changes to this bug.