views:

46

answers:

2

I am developing a ASP.Net web site and my page works normally in IE/Firefox/Opera

This is the page source code.

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"&gt; 
<html xmlns="http://www.w3.org/1999/xhtml"&gt; 
<head><title> 
 Content Navigation
</title><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 
    <script language="javascript" type="text/javascript" src="/js/jquery/jquery-1.4.2.min.js"></script> 
</head> 
<body> 
dd222222222222222222222
    <div id="content-tree"> 
    </div> 



</body> 
</html>

It is simple, isn't it? But in my Chrome 6.0.472.53, I always get a white page, just a white page, nothing else.

After click the "Inspect Element" in context menu, here is the HTML DOM structure I see

<html xmlns="http://www.w3.org/1999/xhtml"&gt;&lt;head&gt;&lt;title&gt;
 Content Navigation
</title><meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <script language="javascript" type="text/javascript" src="/js/jquery/jquery-1.4.2.min.js"></script></head></html>

Hmmm, the body is gone! If I remove the jquery js reference line, body comes back

Is this a bug in Chrome or mine? my web host is IIS7.1

Thank you for any help

Update:

I have reported this issue to Chrome Help And here is the screenshot:

Correct: http://img128.picfoco.com/img.php?id=1274578614&amp;q=&amp;jump=5176678858&amp;ru=

Incorrect: http://img122.picfoco.com/img.php?id=778329008&amp;q=&amp;jump=4680429165&amp;ru=

A: 

Not really sure, I can't replicate the issue in my Chrome build. Can you try replacing your jQuery ref to the following from the Google repository? If it does the same, possibly try degrading to 1.3 and see if that produces the same results.

<script language="javascript" type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js" ></script>
jon3laze
Test with this CDN link, same result If I added this line, white page;If I remove this line, content is shown up;
Jerry
A: 

I find the reason now

because there is a "Connection:Close" in the response HTTP HEAD, and it only affects Chrome

After remove this head, everything is fine

Jerry

related questions