Closed Bug 268193 Opened 20 years ago Closed 19 years ago

Tab completion failed because of Exception NS_ERROR_FAILURE [nsIDOMDocumentXBL.getBindingParent chrome://chatzilla/content/handlers.js :: onTabCompleteRequest :: line 382

Categories

(Other Applications :: ChatZilla, defect)

Product:
Other Applications
Component:
ChatZilla
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: timeless, Assigned: rginda)

Details

filing this as a reminder, sorry the terminal session where this happened
decided it doesn't believe in clipboards anymore, so i can't copy the error anymore.
Product: Core → Other Applications
Looks like this can only occur if the node passed in
(document.commandDispatcher.focusedElement) doesn't have nsIContent (fails the
QI to it). Which would be a pretty bad situation, as I understand things.
There is no point us handling a [potential] case that can only occur when something fundamental in Gecko is broken. Unless this can be reproduced reliably, with an official build, this is simply not our concern.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.