I have noticed one issue so far, and I noticed that the forums have a couple other issues.  Is there a date or approximate date on when IE9 support is planned?


Thanks,
Dave

Very soon- we're looking into issues now and expect to have a release out in next few weeks addressing issues with IE 9. This is dependant on what we discover, obviously, and the timeframe is approximated based on the issues we do now (thus far, there are a few issues with context menu).  What problem have you faced? Please share whatever you discover so we can investigate.

Thanks for the quick response. 

I have noticed most things do still work, but I did find one bug.  I have a drop down menu, with a sub menu.  When I click an item in the sub menu, the sub menu does not hide after clicking.  The main menu does hide.  I can provide more details on how it is set up if you cannot reproduce this.

Reproduceable here:

http://aspnetajax.componentart.com/control-specific/menu/features/simple_contextMenu/WebForm1.aspx

Thats the same problem we have, see: http://www.componentart.com/community/forums/t/62448.aspx

Since we have a subscription with source code, we made a change in the javascript code to temporarily fix the error (has to do with null objects) until  officially ComponentArt fixes the problem.

Thanks for responding everyone. Resolver, can you verify something for me- is your menu a context menu (like the linked demo)?  If it is, this is a known issue, and is one of the ones I'm referring to above- sub-groups on a context menu don't collapse correctly and throw an error.

It is a context menu.  I get the following error onclick of an item in the submenu:

SCRIPT5007: Unable to get value of the property 'firstChild': object is null or undefined

 

ScriptResource.axd?d=35Y-V9DzNzmlheIL1ZEg2jcP_VOH1YhVhLyPKdojWflfAblNkcMVdpDI4gCvGxzHpyDqaWiPn90OIzgDjdT6GiJOr_oRmzlNVOQ8m887DYed_ivr3Dwk44f2XLRVHMAmtbxMusuXJwrhqNIhHFn4H7ZNne2eWNbE3TqH2fBAqG1ff94HNiT_B7WMUL6Hnd5A0&t=6c65fa59, line 1 character 68623

Thanks for responding- that is definitely an issue we're aware of and that the patch will address.

When will there be a patch for IE9? IE9 is now pushed via windows update and more people are using it every day, so the problem becomes bigger and bigger.

I though you were focusing on Web.UI again, but what we get a new beta of data visuslization and nothing about a patch or a new version of Web.UI. How can you still sell a product when there are no updates. You still do not fully support asp.net 4 (still have to use options to run asp.net 4 the 3.5 way, e.g. for id's) and bugs that already existed since the first beta release of IE9 (almost a year ago) and are still not fixed. We have changed the source code (temporary fix), to make it work in IE9. We can not tell the customer/wesite visitors: do not intstall IE9.

There will be a patch coming to address the IE 9 issues. For the record, so far there are two issues related to the menu confirmed:

 

1. the old, deprecated client event model doesn't work (e.g. using ClientSideCommand rather than ClientEvents), and 

2. custom context menus with multiple group levels throw an error when collapsing.

 

If you're experiencing any others please let me know.

 

The next release of Web.UI will follow the next release of dv, which is currently in beta.  I'd be interested in seeing the fix you implemented, if you wouldn't mind sharing it-  it may help get a formal fix in place more quickly. If you want to share, you can just post what you did or you can open up a support request (I'd refund it of course).

The problem with the context menu collapse is that the javascript event order in IE9 is different then previous versions. The problem lies in the javascript function Menu_RepaintItem in A573R388.js. When the contextmenu with multiple groups is collapsed, and you are using left or right icons in the parent menu item, it tries to repaint the item and change the left or right icon using the firstchild or lastchild properties. But the parent is already distroyed (and I think the repaint item event should not be fired) and there is no firstchild or lastchild object anymore (this is the javascript error you get).

Because the javascript is obfuscated it is hard to investigate the real problem. So al we did was to put an extra check in the function if the firstchild or lastchild properties is not null. This is really a workaround and not a fix, but it works :). So we change on several places the following check

 

if (_157.RightIconUrl != null)

to

if ((_157.RightIconUrl != null) && (_157.lastChild != null))

The problem lies in the fact that the parent group is distroyed before the subgroep, and the repaint item function is called on an item which does not exists anymore.

I hope this makes it more clear. As I said it is just a workaround and not really a fix.

Fantastic - thanks for posting this. I was aware that it was related to a change in the collapse order (parent collapsing before child), but the icon variable is new information for me. I'm going to forward this to the team right now.

An update for anyone who is being affected by this: I can send a custom 2011.1 build to fix the problem (the fix will be applied to the next version as well, of course).  Just open up a support request and I'll send it along (and refund the ticket, of course).

Do we get an update for 2010.1 as well ?

I'm afraid not - we don't retroactively apply fixes to old versions. If you don't have a key for 2011, I'd suggest contacting sales as they can very likely work something out with you.