Databases
StackOverflow2013
Postsdbo
POIE 9 BoxModel padding/spacing issue when changing localhost to computername
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIE 9 BoxModel padding/spacing issue when changing localhost to computername
    text
    copied!<p>when I run my site on for example: /localhost/Test then the box-model and table borders/padding/spacing etc... looks normal.</p> <p>Example IE9 Box Model OK localHost: <a href="http://www.flickr.com/photos/cenesam/6243269622/in/photostream" rel="nofollow">http://www.flickr.com/photos/cenesam/6243269622/in/photostream</a></p> <p>When I run the same test site on: /my computer name/Test then IE9 goes wacky and the box-model increases padding / spacing etc...</p> <p>Example IE9 BoxModel NOK Computername: Url: <a href="http://www.flickr.com/photos/cenesam/6242752657/in/photostream" rel="nofollow">http://www.flickr.com/photos/cenesam/6242752657/in/photostream</a></p> <p>Does anyone recognize this behaviour and knows how to deal with this? I've included 2 sample pictures to show the visual problem. One is with localhost one is with computer name.</p> <p>Any ideas are much appreciated. Thanks, Joost</p> <p>Finaly found the answer somewhere on the web. Spudley (thank you!) pointed me to the right direction. This meta tag was definitly the answer!!</p> <p>But what is important that IE NEEDS this tag to be the FIRST one in the Head section. My site uses a theming engine which parses the styles in the head tag and therefore it was not working.</p> <p>Now I'm overriding this in web.config (webserver section) by:</p> <pre><code>&lt;httpProtocol&gt; &lt;customHeaders&gt; &lt;remove name="X-UA-Compatible" /&gt; &lt;add name="X-UA-Compatible" value="IE=Edge" /&gt; &lt;/customHeaders&gt; &lt;/httpProtocol&gt; </code></pre> <p>And now it finaly works again. Thank you all for thinking with me!</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

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