Closed Bug 379794 Opened 18 years ago Closed 18 years ago

document.tooltipNode.target has no properties in chrome://navigator/content/nsBrowserStatusHandler.js at Line: 281

Categories

(SeaMonkey :: UI Design, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bugzilla, Unassigned)

Details

I have seen this error Error: document.tooltipNode.target has no properties Source File: chrome://navigator/content/nsBrowserStatusHandler.js Line: 281 reported in the Error console several times in the last 10 nightly trunk builds. I've searched for duplicates and couldn't find any (closest I found was bug 241125). I have a few old addons extensions installed. I don't know if these have an impact or are responsible for creating such error; for now, I don't think they have are involved. Steps to reproduce: Unidentified. Unknown for now. I have not tried to use a fresh new profile. Reproducible Not always. Intermittent occurences. Seamonkey 1.5a rv:1.9a5pre build 2007050408 under XP Pro SP2. Setting initial state to UNCONFIRMED until I can find more solid info on this bug.
Here's the relevant block of code coming from jar:resource:///chrome/comm.jar!/content/navigator/nsBrowserStatusHandler.js if (document.tooltipNode) { // Optimise for the common case if (aWebProgress.DOMWindow == content) { document.getElementById("aHTMLTooltip").hidePopup(); document.tooltipNode = null; } else { for (var tooltipWindow = document.tooltipNode.target.ownerDocument.defaultView; tooltipWindow != tooltipWindow.parent; tooltipWindow = tooltipWindow.parent) { if (tooltipWindow == aWebProgress.DOMWindow) { document.getElementById("aHTMLTooltip").hidePopup(); document.tooltipNode = null; break; } } } } where document.tooltipNode.target.ownerDocument.defaultView; is Line 281
I can not find more to support this bug. I'm going to resolve it as WORKSFORME.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Component: XP Apps: GUI Features → UI Design
You need to log in before you can comment on or make changes to this bug.