I have one user who encounters JavaScript errors on most (if not all) web pages I've created using ASPxperience 9.2.6 and 9.2.8 (wasn't a problem in 8.3).
The most common error is in the Actual results box below.
Most of the pages use the ASPxPopUp control. The errors occur on a fresh GET request.
The user is using Windows XP SP3 and IE8. They had the same problem using IE7, and I asked them to upgrade but with the same results. Launching without add-ons makes no difference. I've checked their environment for any obvious problems but cannot find anything that would be interfering. I've reset security settings, advanced options, cleared the cache, updated using Windows Update, etc.
I cannot reproduce the errors on other machines running IE6/IE7/IE8.
Any ideas what might be causing this?
Actual Results:
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; chromeframe; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET CLR 1.1.4322; MS-RTC LM 8)
Timestamp: Thu, 12 Nov 2009 22:25:13 UTC
Message: Object doesn't support this property or method
Line: 1676
Char: 3
Code: 0
URI: http://migsptest/EIS/DXR.axd?r=1_103
We have closed this ticket because another page addresses its subject:
Add support for Google Chrome Frame plug-in for Internet Explorer
Hi Sam,
Unfortunately, the information you provided doesn't allow us to clearly diagnose this problem. If possible, describe your approach in greater detail or post any sample project showing the issue. We'll deploy it locally, and then check for a a solution.
Thanks,
Alex
I have attached a repro project. Again, I can only reproduce the problem on this one user's machine (so far). Most of our users are still using IE6, but we've begun an upgrade and I don't know how many other machines may exhibit the same problem after upgrading to IE7 or IE8.
Just visiting with Default.aspx (GridView) or WebForm1.aspx (popup) results in the aforementioned script errors. I looked at the line of JavaScript that is failing, and I couldn't really see why it would be failing.
(My original posting contained the DX JavaScript in question as an attachment.) Let me know what other kinds of information I could supply that might be helpful.
Hi Sam,
Thanks for posting a sample project here. I've tested it locally, but I didn't notice anything unusual. It appears that some third party software which blocks our scripts is installed on your machine. Could you please check your proxy settings and disable the proxy (and antivirus software, if any) temporarily? Does this make any difference?
Thanks,
Alex
No proxy is in use, and the AV is not making any difference. I guess you haven't seen anything like this before? It is odd that it is version dependent and only the DevExpress components exhibit this behavior.
Hi Sam,
I'm sorry to hear that you're still experiencing this problem. So far, we haven't managed to reproduce this similar problem in our tests. Based on the information you provided, we can only assume that this problem is specific to a particular machine configuration. Is there any chance that you reinstall the OS on the problematic machine, and then check whether this problem is gone? We apologize for the inconvenience.
Thanks,
Alex
FYI, B142057 is reporting the same issue, and that is on a clean install of the OS and browser. Obviously there is a problem beyond our 1 machine. Perhaps some of your senior engineers can have a look at this issue?
I was doing some research into the addEventListener function, and I've seen instances where developers have timing / synchronization issues, where they try to call the function for elements that don't exist yet (before 'domready'). So the script actually starts executing before the page is complete.
Sam,
That's true, the problem described in the B142057 thread is similar. Our R&D team guys have already looked into this problem, however, we didn't manage to isolate the issue locally. Is there any chance that you can provide us with remote access to the problematic machine, so that we can take a closer look?
Thanks,
Alex
I figured it out. The prescence of "chromeframe" in the user agent is causing this problem. For some reason, ChromeFrame does not always attach this string to the user agent. In any case, it is likely that your JavaScript code is looking for the "chrome" substring and assumes this means it's executing under Chrome, which is incorrect. Google has scripts available to help you differentiate between the two.
This would be a bug in the DevExpress code. Likely this was not an issue in 8.3 because there was probably little/no Chrome detection code.
Note that this doesn't just affect the JavaScript code, it seems to affect server content as well (getting different markup with that user aganet), as you probably have to fix this in the script AND on the server side.
You may want to ensure that other bug report is marked as solved when this one is.
Hi Sam,
I believe you're referring to a known issue. There was a bug in Chrome Frame plugin itself, and it has already been fixed (see Add support for Google Chrome Frame plug-in for Internet Explorer). So, I suggest that you install the most recent Chrome Frame version on your machine, and then check whether this problem is gone. Other than that, note that we cannot guarantee that a web page is rendered correctly via the Google Chrome Frame, because we don't officially support it.
Thanks,
Alex