This seems like a dupe of bug 1389449 - doesn't seamonkey ship trunk cz?
> This seems like a dupe of bug 1389449 - doesn't seamonkey ship trunk cz? We do but it usually needs to be manually updated if the version doesn't change. Should be in the seamonkey-2.54a1.en-US.win64.zip if someone wants to extract it but it is not signed: https://archive.mozilla.org/pub/seamonkey/nightly/2017/08/2017-08-22-04-47-02-comm-central-trunk/ 2.54 itself isn't currently much good for anything. I am wating for the tree to stabilize a bit more before I fix the errors.
It seems that in the 2.54 nightly from 10-Sep-2017, Chatzilla errors out with the following message: Timestamp: 9/10/2017, 3:19:00 PM Error: TypeError: client.deck is undefined Source File: chrome://chatzilla/content/handlers.js Line: 10 The line in question: for (var i = 0; i < client.deck.childNodes.length; i++) Chatzilla version in question is the latest nightly: ChatZilla 0.9.93.2017081717 [SeaMonkey 2.54a1/20170910061624]
(In reply to John Duncan from comment #3) > It seems that in the 2.54 nightly from 10-Sep-2017, Chatzilla errors out > with the following message: > > Timestamp: 9/10/2017, 3:19:00 PM > Error: TypeError: client.deck is undefined > Source File: chrome://chatzilla/content/handlers.js > Line: 10 > > The line in question: > > for (var i = 0; i < client.deck.childNodes.length; i++) > > Chatzilla version in question is the latest nightly: > > ChatZilla 0.9.93.2017081717 [SeaMonkey 2.54a1/20170910061624] This feels like a separate (new?) issue to comment 0 given the different error. Frank, can you confirm?
Yes must be a new issue. I looked at it yesterday but was unable to find the cause. Probably because of scope changes. Not sure. There were lot of removals and changes in the is area in the last weeks. I am quite sure this bug here is fixed/invalid but we can either remodel it or create a new one.
You need to log in before you can comment on or make changes to this bug.