blocks|key|1129944|text|Internet+Explorer。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1129945|更严肃地说，另一个答案中的尾随逗号答案是好的。使用框架可以有所帮助，但它不是一个包罗万象的工具。你将不得不处理跨浏览器的问题。因此，请确保在您关心的所有版本中进行测试。|1129946|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Internet Explorer. 

Ok more seriously, the trailing comma answer in another answer is good. Using a framework can help, but its not a catch-all. You are going to have to deal with cross browser issues. So make sure you test in all versions you care about.

blocks|key|915166|text|注意iframe边框的处理方式(How+to+Remove+an+IFrame+border+in+Javascript)之类的细微差别。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|915167|我想internet-explorer+tag应该会给你很多很好的例子。|915168|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1516803/how-to-remove-border-from-iframe-in-ie-using-javsascript|1|https://stackoverflow.com/questions/tagged/internet-explorer^0|G|18|0|0|2|L|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

Watch out for little differences like the way iframe borders are handled (<a href="https://stackoverflow.com/questions/1516803/how-to-remove-border-from-iframe-in-ie-using-javsascript">How to Remove an IFrame border in Javascript</a>).

I guess the <a href="https://stackoverflow.com/questions/tagged/internet-explorer">internet-explorer tag</a> should give you lots of good examples.

blocks|key|915262|text|在编写一个必须支持IE的站点时，最常见的错误是忘记在每个版本中进行测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|915263|您需要确保您的所有代码都能在IE6+(如果您计划支持它)、IE7、IE8和IE8-+in+-IE7-mode下工作。还有IE9+(现在还处于测试阶段)。|915264|测试多个IE版本的捷径很少，但请注意，它们并不总是给出与真实用户看到的完全相同的结果；唯一确定的方法是在真实的IE版本中实际测试它，无论这有多痛苦。|915265|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The most common mistake while writing a site that has to support IE is to forget to test in every version.

You need to make sure all your code works in IE6 (if you plan to support it), IE7, IE8, and IE8-in-IE7-mode. And also IE9 (which is now in beta).

There area few shortcuts to testing multiple versions of IE, but be aware that they don't always give exactly the same results as what real users will see; the only way to be sure is to actually test it in real versions of IE, no matter how painful that is.

blocks|key|915335|text|使用%2B连接字符串|type|unstyled|depth|inlineStyleRanges|entityRanges|data|915336|var+str="";
for+(var+i+=+0;+i+<+max;+%2B%2Bi)+{
++str+%2B=+somefunction(i);
}|code-block|syntax|javascript|915337|在MSIE上，这可能需要几分钟时间。我曾经做过一个测试，Opera+a+Firefox在几秒钟后就结束了，但MSIE在20分钟后还没有完成！|915338|但是，如果使用数组，则MSIE速度很快：|915339|var+str+=+[];
for+(var+i+=+0;+i+<+max;+%2B%2Bi)+{
+++str.push(+somefunction(i));
}
str+=+str.join("");|915340|很抱歉，我现在找不到关于它的帖子。|915341|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|U|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Concatenate strings with +

<pre><code>var str="";
for (var i = 0; i &lt; max; ++i) {
 str += somefunction(i);
}
</code></pre>

On MSIE it can take several minutes. I once did a test where Opera an Firefox where finished after a few seconds, but MSIE hadn't finished after 20 MINUTES!

However, if using an array, MSIE was fast:

<pre><code>var str = [];
for (var i = 0; i &lt; max; ++i) {
 str.push( somefunction(i));
}
str = str.join("");
</code></pre>

Sorry, but can't find the post I made about it right now.

blocks|key|915422|text|IE不支持自定义事件，只支持DOM事件(是的，即使在9测试版中也是)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|915423|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

IE does not support custom events, only DOM events (yes even in 9 beta).

blocks|key|915524|text|IE+(8和更低版本，不确定9)不能处理访问字符串中的字符，如数组，如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|915525|var+str+=+'abc';
var+c+=+str[2];
alert(c)|code-block|syntax|javascript|915526|在大多数浏览器中，这将警告“c”，但IE警告“未定义”。出于跨浏览器的原因，我们应该使用charAt函数：|915527|var+str+=+'abc';
var+c+=+str.charAt(2);
alert(c)|915528|这也会在IE中警告'c‘。|915529|另一个小区别是对象和数组中的尾随逗号。这在大多数浏览器中都是有效的，但会在IE中引发错误：|915530|ar+=+[1,2,3,]|915531|而且还|915532|ob+=+{name:'janet',+surname:'walker',}|offset|length|style|CODE|915533|如果你没有意识到这一点，你可能会非常恼火。这两个问题可能是我经常遇到的问题，因为我习惯了python，但它仍然值得注意。|915534|entityMap^0|0|0|0|0|0|0|0|0|0|12|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|14|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|16|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|18|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|19|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1A|8|@$U|1B|V|1C|W|X]]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1D|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|11|$]]

IE (8 and lower, not sure about 9) cannot handle accessing characters in strings like arrays, as in:

<pre><code>var str = 'abc';
var c = str[2];
alert(c)
</code></pre>

In most browsers this will alert 'c', but IE alerts 'undefined'. For cross-browser reasons one should rather use the charAt function:

<pre><code>var str = 'abc';
var c = str.charAt(2);
alert(c)
</code></pre>

This will alert 'c' in IE as well. 

Another small difference is that of the trailing comma in objects and arrays. This is valid in most browsers, but raises errors in IE:

<pre><code>ar = [1,2,3,]
</code></pre>

and also 

<code>ob = {name:'janet', surname:'walker',}</code>

which can be quite irritating if you're not aware of it. Both these problems are probably something I run in frequently because I'm used to python, but it's still worth looking out for.

blocks|key|915614|text|除非打开控制台窗口，否则IE+7/8无法理解console.log/dir。如果您在prod环境中留下任何JS，这很容易破坏JS。一直都有|type|unstyled|depth|inlineStyleRanges|entityRanges|data|915615|if(window.console)
+++console.log('Hello+World')|code-block|syntax|javascript|915616|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

IE 7/8 fails to understand console.log/dir unless console window opened. This can easily break your JS if you leave any in the prod environment. Always have

<pre><code>if(window.console)
 console.log('Hello World')
</code></pre>

I'm about to start coding a new, javascript-heavy website, but before I start I'd like to minimize my debugging time in Internet Explorer by knowing beforehand what the quirks are. I'm not planning to worry too much about IE6.

What are the common mistakes/differences to avoid in javascript code that work fine in other browsers, but break in Internet Explorer?

What are the common mistakes to avoid when coding javascript for Internet Explorer?

我即将开始编写一个新的、大量使用javascript的网站，但在开始之前，我想通过预先了解这些怪癖来最小化我在Internet Explorer中的调试时间。我不打算太担心IE6。javascript代码中常见的错误/差异是什么，这些错误/差异在其他浏览器中工作良好，但在Internet Explorer中中断？

问在为Internet Explorer编写javascript时，需要避免的常见错误是什么？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在为Internet Explorer编写javascript时，需要避免的常见错误是什么？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在为Internet Explorer编写javascript时，需要避免的常见错误是什么？
EN