Closed Bug 6729 Opened 26 years ago Closed 26 years ago

Messenger start page should be loaded from onload= handler.

Categories

(SeaMonkey :: MailNews: Message Display, defect, P2)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: locka, Assigned: alecf)

References

()

Details

The messenger window loads the Netscape Mail "welcome" page into the bottom-right pane (see URL). The messenger menu does not appear until this URL has completely loaded.
Assignee: phil → alecf
Reassigning to alecf, and cc'ing rickg. Is this fixable using finer-grained interruptible reflow, or do we just have to live with this?
I think the same thing happens in the browser, but I could be wrong. I think someone has just noticed some consistency about what gets loaded first. Adding Hyatt (since this is chrome layout) to the CC list in case he wants to add any comments.
Can someone explain this bug in more detail? I'm not understanding the problem.
I think someone is just noting the order in which the chrome is layed out - noting that the menu does not appear until the rest of the page (in this case the messenger start page) finishes laying out.
Status: NEW → ASSIGNED
Summary: Messenger menu does not appear until Netscape page has loaded → Messenger start page should be loaded from onload= handler.
From Dave: Make sure you are NOT specifying the initial source frame to load in your content area in the XUL. You should load the source frame in the chrome's onload handler instead. In this way you can make sure that the onload handler for the chrome fires before content has been loaded (rather than after, which is what will happen if you explicitly specify the source right there in the XUL). --- Ah, good to know. Updating bug summary. I switch over from using the IFRAME's src= method to using the onload= handler.
Actually, it might be smart of us (XpToolkit) to make this delay happen automatically for any areas labeled as "content", i.e., sandboxed content areas. Then you could go ahead and specify the source, and we would handle delaying its load.
I suggest applying the workaround. After you've done this, I'd reassign this bug to danm, and he'll handle the automatic delaying so that (in the future) this will work properly without you having to think about it.
Priority: P3 → P2
Target Milestone: M7
QA Contact: lchiang → pmock
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
finally fixed - it loads faster now I think.
Status: RESOLVED → VERIFIED
Verified in the June 8 Seamonkey build on Win32 (1999-06-08-08-m7), PPC (1999-06- 08-08-m7), and Linux (1999-06-08-08-m7). In today builds, the Messenger menu appears before the start page. To test, I ran yesterday builds (1999060708-m7) to see that the Messenger menu appeared after the start page finishes loading.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.