ChatZilla:User Mistakes: Difference between revisions
No edit summary |
|||
| Line 8: | Line 8: | ||
==Bad click prefs== | ==Bad click prefs== | ||
If ''messages.click'' is set to a non-existant command, ChatZilla's handling of links fails and the events pass to a default handler that doesn't understand ''x-cz-command:''. - [[User:Rdm|Robert Marshall]] 09:34, 6 Nov 2005 (PST) | If ''messages.click'' is set to a non-existant command, ChatZilla's handling of links fails and the events pass to a default handler that doesn't understand ''x-cz-command:''. - [[User:Rdm|Robert Marshall]] 09:34, 6 Nov 2005 (PST) | ||
=== Fix === | |||
I think the right solution here is to change onMessageViewClick in handlers.js to never let the click proceed normally, and just display an error if the command didn't work. | |||
--[[User:JamesRoss|JamesRoss]] 09:41, 6 Nov 2005 (PST) | |||
Revision as of 17:41, 6 November 2005
User Mistakes Made in ChatZilla
This page is for listing all the common (and some not-so-common) problems normal users encounter, especially those which could be handled either silently or otherwise by ChatZilla.
Malformed aliases
Unlike with the /alias command, when using the pref panel, aliases must be entered with an = sign between the alias name and the command(s). The /alias command currently can't edit malformed aliases, or create new aliases when a malformed one exists. - Robert Marshall 09:34, 6 Nov 2005 (PST)
Bad click prefs
If messages.click is set to a non-existant command, ChatZilla's handling of links fails and the events pass to a default handler that doesn't understand x-cz-command:. - Robert Marshall 09:34, 6 Nov 2005 (PST)
Fix
I think the right solution here is to change onMessageViewClick in handlers.js to never let the click proceed normally, and just display an error if the command didn't work. --JamesRoss 09:41, 6 Nov 2005 (PST)