User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2 Build Identifier: Firefox/0.9.2 for example: <img id=next src="image.gif" onClick="next()"> - would not work, until we change ID to something else: <img id=any_other_ID src="image.gif" onClick="next()"> Reproducible: Always Steps to Reproduce:
id="next" i/o id=next might help (W3C)
Assignee: firefox → general
Component: General → DOM
Product: Firefox → Browser
QA Contact: firefox.general → ian
Version: unspecified → Trunk
The problem is that the "next" identifier is resolved up the scope chain -- first in the scope of the node itself, then document scope, and finally window scope. Now window.next is a function, but document.next is a DOM node (for DOM0 compat reasons, looks like). So the "next" identifier is resolved to a DOM node, and when you try to treat it as a function you get an exception thrown. Past removing the document.id thing, there's nothing to be done here -- the rest of the behavior is absolutely correct. Using window.next() would work to specify that the "next" in the window scope is wanted...
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
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.