Note that there are some explanatory texts on larger screens.

plurals
  1. POX-UA-Compatible meta tag in ASP.NET 4.0 site doesn't work
    primarykey
    data
    text
    <p>I am writting an asp.net 4 application and i want my application to work in compatiable mode (IE8 AND IE9) .</p> <p>I have used following meta tag so far and it is not working. (HAVE TRIED WITH "IE=8" AS WELL)</p> <p>I have followed this thread but no luck so far;</p> <p><a href="https://stackoverflow.com/questions/3368220/setting-x-ua-compatible-meta-tag-in-asp-net-4-0-site-doesnt-work">Setting X-UA-Compatible meta tag in ASP.NET 4.0 site doesn&#39;t work</a></p> <p>I don't know if it is a known bug? <a href="http://connect.microsoft.com/VisualStudio/feedback/details/581278/setting-x-ua-compatible-meta-tag-in-asp-net-4-0-site-doesn-t-work-yes-it-s-at-the-top#" rel="nofollow noreferrer">http://connect.microsoft.com/VisualStudio/feedback/details/581278/setting-x-ua-compatible-meta-tag-in-asp-net-4-0-site-doesn-t-work-yes-it-s-at-the-top#</a></p> <p>ADDED:</p> <p>If i remove 'StyleSheetTheme' from the page tag then it renders in compatiable mode.</p> <ul> <li></li> </ul> <p>Any way to fix it?</p> <p><strong>Possible solution:</strong></p> <p>It works if i add meta tag dynamically on the page load event and leven the stylesheet value in the page tag.</p> <blockquote> <p>Dim metaTag As New HtmlMeta() </p> <p>metaTag.Attributes.Add("http-equiv", "X-UA-Compatible") </p> <p>metaTag.Attributes.Add("content", "ID=EmulateIE7")</p> <p>Page.Header.Controls.AddAt(0, metaTag)</p> </blockquote> <p><strong>Do you think its a right way of doing it? any other better solution?</strong></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload