You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 9, 2024. It is now read-only.
Calling any containter's RemoveAll() method makes it emit removeAll(null) unless true/false is provided as paramemter to the call. This makes the client-side code misinterpret the null argument as an object and try to reference null.destroy, thus triggering a run time exception.
To reproduce the issue, just click twice the 'launch window' button. First time it does not trigger the issue because there's nothing to be removed at all, so the breaking test is never triggered. Second time, as there are items within the container, then the error arises.
This issue is Ext.NET-specific.
The text was updated successfully, but these errors were encountered:
Interesting to add, calling anything without parameters seems to add the null argument (which is not really equivalent to undefined, or absent. this.MenuDynItems.Call("getHeader"); this.MenuDynItems.Call("removeAll");
It seems this is a common practice by Ext.NET that just in this case has resulted in an error.
Found: 4.5.1
Ext.NET forum thread: RemoveAll() causes a Javascript Error on subsequent calls
Calling any containter's
RemoveAll()
method makes it emitremoveAll(null)
unless true/false is provided as paramemter to the call. This makes the client-side code misinterpret thenull
argument as an object and try to referencenull.destroy
, thus triggering a run time exception.Test case to reproduce the issue:
To reproduce the issue, just click twice the 'launch window' button. First time it does not trigger the issue because there's nothing to be removed at all, so the breaking test is never triggered. Second time, as there are items within the container, then the error arises.
This issue is Ext.NET-specific.
The text was updated successfully, but these errors were encountered: