From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.5+) Gecko/20011015 BuildID: 2001101503 When I access this page I get: Error: uncaught exception: [Exception... "Not enough arguments [nsIDOMWindowInternal.scroll]" nsresult: "0x80570001 (NS_ERROR_XPC_NOT_ENOUGH_ARGS)" location: "JS frame :: <unknown filename> :: onload :: line 0" data: no] in the JS console. Reproducible: Always Steps to Reproduce: 1. Access http://www.nexgo.de/dbd/priv/adressen/adr_uebersicht.html 2. 3. Actual Results: The error shown above occurs and the pulldown menu in the page is non-functional. Expected Results: The pulldown menu should be useable. Unfortunately you need an account to access this page. You can either create a temporary one or I'll change the password on mine for a while.
Assignee: rogerl → jst
QA Contact: pschwartau → amar
This is the only line I could find browsing the different files: <body background="/c/images/bg_home_big.jpg" leftmargin="0" topmargin="0" marginwidth="0" marginheight="0" onLoad="preload();scroll('scroller');">
setting status to NEW. Should scroll() be replaceable? Sounds like the page may be defining its own....
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 2000 → All
Hardware: PC → All
|scroll| is replaceable, defining your own scroll function works just fine.
|scroll| doesn't seem to be replaceable to me. It isn't in the list of JSStrings in nsDOMClassInfo and nsIDOMWindowInternal doesn't document it as being replaceable.
jst, any idea? like I said scroll doesn't sound replaceable to me
Fabian, |scroll| is a method, not a property, thus it's replaceable by nature (only properties with getter and setter methods have issues with "replaceability").
WORKSFORME, no error on the page when loaded in mozilla, but I do see a JS error when I load the page in IE. This site needs to fix their issues, but I don't see a problem in mozilla on this page (except for some potential layout bugs, but those are unrelated to this bug).
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.