TYPO3 Core

had same problem with ie7; the following workaround fixed it, though I think it is not the solution to the source of the problem (why is path undefined?):

Index: typo3/contrib/extjs/ext-all-debug.js
===================================================================
--- typo3/contrib/extjs/ext-all-debug.js    (revision 10523)
+++ typo3/contrib/extjs/ext-all-debug.js    (working copy)
@@ -1121,7 +1121,12 @@
             if(typeof root == "string"){
                 root = document.getElementById(root);
             }
-            var paths = path.split(","),
+            
+            var paths = new Array();
+            if(typeof path != "undefined") {
+                paths =  path.split(",");
+            }
+            
                 results = [];

we can't patch ExtJS core.

Please apply patch from #13580 first and try again - i have the feeling that all these errors have the same source: invalid HTML

Hi,

sorry for the late response, i did not work on that project for some weeks.

@Steffen: i updated to 4.5.3-dev from git and also to the git versions from workspaces and version where the patch you mentioned is already applied. That did not fix the issue.

Patching ExtJS however worked. Thanks Thomas!

IE (especially 6) is really a mystery. The JS engine has some big quirks and e.g. likes to loose variables. I fixed a core-bug in IE6 some time ago, where a callback function was not able to access a param that was passed to the surrounding function. Saving the param to a local variable however fixed that. Maybe something similar is going on here.

We use the patched ExtJS source since then and did not spend any more time on that.