Closed Bug 27775 Opened 25 years ago Closed 25 years ago

cannot load oracle site (due to javascript error?)

Categories

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

x86
Other
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: buster, Assigned: vidur)

References

()

Details

(Whiteboard: [PDT+] Have fix, waiting for review)

using mozilla debug build on windows, pulled 10:00 am this morning
try to load http://www.oracle.com
immediately get a "done" and a blank screen.
this error prints to the console:

JavaScript Error: TypeError: redeclaration of const content
URL: http://www.oracle.com/
Severity: normal → major
Looks like the included JS isn't getting executed.  It only sniffs for NS 4, but
changing that didn't produce better results.
The script is executing. The error occurs because of the newly defined  
"content" property on the Window interface (see 
http://lxr.mozilla.org/seamonkey/source/dom/public/idl/base/Window.idl#12). The 
property was defined by danm and has something to do with dialogs from what I 
can tell. Dan, you're going to have to change the name of the property so we 
don't have conflicts - a mixed case name might help prevent conflicts in the 
future. 

Marking beta1 since this is a fairly major site.
Assignee: vidur → danm
Keywords: beta1
Putting on PDT+ radar for beta1.
Whiteboard: [PDT+]
Target Milestone: M14
This is a duplicate of bug #26226
*** Bug 26226 has been marked as a duplicate of this bug. ***
Whiteboard: [PDT+] → [PDT+] cheap workaround to be backed out someday by 2/21
Vidur plans a much more awesome and general solution than my intended one-
property specialization, so he gets to hold onto this one.
Assignee: danm → vidur
Whiteboard: [PDT+] cheap workaround to be backed out someday by 2/21 → [PDT+]
Whiteboard: [PDT+] → [PDT+] Have fix, waiting for review
Fixed on 2/22/2000. Marked window.sidebar, content and controllers with the new 
keyword "replaceable".
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.