13352 - [BLOCKER][PP] Document Done no longer displayed for blank page

Status: VERIFIED WORKSFORME

(SeaMonkey :: General, defect, P1)

Description

[Paul Wyskoczka]

Overview Description:
In our performance testing the blank page is used as a default when obtaining
results for our launch and relaunch tests. As of todays build on all plaforms
the Document Done message is no longer being displayed at the bottom of the
browser. That makes it difficult to determine when the page has completely
loaded.

Steps to Reproduce:
1)Install the browser and make sure the nav preference is set to blank page
2)Launch the browser and wait for the page to be displayed
3)The blank page is displayed but the Document Done message is not displayed

Actual Results:
Document Done message is not displayed

Expected Results:
Document Done message is displayed


Build Date & Platform Bug Found:
9/8/99 -  All plaforms

Additional Builds and Platforms Tested On:
Windows 95, MacOs 8.6, Linux 6.0

Additional Information:
None

Comment 1

[leger]

Updating QA Contact...marking as a Blocker.  Need fixed ASAP please.

Comment 2

[don]

Radha, is this our bug?

Comment 3

[Radha on family leave (not reading bugmail)]

After the first page is done loading, do you see "Document Done" messages for
subsequent loads?

Comment 4

[Radha on family leave (not reading bugmail)]

I got the windows build made at 1:58 pm today from mozilla.org and tried it out.
I do see Document Done messages at the bottom as well as on the console. Can
someone show me what they are seeing or try out hte latest build.

Comment 5

[Radha on family leave (not reading bugmail)]

Browser AppCore is not receiving OnEndDocumentLoad() notifications from necko
for about:blank. The "Document Done" message gets printed from
nsBrowserBrowserAppCore::OnEndDocumentLoad(). Necko has to send these in. cc'ing
warren.

Comment 6

[Warren Harris]

I suspect that the input stream channel that about:blank uses isn't getting
inserted into the load group, and consequently the notification isn't given
when it's being removed.

I'm going to reassign this to Rick Potts (in case I don't get to it).

Comment 7

[rpotts (gone)]

Ever since my last round of nsLoadGroup changes the about protocol handler
stream never got added to the LoadGroup...

This didn't seem to cause any problems at the time.  Could something else have
changed that now makes this a problem?  I don't understand what's going on
here...

Comment 8

[rpotts (gone)]

I'm kicking this one back to warren since he has some changes that should fix
this problem...

Comment 9

[leger]

Putting on [Perf] radar.

Comment 10

[Warren Harris]

Should be fixed now.

Comment 11

[Paul Wyskoczka]

Verified on Windows, Mac and Linux with the 9/16 build.

Comment 12

[Paul Wyskoczka]

This is broken in today's build (9/22) on all platfoms.

Comment 13

[leger]

Clearing FIXED resolution due to reopen.

Comment 14

[Paul Wyskoczka]

This problem is in the commerical builds with the new UI and the document done
message is not displayed when loading any page.

Comment 15

[chris hofmann]

putting on my m10 radar.

Comment 16

[rpotts (gone)]

So it this problem *only* in the commercial builds?  Because I'm not seeing it
in the mozilla apprunner...

Comment 17

[Paul Wyskoczka]

The UI for the commercial build is different from the Mozilla build.

Comment 18

[Warren Harris]

If this is a commercial-build-only problem, I don't see how it's a QA blocker.
I'm moving this to m14 unless someone thinks otherwise.

Comment 19

[Warren Harris]

This is no longer an issue.

Comment 20

[Paul Wyskoczka]

I am reopening this bug because as of the 10/28/99 build the "document done" message is longer displayed in the console and
therefore we cannot run our performance tests.

Comment 21

[Paul Wyskoczka]

This is a windows related problem only.  Linux is ok and we don't use document done on the mac.  This is only a blocker for
performance not for the product in general.

Comment 22

[leger]

Clearing FIXED resolution due to reopen of this bug.

Comment 23

[Paul Wyskoczka]

Now working in build 1999-11-02-09-M11.

Comment 24

[Paul Wyskoczka]

Verified in build 1999-11-02-09-M11.