Internet Explorer的操作已中止和延迟问题 [英] Internet Explorer's Operation Aborted and Latency Issue

问题描述

如果你不知道操作中止错误是什么，这里有一个Microsoft知识库文章吧，的 http://support.microsoft.com/default.aspx/kb/927917 。还有这件事，但是职位吨为它的发生简单的答案是这样的;错误仅当您尝试试图操纵元素加载之前，通过JavaScript操纵DOM元素出现。

If you don't know what the operation aborted error is, here's a Microsoft KB Article about it, http://support.microsoft.com/default.aspx/kb/927917 . There's also tonnes of posts about it but the simple answer for it's occurrence is this; the error only occurs if you try to manipulate a DOM element via JavaScript before the element you are trying to manipulate is loaded.

我知道Internet Explorer的（IE）臭名昭著的操作已中止是怎样发生的，并知道如何解决它。我的问题是一个很奇怪的场景。本地测试和开发机上的IE7，我从来没有得到中止操作错误（这两个网站运行的HTTP）。

I know how Internet Explorer's (IE) infamous Operation Aborted occurs and know how to fix it. The problem I have is a very weird scenario. Testing locally and on a development machine with IE7, I never ever get the operation aborted error (both sites running as http).

不过对客户的试验场它发生的所有时间。不幸的是我的测试环境是不一样的客户端的测试环境，因此，增加了一些变量的组合，但我看到的主要区别是，客户端的测试现场使用SSL

However on our client's testing site it occurs all the time. Unfortunately my testing environment is not the same as the client's testing environment, so that adds some variables to the mix, but the main difference I see is that the client's testing site is using SSL.

有没有人曾经有过的操作已中止错误仅用于SSL的网站？

Has anyone ever had the Operation Aborted error only for an SSL site?

这在我脑海中突然出现的另一个想法是，这是一个延迟的问题。本地网站的负载几乎是瞬间而在我的客户的测试网站，页面加载速度较慢。因此，考虑到这一点，我得到了提琴手运行和模拟本地或我们自己的测试服务器的性能在老同学的调制解调器的速度运行，仍然没有中止操作错误。

The other thought that popped in my head was that it was a latency issue. Locally the site loads up almost instantaneously whereas on my client's testing site, the page loads slower. So with that in mind, I got Fiddler running and simulated the performance to run at old school modem speeds, still no operation aborted error locally or on our own testing server.

FYI：该网站是使用ASP.NET AJAX 1.0的扩展的ASP.NET 2.0网站。有问题的网页也有它的AJAX Control Toolkit中的级联降下来了。

FYI: The site is an ASP.NET 2.0 Site using ASP.NET AJAX Extensions 1.0. The page with the issue also has the AJAX Control Toolkit's Cascading Drop Down on it.

是的，据我可以告诉大家，操纵DOM是标记的结束，而不是开始。

And yes as far as I can tell all JavaScript that manipulates the DOM is at the end of the markup, not the beginning.

任何帮助或意见是很大的AP preciated。

Any help or comments is greatly appreciated.

推荐答案

在网上淘，我发现这个问题后嘛。它与在的ASP.NET AJAX客户端框架中的错误的事情。

Well after scouring the Internet I found the issue. It has to do with a bug in the the ASP.NET AJAX client-side framework.

我要套用我发现了什么：

I'll paraphrase what I found:

问题是发生是由于一个Internet Explorer / ASP.Net AJAX错误的竞争条件。当应用程序有ASP.Net AJAX的服务器控件的网页上显著号遇到此问题的概率增大。这个问题在这里解释的http://seejoelprogram.word$p$pss.com/2008/10/03/fixing-sysapplicationinitialize-again 。我加入此修复程序，我工作的项目。

The issue is a race condition that occurs due to an Internet Explorer/ASP.Net AJAX bug. The probability of encountering this issue increases when the application has a significant number of ASP.Net AJAX enabled server controls on the web page. The issue is explained here, http://seejoelprogram.wordpress.com/2008/10/03/fixing-sysapplicationinitialize-again . I have added this fix to the project I'm working on.

此修复程序仍然需要，如果使用ASP.NET 3.5 SP1。

This fix is still required if using ASP.NET 3.5 SP1.

这篇关于Internet Explorer的操作已中止和延迟问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！