JS error in line 12 - object is missing
transliteration - November 13, 2008 - 20:34
| Project: | Chatblock |
| Version: | 5.x-1.0.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
I didn't notice bug myself but one of my users has reported the following.
On the Maxthon browser he often gets pop up with message which can be translated to English approximately as:
----------8<---------
During the execution an error has occurred.
Do you like to start debugger?
Line: 12
Error: The object is needed.
----------8<-----------
When confirming to start debugger, it point to the line 12 of chatblock.js:
if (objDiv.scrollHeight > 0) {and shows a message:
---------8<---------
Error in execution of Microsoft JScript: The object is needed.
--------8<---------
I have following Settings for the chatblock:
logged in users can both view the chat and post chat messages,
unlogged users have permission only to view the chatblock.
Does anyone has ideas, i am confused.
Thanks for the module.
#1
I think the README.txt includes a list of supported browsers. In any case, I have never used the Maxthon browser so I have no comparison, but it is clear that it's implementation of JavaScript is not exactly the same as other browsers.
However since the Maxthon seems like it is an extremely small user base, my suggestion to your user is to try a different browser for chatting. In any case this is not a critical bug and I'm going to mark it "won't fix". If you can provide a patch which keeps the existing functionality for the other browsers and makes this still work for Maxthon, I'll test your patch and commit it.
Dave
#2
Ok , I see, I need time to investigate the problem. Any help and suggestions are welcome and highly appreciated. So, If someone will have ideas, I still ask to join the discussion. And since the Maxthon is an IE-based browser, I doubt if the IE will actually not have the same issue. Nevertheless, I understand you, Dave, as far such bug is not reported on IE, you will not spend your time to fix that, so I ask again other volunteers who have time and interest, to help me to resolve that. Thanks.
#3
I've tested this module in IE before and not noticed this bug, but if you could check to see if it doesn't work in IE then of course I have to fix it given the market share of Internet Explorer.
#4
Good news, after the user which has reported the issue has got a newer version of its browser, the issue is gone, so I guess there was a bug in the browser, not the module. So, I apologize for disturbance. Guess we can close the issue now.
#5
Okay, marking this fixed then.
Dave
#6
Automatically closed -- issue fixed for two weeks with no activity.