Closed Bug 297993 Opened 20 years ago Closed 19 years ago

Impossible to set event handlers using only document.body

Categories

(Core :: DOM: Events, defect)

Product:
Core
Component:
DOM: Events
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED EXPIRED

People

(Reporter: deadpool42, Unassigned)

Details

Attachments

(1 file)

The body.onclick event doesn't get assigned until you click the button.
468 bytes, text/html
Details 
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

Using either "document.body.event = function;" or "document.event = function;"
anywhere in the page fails without producing any kind of error in the Javascript
Console.  This does work if you set it after the entire page has loaded (<body
onload="document.body.event = function;">).

Reproducible: Always

Steps to Reproduce:
1.  Try to set a handler function for the body without using an attribute in the
tag itself.

Actual Results:  
Nothing.  The function is never called.

Expected Results:  
Either the handler should be assigned normally or a warning should be generated.
The onclick handler in the testcase works for me without pressing the button.
Note that <body> does not span the whole window but only in a rectangle with the
height of the button, i.e. you have to click to the right of the button to
invoke the onclick handler.

I am using Deer Park Alpha 1.
(In reply to comment #2)
I didn't know that, so I guess I should have used the event that was originally
causing me trouble: onload.  I can't seem to set a handler for
document.body.onload no matter where the statement is (unless it's in the onload
attribute of the <body>).
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: