Hi Cemil,

Our products will support IE9. Please wait for our next product release.

Regards,
Lili Khiung

How soon do you expect the new release? Considering that IE9 has been around for a year now, we find it critical for our customers to be able to use our products in the new browser version.  If you provide a release soon, we would even be considering to renew our licence with Intersoft which we haven't done in over a year due to poor environment support.

Hi Dasha,

Lili,

Our company has not upgraded your software in a long time.  This was due to a very high number of customizations and workarounds that we had to apply to the javascript every time we upgraded to the latest version.  We have voiced our problems many many times and reported all the issues, but not too many of them were addressed.  At one point the company decided that we will no longer upgrade to save time and resources.

When IE officially released, we encountered multiple issues with the WebGrid, which is not that surprising, considering we're using version 7.0.7200.400.  I then decided to visit your live demo to see if you guys have upgraded to accomodate IE9.  As I said, we would even be willing to renew our licence if the controls worked.  I'm attaching a screenshot of what I saw.  Not only was I not able to navigate the examples because the tree view on te left isn't working, but the grid looked copletely broken.  None of the client side functionality like sort column or context menu is working as well.

Did I do something wrong? Or is there an outdated version running in the live demo?

Hi,

Dasha has mentioned a good point. I have the same problems in IE9. Not only the live demos but also the one I am using on my current project are not working properly. They only work when the compatibility mode is active or when you add

<meta http-equiv="X-UA-Compatible" content="IE=8" />

on the page for compatibility.

Dear Customers,

Our control will certainly support IE9. Currently, we are retesting our controls in IE9. We will ensure that all our controls support IE9 in the upcoming release (2011 R1).

Regarding the issue in live demo, this is an issue in IE9 browser itself. IE9 has a critical issue where the standards mode was  incorrectly chosen although the page doesn't supposed to use standards mode. This bug has been filed in Microsoft as attached in the image. To try the sample at the time being, you have to open the sample in a new window. To do this, click the "Open in New Window" button. We will display a friendly message in the upcoming release to avoid the confusion.

Regards,

Lili Khiung

Hi Dasha,

I am terribly sorry for the mistake. Our Products will be enhanced to be fully supporting IE9 in the upcoming 2011 R1 release.

Regards,

Lili Khiung

Do you have a date yet, when we can expect the 2011 R1 release will be out?

Best Regards

Rolf Arndt

Thx alot

Cemil Fidanligul

For sharing the information how to fix the problems for now.

Hopefully its only a solution which we need to have implemented as short time as posiable.

Best Regards

Rolf Arndt

Hi Rolf,

We are planning the 2011 R1 Release to be out within this month.

Regards,

Lili Khiung

Hi Rolf,

We are planning the 2011 R1 Release to be out within this month.

 

Regards,

Lili Khiung

Will this release be out soon? Any release date yet?

We are alot who are waiting on this release.

BR Rolf Arndt

IE9 Final is out and WebGrid 2011 R1 is out.

Did anyone test if this is working now? Is this "bug" (or maybe intended behaviour) changed in the final IE9?

Also, from the bug report I see that you were talking about an IFRAME being rendered in quirks mode and that mode wasn't applied if the parent is standards mode. Does this mean that WebGrid still uses quirks mode? Or is the content rendered browser-specific? Can't WebGrid just render standard compliant HTML and only for old browsers create special output?

Hi,

WebGrid can run in quirks mode and standard mode. The problem with IFRAME in IE9 occurs when using the HTML DOCTYPE and put in the IFRAME. The IE9 treat it like XHTML DOCTYPE instead of HTML DOCTYPE. But our WebGrid already supports HTML and XHTML DOCTYPE, so does for the old browser.

Regards,

Lili Khiung

Yesterday I tested the WebGrid in our environment and I'm sorry to say that the issue is still there.  The easiest way to reproduce what I'm seeing is to put a WebGrid in a Sharepoint 2010 web part.  Sharepoint 2010 turns on the compatibility mode by default, but if you F12 the page and enforce IE9 document standards, then the error becomes obvious.  I loose all client side functionality like sorting, grouping, context menu, ect.  From my investivation the problem lies in the javascript files when the code tries to access the gridId attribue by way of the dot operator (gridElement.gridId).  If I change the code to gridElement.GetAttribute('gridId'), then it works.  This does not only happen with the gridId attribute, but many others that are spread out all over the javascript files.  My concern is not the standard Sharepoint pages. As I said, the compatibility mode is turned on automatically and the user would not know what's happening.  We're planning to develop a series of templates on the Sharepoint platform that will take advantage of HTML5 which will require IE9 running in IE9 mode.  If the WebGrid is not working, then it's a huge problem for us.

Please let me know if you need more details on how to reproduce the issue.

Thank you,

Dasha.

Hi Lili, just wondering if you've had any luck reproducing my issue?  Do you need any help from me?  This is a pretty critical matter for our company, so plase feel free to reach out if something is unclear.

Thank you, 

Dasha.

Hi Dasha,

Deeply apologize for the inconvenience. We are still investigating your issue and will inform you as soon as we got any progress for your issue.

Regards,

Lili Khiung

Lili,

I am also experiencing the problems described by Dasha above. I am running a WebGrid in IE 9 with standards enforced, and have no client-side functionality (ie: right-click). I am currently trying to certify our product as IE 9 compatible, and cannot do so until WebGrid works properly.

This bug is currently our highest priority. When can we expect this issue to be resolved?

Hello,

As far I know, compatibility/quirk mode is choosed as default, when running non XHTML mode.
Example,
If you run all our HTML document mode in our WebGrid sample, IE browser would choose quirks mode as default. If we enforce to use IE9, surely it will return javascript errors or some functionality would not work.
But, if you tried to run a XHTML mode (i.e XHTML.aspx), it will automatically choose IE9 as default.

So, All I want to say is, our WebGrid supports IE9. If you want to enforce the browser to use IE9 as document mode, you need also to use XHTML mode in your webpage.

Regards,
Handy

Handy,

I just ran the scenario you suggested, and I am still getting the following javascript error from WebGrid: "Unable to get value of the property 'Tables': object is null or undefined".

The web page is marked as:

I'm using the latest version if WebGrid, and viewing the page in IE9, and still getting javascript errors. I also tried using XHTML 1.0 Strict, and received the same javascript errors.

Thanks.

Hello,

Can you provide us a simple sample that replicates this issue? Also, If you are running our XHTML.aspx in WebGrid sample, does the issue persist?

Regards,
Handy

Did anyone from intersoft try to reproduce the situation that i described? All you need to do is create a simple web part with a WebGrid, add some static data to it, and put it on a SharePoint 2010 wiki page.  When you force the ie Document Mode into Quirks, the page does not even load.  If I enforce Document Mode = IE9, then I loose all client side functionality for reasons that I already described: IE9 does not recognise the dot accessor for custom attributes.

Handy,

I've attached a very simple example that does not work in IE9. Please run the example below using IE9, and you should get the error I described above ("Unable to get value of the property 'Tables': object is null or undefined").

The behaviour after the javascript errors are exactly as Dasha describes - loss of all client side functionality.

NOTE: I have run the same code in IE8, and it functions without issue.

Thanks.

Hi Dasha,

Regarding issue in sharepoint, we are still investigating this issue. I have forwarded this to our developerteams and will let you know the update soon.

Regards,
Handy

Hello,

I don't see any of attachment sample in here. Can you please reattach the sample?

Regards,
Handy

My apologies. Please see the attached example.

Thanks.

Hello,

I can replicate the issue that you mentioned. However, this issue has been fixed in our 2011R1 release.
As we discussed at beginning that our WebGrid 7 would fully support IE9 in our next release. When I looked into your project bin folder, it was using older build version of WebGrid7. 
If you run our WebUIStudio2011R1, this issue would not happen.

Regards,
Handy

Thanks Handy,

I upgraded to the latest release of WebGrid, and the javascript errors have gone away. Sorry for the confusion, and thanks for your help!

Handy,

I appreciate you guys looking into my issue. Are there any news?

Dear Support,

It has now been a MONTH since I described the issue I've encountered in a Sharepoint environment.  When I put together the test project, it took me 3 hours.  Granted, you may be less familiar with Sharepoint, and probably more busy, it would naturally take you longer.  But a month????  Can someone please tell me if they tested WebGrid 7 in Sharepoint 2010 in IE9 document standards. I'd be very happy to learn that I did something wrong and I need to re-check my setup, etc.  But please take the time to try out my scenario and tell me what you find.

Hoping to hear from you soon,

Dasha

Hello Dasha,

Unfortunately, due to other high priorities and urgent issues, we have to shipped SP1 earlier than expected. As the results, there are several priorities that need to be changed. I am apologized that we did not focus to test in SharePoint environment. We are not quite familiar with SharePoint environment.
Perhaps, you can help us to avoid wasted times by providing a simple video to show step by step to replicate the issue (integrating to sharepoint and import webpart to Sharepoint library, settings, etc).
Once we are able to have the same result in here, we will forward this to our development teams.
Thank you for your understanding in this matter. Once again, I am very sorry that we are very late to assist you.

Regards,
Handy