I had a page working fine earlier. JQ Update has broken this. Any idea about the error in the screenshot. I am using Hierarchical grid with template columns
Uncaught Error: Syntax error, unrecognized expression: tbody > tr > td:[data-skip=true]
Strange.. it is... Is there a way i can see generated HTML for igGrid
This is still unresolved error. Please suggest
I am seeing this error as well. Do we have a solution yet?
Hi guys,
I have some good and some bad news for you.
The good news is that a similar error was reported in the forums some time ago about jQuery 1.8.Our development team have tackled the issue and the fix will be available in the upcoming Service Release.I think that the error was very similar to this one so perhaps the fix will apply to this problem as well.If you like, you can contact the Developer Support team so there can be a new development issue opened for this problem with jQuery 1.9.0.
Also, the dev team will be doing sanity checks on jQuery 1.8.* and 1.9.0However, here are the "bad" news.jQuery 1.8.* and 1.9.0 are relatively brand new and they did introduce a lot of big changes to the library so it's expected that our controls can show defects when operating with these versions of jQuery.Also, I' like to turn your attention to a couple of statistics
As you can see jQuery 1.4.4, 1.6.* and 1.7.* are the most used versions in production environments, thus it's our #1 goal to provide 100% compatibility with them.jQuery 1.5.* series were a flop and that's why 1.6.* came out so fast so although we support 1.5.*, I won't mention it from here on out. So since 1.8.* and 1.9.* are new and they introduce a lot of new stuff, we'll need some time to adapt to them, but that won't be our primary goal.I realize that in saying this a lot of eager early adopters will get burnt, but I'm afraid that we have to prioritize our tasks in order to best suite the wide public's interests first. As a conclusion, our jQuery controls will have support for jQuery 1.8.* and 1.9.*, but that will happen in the upcoming Service Release at the soonest.Thank you for understanding the matter.
Hi Rocky,
The problem comes from a fundamental rule about printing strings in HTML - the < and > symbols denote the beginning and the end of a tag so in most cases you never want to print them directly, simply because the browser will either remove those symbols from the DOM tree or it will treat everything between them as a tag.
The igGrid and the igHierarchicalGrid both print column data as raw HTML on purpose, allowing the developers to actually have HTML code in the values of their columns, which may in rare cases be undesired.
The solution lies in using the grid column's formatter function - in it you can substitute all occurrences of the < and > symbols with their escaped versions: < and >
Here's how the definition of your column can look like:
{ key: "Message", headerText: "Message", width: 150, dataType: "string", formatter: function(val) { return val.replace("<", "<").replace(">", ">"); } }
Hope this helps and good luck!Cheers,Bobby
i am using infragistics jquery grid 2013 version where i am facing problem in data populated in the grid. Please find the example of json object mentioned below
Object { Id="5225e9e351d8d61f78697188", Date="2013-09-03 15:53:39.5522", Message="messeage Service for '<Query>ajax'"}
Everything works fine but in the grid for message column it get populated and cell has a value as "messeage Service for 'ajax'" instead of showing the full message as "messeage Service for '<Query>ajax'".
"<Query>" is getting excluded from data rest is binding to the grid cell.
I already spend a day on this but not able to resolve it. Please help me its urgent.
Glad to hear that the new volume release (13,1) works for you :)If you run into any trouble when our controls are used in conjunction with a specific version of jQuery or jQuery UI, do not hesitate to let us know.All the best,Borislav
It seems the new 13.1 version of infragistics fixed this issue. I am now using JQuery 2.0.0 (via nuget) and JQueryui 1.10.2.
Reverting to Jquery 1.7.2 corrected my issue. Thanks for the fast response.