Open
Bug 289450
Opened 20 years ago
Updated 16 years ago
Error ``tipElement has no properties'' [xs] in file ``chrome://navigator/content/browser.js''
Categories
(SeaMonkey :: UI Design, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: timeless, Unassigned)
Details
stepping using venkman resulted in the following very amusing error:
Continuing from error handler.
#0: function get_accessible() in <chrome://global/content/bindings/popup.xml>
line 25
025: var accService = Components.classes
["@mozilla.org/accessibilityService;1"].getService
(Components.interfaces.nsIAccessibilityService);
#0: function get_accessible() in <chrome://global/content/bindings/popup.xml>
line 26
026: if (this.localName == "popup" || this.localName == "menupopup")
#0: function get_accessible() in <chrome://global/content/bindings/popup.xml>
line 28
028: else if (this.localName == "tooltip")
#0: function get_accessible() in <chrome://global/content/bindings/popup.xml>
line 29
029: return accService.createXULTooltipAccessible(this);
#0: function onpopupshowing(event=MouseEvent:{0}) in
<chrome://navigator/content/navigator.xul> line 1
#0: function FillInHTMLTooltip(tipElement=null:null) in
<chrome://navigator/content/browser.js> line 360
360: var retVal = false;
#0: function FillInHTMLTooltip(tipElement=null:null) in
<chrome://navigator/content/browser.js> line 361
361: if (tipElement.namespaceURI
== "http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul")
Error ``tipElement has no properties'' [xs] in file
``chrome://navigator/content/browser.js'', line 361, character 0.
Stopped for error handler.
#0: function FillInHTMLTooltip(tipElement=null:null) in
<chrome://navigator/content/browser.js> line 361
359: {
360: var retVal = false;
361: if (tipElement.namespaceURI
== "http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul")
362: return retVal;
363:
0005: document.tooltipNode
$[0] = [null] null
#0: function FillInHTMLTooltip(tipElement=null:null) in
<chrome://navigator/content/browser.js> line 361
#1: function onpopupshowing(event=MouseEvent:{0}) in
<chrome://navigator/content/navigator.xul> line 1
while the code has moved a bit since 1.8a5, the code is still functionally the
same and can still break the same way :)
Comment 1•17 years ago
|
||
Which product/version are you using ? Can you reproduce with SeaMonkey v1.1.9 ? Can you reproduce with SeaMonkey v2.0a1pre ?
Assignee: guifeatures → nobody
QA Contact: guifeatures
You need to log in
before you can comment on or make changes to this bug.
Description
•