Hi,
After migrating to the new version my templated combo boxes freeze upon selection.
After several hours of debugging I found out that igCombo enters into an infinite recursion call of function _replaceTextInNode.
I've modified your own example http://jsfiddle.net/gh/get/jquery/1.9.1/igniteuisamples/jsfiddle-samples/tree/master/EN/HtmlSamples/combo/templates/ into http://jsfiddle.net/mPrL7/1/ in order to replicate it. I basically removed the image and address from the template. Select an item them try reopening the combo then the browser will freeze.
I would like to reiterate that my template was working in 2013.2
My template is simply <div><span>${__parameterlocal_}</span><span>${__parameter____parameterunits_}</span><span>${__designminimum_}</span><span>${__designmaximum_}</span></div>
Please could you confirm whether it is a bug? If it is, how long should I wait for a fix?
Regards,
Silverio
Hello Silverio,
I am currently reviewing this scenario and will keep you posted of any available information. Please do not hesitate to contact me with any updates in the meantime.
Hi Silverio,
This issue seems to only be present in the RTM build for 14.1 - 1021. The CDN links used in the jsfiddle are the ones used by the sample browser and therefore point to this build. Changing the CDN to point to use the new SR seems to resolve the issue:
http://jsfiddle.net/mPrL7/2/
http://help.infragistics.com/doc/jQuery/2014.1/CLR4.0/?page=Deployment_Guide_Infragistics_Content_Delivery_Network%28CDN%29.html
Hope this helps. Please feel free to contact me if you have any questions.
Hi Petar,
Thanks for the quick reply.
Please could you point out where paid customers can get the new SR so that we can wrap it with our product? Our next release is due on Friday.
Cheers,
Sil
I've found the IgniteUI_v14-1.2031_SR release which is identical to what I currently have.
I hope that you understand that the example in JSFiddle might work with SR for you but our code doesn't and we have already spent too many hours debugging igCombo and I have already pointed out where the problem occurs.
We will rollback to 2013.2 until you can replicate the problem in your end and come up with a new SR.
Hello Sil,
Thank you for your replies.
The reported issue was also tested in a local sample - my test sample is attached for your reference. Please note that with version 14.1 build 2031, the behavior so far does not seem to occur. In order to be able to research the matter further and provide you with more feedback, I would need a working sample demonstrating the issue in question.
Please do not hesitate to contact me with any updates or questions.