Closed Bug 261150 Opened 21 years ago Closed 21 years ago

error switching motifs

Categories

(Other Applications Graveyard :: ChatZilla, defect)

PowerPC
macOS
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 265573

People

(Reporter: micklweiss, Assigned: rginda)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a3) Gecko/20040831 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a3) Gecko/20040831 when switching motifs in Chatzilla: Internal error dispatching command “sync-motif”. [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMXULElement.boxObject]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://global/content/bindings/browser.xml :: get_docShell :: line 0" data: no] It works though. Reproducible: Always Steps to Reproduce: 1. switch motifs via /motif path_to_motif.css 2. the error appears 3. Actual Results: the error appears: Internal error dispatching command “sync-motif”. [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMXULElement.boxObject]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://global/content/bindings/browser.xml :: get_docShell :: line 0" data: no] Expected Results: nothing should print out Its not a big problem, but it seems to make it take longer to switch motifs.
I'm also seeing this bug. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040830 Firefox/0.9.1+ Chatzilla 0.9.64g, Windows XP The error message always appear, regardless whether the motif is being switched via menu (View -> Color Scheme), via preferences, or via /motif.
Hmm, intesting. I couldn't reproduce this on Windows with a nightly Mozilla build a few days ago. Mick Weiss, was the error actually on a nightly Mozilla build (as your UA string suggests)? Anyone up for running the JavaScript Debugger, setting it to stop on exceptions, and getting a JS stack for this? Based on the fact it's still switching, I can only think it is the line here: http://lxr.mozilla.org/mozilla/source/extensions/irc/xul/content/output-window.js#250 Can anyone confirm if the message "Using <%S> as default motif." (with %S replaced) is being displayed, or anything similar?
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr; rv:1.7) Gecko/20040803 Firefox/0.9.3 Build Identifier : Mozilla/5.0 (Windows; U; Windows NT 5.0; fr; rv:1.7) Gecko/20040803 Firefox/0.9.3 Hello > Can anyone confirm if the message "Using <%S> as default motif." (with %S > replaced) is being displayed, or anything similar? Yes, "Using <%S> as default motif." is displayed. But the actual motif isn't changed. The only way to change the motif that works fine is to do it via the Tools>Options appropriate text-zone. Please make it work like before !! :)
(In reply to comment #3) > Please make it work like before !! :) No use saying that, since it works perfectly here. :P Not to mention there was a distinct lack of changes to this code...
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr; rv:1.7) Gecko/20040803 Firefox/0.9.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr; rv:1.7) Gecko/20040803 Firefox/0.9.3 Let's get more precise about it. WHAT DOESN'T WORK: When a css file is dragged and dropped on : network window : the error message is [ERROR] Internal error dispatching command “sync-motif”. [ERROR] [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMXULElement.boxObject]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://global/content/bindings/browser.xml :: get_docShell :: line 0" data: no] [INFO] Using <X.css> as default motif. (where X.css stands for the ful path to motif) But the MOTIF IS ACTUALLY CHANGED to what is wanted in THIS WINDOW. channel window : the error message is the same as the one described before, but the motif is actually changed to what is wanted in THE NETWORK WINDOW (not the channel window) user window : there's no error message, only the info saying "Using <X.css> as default motif.". But the motif is actually changed to what is wanted in THE NETWORK WINDOW (not the user window) where there's no error nor info message displayed. a /css command in each kind of window produces the same errors. WHAT WORKS FINE: /network-motif X.css in the chatzilla text zone /channel-motif X.css in the chatzilla text zone /user-motif X.css in the chatzilla text zone Typing or copying the path X.css in the tools>options appropriate text zones.
Excelent, thanks. So, as a summary, would it be right to say it only changes the network view when dropped or done with /css?
For me, everthing actually did change (thats what I meant by - "it worked") and it just produced that error message. I started up the JavaScript debugger - but I couldn't seem to figure out how to do a stacktrace (I've worked with strace but I can't figure out a GUI JS Debugger - go figure :) If someone could point me to a walkthrough (not as a comment - but as an e-mail) -- to reduce the amount of useless **** that everyone will get -- I would appreciate it. Note: I tried to find a walkthrough/tutorial/how to via google with no success. Thanks! - Mick
Product: Core → Other Applications
I'm pretty sure this is the same bug, I just wish I knew what was going on. :-/ *** This bug has been marked as a duplicate of 265573 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: Other Applications → Other Applications Graveyard
You need to log in before you can comment on or make changes to this bug.