I'm experiencing some strange problems with the BackOffice that seems to be related to jQuery. I tried to upgrade jQuery from 1.6.2 to 1.7.1. This reduced the amount of crashes but I still get some of them and moreover I don't know if upgrading jQuery can introduce some other problems.
With some document types when I click on a node in the left treeview to edit the content I get randomly one of the following results:
the address bar of the browser goes to: res://ieframe.dll/acr_error.htm#,http://localhost/umbraco/umbraco.aspx#content;
the iexplorer.exe crash;
the full page refresh and I get a message at the top telling me "This tab has been recovered";
I got the Yellow Screen Of Death telling me:
Height must be non negative. Parameter name: value
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.ArgumentOutOfRangeException: Height must be non negative.
Parameter name: value
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:
[ArgumentOutOfRangeException: Height must be non negative.
Hey I have been encountering this problem as well, I might try to force compatibility mode (by adding the meta tag to the backend default page) and see if that fixes the issue.
jQuery problems with Internet Explorer 8
Hi guys,
I'm experiencing some strange problems with the BackOffice that seems to be related to jQuery. I tried to upgrade jQuery from 1.6.2 to 1.7.1. This reduced the amount of crashes but I still get some of them and moreover I don't know if upgrading jQuery can introduce some other problems.
With some document types when I click on a node in the left treeview to edit the content I get randomly one of the following results:
Height must be non negative. Parameter name: value
Hey I have been encountering this problem as well, I might try to force compatibility mode (by adding the meta tag to the backend default page) and see if that fixes the issue.
L
On my side I have modified my /umbraco/umbraco.aspx two times.
Once with those two lines:
And the second time with
I checked the source code of hte pag and the response headers with Fiddler. Both are set correctly but it still crashes...
is working on a reply...