197718 - javascript console error: "Error: this.mMissedlconCache has no properties"

Status: RESOLVED EXPIRED

(SeaMonkey :: Tabbed Browser, defect)

Description

[KCastleman]

User-Agent:       Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.3) Gecko/20030312

Writing little javascript programs on my desktop, the Javascript Console shows
this error "Error: this.mMissedlconCache has no properties" for every javascript
page I open. 
I am using Windows Me.
Additional info:
Source File:
chrome://global/content/bindings/tabbrowser.xml#tabbrowser.addToMissedlconCache()
Source of:
jar:resource:///chrome/toolkit.jar!/content/global/bindings/tabbrowser.xml#abbrowser.addToMissedlconCache()

Reproducible: Always

Steps to Reproduce:
1. write a little javascript program like "javascript: var now = new Date();"
2. run the program on a simple html page
3. check the JavaScript Console for error messages.

Actual Results:  
For every instance of javascript, an error message appears in the JavaScript
Console.

Expected Results:  
No error messages for javascript that has no errors.

A similar problem was present in Mozilla 1.3b, so that I eventually had to
uninstall it and go back to Mozilla 1.3a. It made the JavaScript Console Mozilla
1.3b unusable.

Comment 1

[KCastleman]

Further, if I try to use "javascript: window.close" I get the following message:

"Scripts may not close windows that were not opened by script."

This was never true in the past and makes my work hard, since I write many
javascript windows with the close option. I hate to have to write a window.open
script just to make them work while I test them.

Comment 2

[John Morrison]

this is fixed, I think, in current builds. If not, it's a duplicate anyways.

The script bug is an intentional security restriction. You can set a pref
in your profile to defeat this restriction if you so choose. 
  user_pref("dom.allow_scripts_to_close_windows", true);

*** This bug has been marked as a duplicate of 121234 ***

Comment 3

[Alfonso Martinez]

*** Bug 199285 has been marked as a duplicate of this bug. ***

Comment 4

[KCastleman]

User-Agent:       Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.3)
Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.3)
Gecko/20030312

I get the following error in the JavaScript console if I click on a link to a
web page on line, or open a web file on my desktop off line: (NOT using tabbed
browsing)

Error: this.mMissedIconCache has no properties
Source File:
chrome://global/content/bindings/tabbrowser.xml#tabbrowser.addToMissedIconCache()
Line: 2

Reproducible: Always

Steps to Reproduce:
1. After starting Mozilla on line, go to Mozilla.org home page by clicking icon
in browser's right top. (Get error #1 in JavaScript Console)
2. Click on file bug in Mozilla.org left nav bar (Get error #2 in JavaScript
Console.)
3. Click on another link (get error #3 in JavaScript Console.)

Actual Results:  
Each click of web page link puts new error line in JavaScript console:

Error: this.mMissedIconCache has no properties
Source File:
chrome://global/content/bindings/tabbrowser.xml#tabbrowser.addToMissedIconCache()
Line: 2

Expected Results:  
No errors in JavaScript Console for clicking a link. The error refers to tabbed
browsing but the errors occur without tabbed browsing

This reduces usefulness of JavaScript console, as it is always packed full of
error lines.

I am using Window Me and Mozilla 1.3 Final.

Comment 5

[KCastleman]

Additionally, I tried several Mozilla 1.4a builds and the error is still there. 

Comment 6

[Frank Wein [:mcsmurf]]

Reporter: Is this still a problem with a current Mozilla build?

Comment 7

[Gervase Markham [:gerv]]

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/

Comment 8

[Gervase Markham [:gerv]]

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.