Closed
Bug 74306
Opened 24 years ago
Closed 23 years ago
uncaught exception in cookieContextOverlay.xul
Categories
(Core :: Networking: Cookies, defect)
Tracking
()
VERIFIED
WORKSFORME
Future
People
(Reporter: bugzilla, Assigned: morse)
Details
Go to a website, right click on a image and select "View Image" and you get:
JavaScript error:
line 0: uncaught exception: [Exception... "Could not convert JavaScript
argument (NULL value can not be used for a C++ reference type) arg 0
[nsISupports.QueryInterface]" nsresult: "0x8057000b
(NS_ERROR_XPC_BAD_CONVERT_JS_NULL_REF)" location: "JS frame ::
chrome://cookie/content/cookieContextOverlay.xul :: anonymous
:: line 58" data: no]
Assignee | ||
Comment 1•24 years ago
|
||
This is working fine for me, using the image on www.mozilla.org. Can you give
me the URL of the page you are displaying and which image on the page you are
attempting to view.
I'm running on winnt instead of 2000 but that shouldn't make any difference.
Do you have a recent build -- i.e., later than March 28 so that it includes the
extensive changes that I made to the cookie module?
Reporter | ||
Comment 2•24 years ago
|
||
I just reproduced this with build 2001033120:
1) load "about:"
2) rightclick on the mozilla star image and you get the exception...
Assignee | ||
Comment 3•24 years ago
|
||
That test works fine for me -- no exception generated. tever, can you
reproduce?
Reporter | ||
Comment 4•24 years ago
|
||
Just rightclicking on *any* image on *any* webpage produces the exception for
me:
build 2001033120 on win2k
Comment 5•24 years ago
|
||
I see this in the console on linux (build 040216):
JavaScript error:
line 0: uncaught exception: [Exception... "Could not convert JavaScript
argument (NULL value can not be used for a C++ reference type) arg 0
[nsISupports.QueryInterface]" nsresult: "0x8057000b
(NS_ERROR_XPC_BAD_CONVERT_JS_NULL_REF)" location: "JS frame ::
chrome://cookie/content/cookieContextOverlay.xul :: anonymous :: line 58" data: no]
Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.0
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla1.0 → mozilla0.9.3
Assignee | ||
Comment 6•23 years ago
|
||
I'm still not able to reproduce. So I'm going to mark the "future" which means
that I'm not going to get to it -- ever. If someone is able to reproduce this
and wants to post a patch, please do so and reset the target milestone to blank.
Target Milestone: mozilla0.9.3 → Future
Reporter | ||
Comment 7•23 years ago
|
||
20020117
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Comment 8•23 years ago
|
||
Just to clarify comment #7 above. At the same time that gemal made this
comment, he also closed out the bug report as "works-for-me". So I presume that
he was saying that it no longer occured for him with the 20020117 build, rather
than saying that he is still seeing the problem with that build. (Without
realizing that he closed out the report at the same time that the comment was
made, one would probably assume the latter.)
You need to log in
before you can comment on or make changes to this bug.
Description
•