Hello,
When I select a row on my datagrid, I fire a server event to update other fields in the web page.
Whit enableAjax = true, my event is fired, but impossible to modifie the value of the other field. Normal.
So, I set enableAjax= false
But with this, a have a javascript error :
activeElement is null on this function, so impossible to acces nodeName
_onDocumentMouseOverHandler: function(e) { this.__x = e.clientX; this.__y = e.clientY; var activeElem = document.activeElement; if(!this.__controlActive && activeElem.nodeName != "BODY" && activeElem.nodeName != "HTML") { this.__lastFocusedElement = activeElem; if (this.__lastFocusedElement && this.__lastFocusedElement.nodeName == "INPUT") { this.__lastFocusedInputCaretPosition = this.__lastFocusedElement.value.length; } } },
version 10.3.20103.2105
Thx
I was getting this error with version 10.3.20103.1013 so I downloaded the latest which is 10.3.20103.2217 and I am still getting the error. Now it is on line 3192 instead of line 2884 but it is the same error in the _onDocumentMouseOverHandler - the code says var activeElem = document.activeElement;
Was the bug reintroduced with this version?
Thanks - I can be reached at dsanborn@mcgenergy.com.
Hello dufour01 ,
In order to obtain the latest release you should:
1) Login with your account
2)Go to Support and choose Register your Product(if you haven’t register your key)
3)Enter the Product Key(if you haven’t register your key)
4)Go to My IG My keys and downloads
5)Select your Product
There you will find the latest release available for download.
If you need further clarification on this matter don’t hesitate to ask.
Best Regards,
Maya Kirova
Developer Support Engineer
Infragistics, Inc.
http://ko.infragistics.com/support
yes, I have a WebDataMenu on the page.
I look for upgrade
Hi dufour01,
I did a search for that code and it appears to be from the WebDataMenu. You have one? I also compared the code and our source and it looks as if a bug has been fixed regarding this has already been fixed and released. It is bug 77774. It was resolved in build 10.3.20103.2150, so if you upgrade to the latest Service Release, you should be fine.
regards,David Young