Hello,
We've recently upgraded our version of the igniteui grid from 2016.2 to 2017.1 but we are running into a problem when we acces to the grid in responsive mode, we have the following exception :
"Uncaught Error: Element that is being linked does not exists." which happens in the function _linkElementsV : "throw new Error($.ig.Scroll.locale.errorNoElementLink);"
here is the call stack :
_linkElementsV (infragistics.core.js:23993)(anonymous) (jquery.mobile.js:174)_setOption (infragistics.core.js:23692)(anonymous) (jquery.mobile.js:174)_setOptions (jquery.mobile.js:464)option (jquery.mobile.js:455)_super (jquery.mobile.js:159)option (infragistics.core.js:23716)(anonymous) (jquery.mobile.js:174)(anonymous) (jquery.mobile.js:286)each (jquery.js:366)each (jquery.js:155)$.fn.(anonymous function) (jquery.mobile.js:266)_onIgScrollRendered (infragistics.lob.js:70930)(anonymous) (jquery.mobile.js:174)_dataRendered (infragistics.lob.js:70914)(anonymous) (jquery.mobile.js:174)_fireInternalEvent (infragistics.lob.js:40721)(anonymous) (jquery.mobile.js:174)_renderData (infragistics.lob.js:38115)(anonymous) (jquery.mobile.js:174)proxy (jquery.js:500)_completeCallback (infragistics.core.js:13434)fire (jquery.js:3303)fireWith (jquery.js:3433)done (jquery.js:9255)(anonymous) (jquery.js:9482)XMLHttpRequest.send (async)send (jquery.js:9534)ajax (jquery.js:9141)_processRequest (infragistics.core.js:13465)_remoteData (infragistics.core.js:13234)dataBind (infragistics.core.js:12961)dataBind (infragistics.lob.js:33415)(anonymous) (jquery.mobile.js:174)_create (infragistics.lob.js:31271)(anonymous) (jquery.mobile.js:174)_createWidget (jquery.mobile.js:371)$.Widget._createWidget (infragistics.core.js:8202)_createWidget (infragistics.lob.js:30853)
This seems to be happening after that the row fetch by ajax are rendered and it tries to get a scrollingContainer. If i turn the AppendRowsOnDemand off and use the local mode then all the lines are fetched and the problem disappear but we don't want that .
this is how we setted up the feature :
name: 'AppendRowsOnDemand',
chunkSize: "5",
type: "remote",
loadTrigger: "button",
chunkIndexUrlKey: "chunk",
chunkSizeUrlKey: "chunkSize",
recordCountKey: "@odata.count",
rowsRequesting: function (){...},
rowsRequested: function(){...}
Is there any work arround or any patch ?
Thank you :D.
Hello isilog,
Thank you for posting in our forums!
I understand that you are receiving an error when fetching new rows with igGridAppendRowsOnDemand and Responsive mode.
I have a few questions to help better understand this issue.
1. Does this exception still occur if Responsive mode is not used?2. What are the full configuration settings you are using on the grid? Other grid options and features like virtualization and the Responsive feature could also have an impact on this issue.3. What browser(s)/devices do you experience this on?4. What versions of jQuery, jQuery-ui, and jQuery mobile are you using?5. Any other information that could help narrow down the cause of this?
Let me know if I may be of further assistance.
Sorry for the late answer but I've tried to reproduce it outside our solution and I did, the problem seems to occur when the height parameter of the grid is set to null in order to "stretch vertically to fit data".
Here is a .Net test project that reproduce the problem :
https://files.fm/u/sdhqq666
The thing is that the error stop js execution not allowing other treatments binded to later events to happen (in our product):/.
If you need any further information do not hesitate.
Thank you for the sample! I am able to reproduce the issue with it.
I have created a support case for you with an ID of CAS-187528-Y9K4W8. The matter has been determined to be a development issue and has been logged in our tracking system with ID: 243718.
I will leave this case open and update you with any new information. You can view the status of the development issue connected to this case by going to the “Account” tab on our website, selecting "My Support Activity" and then this support case will be listed there. Then, you may select the "Development Issues" tab to view details of this development issue.
Please let me know if you have any questions.