{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 看我几分像从前 的问题《Is there a good reason that a form tag should not》','https://www.manongdao.com/q-1054879.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
Is there a good reason that a form tag should not exist in the head tag?
I was looking at this http://www.w3.org/html/wg/drafts/html/master/forms.html#the-form-element but I could not find anything related to this question.
This works for me:
<head runat="server">
<title></title>
<form id="form1" runat="server">
<asp:ScriptManager ID="ScriptManager1" runat="server"></asp:ScriptManager>
</form>
<link rel="stylesheet" href="http://ajax.aspnetcdn.com/ajax/jquery.mobile/1.2.0/jquery.mobile-1.2.0.min.css" />
<script src="http://ajax.aspnetcdn.com/ajax/jQuery/jquery-1.8.2.min.js"></script>
<script src="http://ajax.aspnetcdn.com/ajax/jquery.mobile/1.2.0/jquery.mobile-1.2.0.min.js"></script>
</head>
Thanks in advance.
If you look at http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2014 in a browser other than IE (which has a very strange bug here), you will see that your form element is not in fact inside the head element. When the parser sees the
<form>tag, it automatically closes the<head>element, creates the<body>element and puts the<form>element and all subsequent elements inside that<body>element.Because this behaviour is necessary for backward compatibility with existing web pages, the spec can't be changed to allow
<form>elements in head, even if there were a good use case for doing so.HTML intended for display belongs in the
<body>tag.There are some browsers that will still display some tags that are put in the
<head>tag, but that is not where it belongs and you are asking for interoperability problems if you put it there.In the spec link that you referenced, it says that
<form>tags go whereflow contentis expected. If you click onflow content, it refers to elements used in the body of documents. The body is what is in the<body>tag.