Closed Bug 60486 Opened 24 years ago Closed 23 years ago

onLoad doesn't work when there is an anchors in the URL

Categories

(Core :: DOM: Core & HTML, defect, P3)

defect

Tracking

()

RESOLVED FIXED
mozilla0.9

People

(Reporter: ajm194, Assigned: nisheeth_mozilla)

References

()

Details

(Keywords: dom0)

From Bugzilla Helper:
User-Agent: Mozilla/4.7 [en] (Win95; I)
BuildID:    2000111620

The onLoad handler isn't triggered when a HTML page is first loaded if it's URL 
has an anchor extension on the end to go to a selected point in the document

Reproducible: Always
Steps to Reproduce:
1. Goto http://booth.lse.ac.uk/test/browsers/mozilla_onload_bug.html
2. Click on first link and see that nothing happens when the page loads
3. Go back
4. Click on the link again, it still doesn't work
5. Go back
6. Click on the second link and it does work but that is because the URL doesn't 
use an anchor

Actual Results:  It doesn't execute the defined onLoad handler

Expected Results:  Displayed an alert box
I see this on linux trunk 2000-11-17-08

Confirming, OS->All
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 95 → All
Looks like this is related to the dummy channel used by the pres shell to
prevent early fireing of the onload event. If I go to the page using the link
with the # the page loads and mozilla scrolls to the right place but the onload
doesn't fire but if I manually scroll the page the onload event fires!!!

Over to Nisheeth who wrote the dummy channel stuff in the pres shell.
Assignee: jst → nisheeth
Hardware: PC → All
Oh, I just noticed that the same thing happens when I submit changes to a
bugzilla bug, the result of the submit loads and the throbber just keeps going
and going and going, if I scroll the page the throbber stopps, whaky...
Keywords: dom0
Target Milestone: --- → mozilla0.9.1
Bringing in load bugs that seem to be related to the dummy layout channel code 
into the 0.9 milestone.
Target Milestone: mozilla0.9.1 → mozilla0.9
waterson's fix to bug 53956 has fixed this bug too.  Marking as such.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.