{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', '推荐 小情绪 Triste * 的问题《Which X-UA-Compatible takes precedence? Http-heade》','https://www.manongdao.com/q-93630.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
As the question states basically. If you have X-UA-Compatible in both your HTTP headers and a meta tag on your document, and they conflict, which one gets respected by IE?
相关问题
- How to fix IE ClearType + jQuery opacity problem i
- Is TWebBrowser dependant on IE version?
- PHP Empty $_POST
- IE dropdown z-index bug
- Multiple cookies with same name
相关文章
TL;DR: The meta tag wins
I found the following (updated) flowchart
here(link is broken) and associated blog post that provides an explanation of how IE9 determines document mode: