227480 - Various member objects are not reported when iterating through DOM nodes

Status: RESOLVED EXPIRED

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

Description

[Ken Johanson]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007

for (i in window)
  document.write(i);

Examples that are not enumerated:
-window.location (or window.document.location)
-window.location.search
-any of the event handlers (onload, onfocus)

There are quite a few more that I cant remember, so should we use a separate
dialog to report them.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.




The given URL's purpose is both educational (browsing of a given browsers
available objects/functions) and used for developer debugging of css/object
intensive pages (namespace conflicts, etc). 

i.e. seems to more completely enumerate its objects.

Comment 1

[Boris Zbarsky [:bzbarsky]]

> -any of the event handlers (onload, onfocus)

Those are not defined by default, hence do not appear.  If you actually set
them, they will appear in the list.

The "location" thing is likely due to its being replaceable...

Comment 2

[Ken Johanson]

Well, it would be neat of the event handlers did appear on the list. That would
allow us to see which objects support which events (e.g. an anchor wooudlnt have
onscroll), and listing them could also be useful for detecting event
capabilities of different browser vintages before trying to use them, for example.

i.e. does enumerate the handlers, and shows their assignment (null by defeult)

There's is actually a window.onresize handler defined in that sample already (to
aid in observing window geometry attributes), but the iterator isnt reporting
it, nor the handler it's assigned to.

Comment 3

[Boris Zbarsky [:bzbarsky]]

> e.g. an anchor wooudlnt have onscroll

Sure it would.  Why wouldn't it?

The point is that the handlers are not "null by default".  They are simply not
defined by default.

But yes, the onresize is not being shown; that seems odd...  "onresize" in
window does test true....

Comment 4

[Gervase Markham [:gerv]]

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/

Comment 5

[Gervase Markham [:gerv]]

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.