title: ExtJS: autoLoad does not work in IE
body: <p>Using ExtJS 2.2.1, I've got a container element which is supposed to load a piece of HTML from the server using:</p>
  
  <pre><code>autoLoad: { url: 'someurl' }
  </code></pre>
  
  <p>This works fine in Firefox, but for IE7 this results in a syntax error in ext-all-debug.js at line 7170:</p>
  
  <pre><code> this.decode = function(json){   
     return eval("(" + json + ')');
   };
  </code></pre>
  
  <p>I fixed this by turning that function into this:</p>
  
  <pre><code> this.decode = function(json){   
      return eval('(function(){ return json; })()');  
   };
  </code></pre>
  
  <p>Then the autoLoad works well in both browsers, but then there's some odd bugs and besides, you really don't want to fix this in the ExtJS library as it will be unmaintainable (especially in the minified ext-all.js which is like half a megabye of Javascript on a single line). </p>
  
  <p>I haven't been able to find a lot about this bug. </p>
  
  <p>Variations that I've tried:</p>
  
  <pre><code>// With &lt;script&gt; tags around all the HTML
  autoLoad: { url: 'someurl', scripts: true }
  // With &lt;script&gt; tags around all the HTML
  autoLoad: { url: 'someurl', scripts: false }
  </code></pre>
  
  <p>And visa versa without the <code>&lt;script&gt;</code> tags. There isn't any Javascript in the HTML either, but it should be possible, because eventually we will use Javascript inside the returned HTML. </p>
  
  <p>The problem isn't in the HTML because even with the simplest possible HTML, the error is the same. </p>
  
  <p>UPDATE - Response to donovan:</p>
  
  <p>The simplest case where this is used is this one:</p>
  
  <pre><code>changeRolesForm = new Ext.Panel({
          height: 600,
          items: [{ autoScroll: true, autoLoad: WMS.Routing.Route("GetRolesList", "User")   + '?userID=' + id}]
      });
  </code></pre>
  
  <p>There is no datastore involved here. The response-type is also <code>text\html</code>, not json, so that can't be confusing it either. And as said, it's working just fine in Firefox, and in Firefox, it also executes the same <code>eval</code> function, but without the error. So it's not like Firefox follows a different path of execution, it's the same, but without the error on <code>eval</code>.</p>