We have a project that uses the WebDataTree for the main menu. When upgrading to the latest service release of 2017.2 the code that we use to see the keyboard focus to the tree fails (error details below). We are using the following code to put the keyboard focus on the tree.
var trTree = $find("trMainMenu");var feTree = trTree.get_focusElement();feTree.focus();
It looks like the fix to Bug #242338 is causing the problem. In the code below "aNode" is null, so aNode._get_owner() fails.
// I.G. 12/Dec/2017 Bug #242338 When tree is in template of WebExplorerBar first node that is selected always remains selected.//getItemFromElem(elemAtPoint) returns any node element (because it only ckecks for address) and so it can return an WebDataTree node instead of a WebExplorerBar one.// There should be a check.to make sure it is an WebExplorerBar node.if (aNode._get_owner() !== this) { aNode = null;}
Can you please confirm that this is an issue, caused by your bug fix and advise on when we can expect this issue to be resolved.
Hello Kurt,
I am working on your inquiry. Using the latest Service Release(2017 vol.2 2051 build), I am not able to reproduce the error.
Can you check if the error is reproduced with the attached sample and steps below?
Steps:1.Run the sample2.Select a node3.Click the button
In the button click, the following code is executed:
function test() { var tree = $find("WebDataTree1"); var elem = tree.get_focusElement(); elem.focus(); }
If additional code is required, or steps are different, would you let me know that?
WebDataTree.zip
Yuki,
I get the same error on your sample as well. To view the error add the following to your script section.
window.onerror = JSErrorHandler;function JSErrorHandler(msg, err_url, line) { alert("Message=" + msg + "\n\nURL=" + err_url + "\n\nLine=" + line); return true;}
Infragistics 17.2.20172.2051. Downloaded and Installed from the support page if that makes a difference.
Visual Studio 2017 (15.6.5)
Running on a Windows 10 Pro 64bit development box. IIS and IIS Express both get the error.
The error occurs in IE11, Edge, Firefox and Chrome (all latest versions).
Note: I had to comment out <system.codedom> section of the web.config as I don't have those packages installed and we don't use them in our projects.
Thank you for the additional code. I see it is reproduced on my end.
I have investigated your issue, and I have asked our engineering staff to examine this further. To ensure that it will receive attention, I have logged this behavior in our internal tracking system with a Development ID of 252033. This will be assigned to a developer in a future sprint to review my investigation and confirm my findings or to offer a fix, or other resolution. I’ve created a case for you CAS-195078-D4M8L0 and will update you for the progress of this issue via the mentioned case. You could reach your case following the link below:
https://es.infragistics.com/my-account/support-activity
Please let me know if you need more information.