Hi,

we are facing the same problem!

When will there be a hotfix available? This is rather urgent!

Regards

If you have access to source code, fix it is the best solution !

If no, an ISAPI extention should be able to modify USER_AGENT on server side...

ClientTarget = "uplevel" in your page Init seems to solve the WebCombo issue.

However, this seems to cause a problem with a CheckBox in a grid. You can check/uncheck the control but it always has the original value on postback.

Seems that the CheckBox column is always outputting the onpropertychange handler which is IE specific.

I found a workaround is to override the Render event of the page and replace 'onpropertychange' with 'onchange'. Do this when Browsers.IsIE = False.

Has anyone gotten word from the IFG team as to when they might have a patch for this? Setting the ClientTarget = "uplevel" seems like it may create more problems then it solves.

We would really appreciate some sort of reponse or resolution sometime soon as our product is dead in the water on FireFox (especially thanks to their auto-upgrading).  Hotfix, please!

Hi Pro's of Mozilla bugs Fixer's

My problem is i cannot open my Web Application in mozilla latest browser 18.0.2 whcih works fine in Mozilla 9.0.1 ... i dont know how to fix ... I tried my max and now i bugged up solving that issue .... please get me out of this big issue...

Coming to my issue : I am using Infragistics grid view controls on which page i am getting error's ... i think it might be because of Infragistics Grid views.
I am getting an error saying ::::
Input string was not in a correct format.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.FormatException: Input string was not in a correct format.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[FormatException: Input string was not in a correct format.]
System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) +9591147
System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) +119
System.Convert.ToInt32(String value) +48
Infragistics.WebUI.UltraWebListbar.UltraWebListbar.getRenderer() +243
Infragistics.WebUI.UltraWebListbar.UltraWebListbar.get_IsAppStyling() +28
Infragistics.WebUI.UltraWebListbar.UltraWebListbar.OnPreRender(EventArgs e) +72
System.Web.UI.Control.PreRenderRecursiveInternal() +103
System.Web.UI.Control.PreRenderRecursiveInternal() +175
System.Web.UI.Control.PreRenderRecursiveInternal() +175
System.Web.UI.Control.PreRenderRecursiveInternal() +175
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2496


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272

Thanks alot :-) You saved my time . Above solution works for me

Thank you so much for your quick response.  The way you put it makes total sense to me and helped me just make the decision to plan on moving to 11.1.

Mike

Hello-

I see where this fix has been applied into the ASP.Net 11.1 version of controls.  Is there any options for dealing with this issue in 10.3?  I understand that 11.1 is not going to be supported as of June 2012, so I would like to avoid upgrading to 11.1 just to deal with this issue.

Mike Reynolds