big problem....
Click in a item of the tree kills ie 8 / 7!
With IE 6 / or Firefox in runs perfekt.
Has anyone a idee why the Browser chrash????
Hey I tried adding an asp TextBox with width set to 99% to one of my pages with a data tree. I didn't get a browser crash. Could you maybe provide some more information so that we can verify our control did not cause this. Were you handling node click? Navigating?
thanks,David Young
I got the problem still. In the on case the removing width in % of the textbox sloved the problem. But on other Pages i got still the crash problem.
I use the tree for navigation. The Postback Event of the tree is used to open another Page, or to select a object. If the Browser crashes or give the info illegal access the session is dead. The Problems comes and goes. If it happens i never get a postback.
Its a big trouble, i will try to replace your tree with the Visual Studio Tree. With the crashing tree we are not able to use the webside.
we use NetAdvantage for .NET 2009.1. Fileversion 9.1.20091.1015
I dont thing is a Problem of Settings or a special Markup. We use 2 trees in the Master Page Side of the applikation. Every Page uses the Tree and somtimes it chrashs...
The Message from ie:
res://ieframe.dll/acr_depnx_error.htm#,http://localhost:4001/Plan/Plan.aspx
Diese Webseite wurde geschlossen, um den Computer zu schützen. Diese Webseite wurde aufgrund eines fehlerhaften oder bösartigen Add-Ons geschlossen. Mögliche Vorgehensweisen: Zur Startseite wechseln Zur zuvor angezeigten Seite zurückkehren
this happens when click on a item of the tree. Not ever you can click 10 times nothing happens and click elven brings the error...
other question is there a solution for the Firefox 3.6?
the ig_webgrid.js uses "document.getBoxObjectFor(elem)". This Function is not more supported by Firefox 3.6.
I tryd to change the ig_webgrid.js file in
D:\Programme\Infragistics\NetAdvantage for .NET 2009.1\ASP.NET\CLR3.5\Scripts
but when i run the app there ever is the old script in the page.
thanks for help
Hi,
Which build number are you using? Could you attach some sample that reproduces this issue? I tried with a couple of scenarios but wasn't able to see this issue. Maybe it's related to something specific in your markup, or on the properties that are set.
Thank you,
Angel