Closed Bug 286105 Opened 20 years ago Closed 20 years ago

Error: XPCNativeWrapper is not defined

Categories

(SeaMonkey :: General, defect)

1.7 Branch
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 267378

People

(Reporter: P.Taylor, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217

Mozilla 1.7.5 is configured with "Javascript:" as home page.  The browser
component is launched.  The navigator component is launched using Ctrl-2.
The word "Mozilla" in the text "Welcome to Mozilla Mail & Newsgroups"
is clicked, and the error reported above is diagnosed in the JavaScript
console.  The exact error message is :

        Error: XPCNativeWrapper is not defined
        Source File: chrome://communicator/content/contentAreaClick.js
        Line: 153

Reproducible: Always

Steps to Reproduce:
1. Configure Mozilla 1.7.5 to have "Javascript:" as home page
2. Launch the browser component
3. Launch the messenger component using Ctrl-2
4. Click on the word "Mozilla" in the text "Welcome to Mozilla Mail
   & Newsgroups" that appears in the message pane


Actual Results:  
The JavaScript console reports 

        Error: XPCNativeWrapper is not defined
        Source File: chrome://communicator/content/contentAreaClick.js
        Line: 153

Expected Results:  
Followed the link without causing the JS error.
Looks like a duplicate of Bug 267378.

Could you please try it with a 1.7.6 build from
http://ftp.eu.mozilla.org/pub/mozilla.org/mozilla/nightly/latest-1.7/ to see if
it is fixed? If it works then it is a duplicate.
Version: unspecified → 1.7 Branch
from reporter:

Looks good, although the new version (1.7.6) makes it
difficult to ascertain exactly which version it is :
"Help/about" describes itself only as Mozilla,
and it is only by hovering over the "Mozilla" link that
one can see "http://www.mozilla.org/releases/mozilla1.7.6". 

That works for me. This would be a different bug anyway.

*** This bug has been marked as a duplicate of 267378 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.