Closed
Bug 350651
Opened 18 years ago
Closed 18 years ago
Favicons on trunk cause writing into Console log
Categories
(Camino Graveyard :: Location Bar & Autocomplete, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bugzilla-graveyard, Unassigned)
References
Details
Using a trunk nightly: 1) Open Console.log and filter on "NSImage". 2) Go to any site with a favicon. 3) Wonder why you just got the following line (or similar) in your console log: 2006-08-29 22:32:39.718 Camino[6879] NSImageCell's object value must be an NSImage. 4) Go to another site with a favicon. 5) Watch the line duplicate itself. Browsing on Bugzilla does not result in duplicate log lines; it seems the logging only happens the first time an icon is loaded. However, if you go to a different site and go back to the first site manually (i.e., typing it in rather than using the Back button), you get the message again, so it's not a simple issue of only occurring when the icon's not in the cache. Not a big deal, but something we should probably fix when we can. This does not appear to happen at all on branch builds or in the 1.0.x releases.
Reporter | ||
Comment 1•18 years ago
|
||
http://landfill.mozilla.org/mxr-test/mozilla/source/camino/src/browser/AutoCompleteTextField.mm#290 is the only reference I can find in our codebase to an NSImageCell. cl
See also bug 346111 comment 2 and 3 (though that may be quite different).
Comment 3•18 years ago
|
||
Are you still seeing this? I can't reproduce with the 8/31 trunk nightly (10.4.7, Intel)
Reporter | ||
Comment 4•18 years ago
|
||
Still seeing this on PPC with 8/31 trunk nightly. Going to my "bugs filed today" query (from autocomplete) triggered the console message, as it had in the past. cl
Reporter | ||
Comment 5•18 years ago
|
||
Fixed by the checkin for bug 346111. I no longer see this in trunk nightlies ever since that landed.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Comment 6•18 years ago
|
||
*** Bug 354918 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•