StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><strong>A couple of possibilities:</strong></p> <p><strong>1)</strong> The <code>.htc</code> file isn't being served with the correct mime-type. From the <a href="http://css3pie.com/documentation/known-issues/#content-type" rel="nofollow">CSS3 PIE Known Issues</a></p> <blockquote> <p>IE requires that HTC behaviors are served up with a content-type header of "text/x-component", otherwise it will simply ignore the behavior. Many web servers are preconfigured to serve the correct content-type, but others are not.</p> <p>If you have problems with the PIE behavior not being applied, check your server configuration and if possible update it to use the correct content-type. For Apache, you can do this in a .htaccess file:</p> </blockquote> <pre><code>AddType text/x-component .htc </code></pre> <p>Is the problematic behavior on a server running IIS? If so, what version of IIS? <a href="http://technet.microsoft.com/en-us/library/bb742440.aspx" rel="nofollow">IIS 5 or higher should have the mime-type for .htc configured correctly</a></p> <p><strong>2)</strong> Perhaps it's a path problem, again from the <a href="http://css3pie.com/documentation/known-issues/#relative-paths" rel="nofollow">CSS3 PIE known issues</a></p> <blockquote> <p>Relative paths</p> <p>There are two main issues related to relative paths in CSS: The behavior URL</p> <p>IE interprets the URL for the behavior property relative to the source HTML document, rather than relative to the CSS file like every other CSS property. This makes invoking the PIE behavior inconvenient, because the URL has to either be:</p> <blockquote> <p>Absolute from the domain root — this makes the CSS not easily moveable between directories — or, Relative to the HTML document — this makes the CSS not easily reusable between different HTML files.</p> </blockquote> <p>URLs in PIE-interpreted CSS properties</p> <p>PIE does not parse the CSS stylesheets (to do so would be unacceptably slow); it lets IE handle the parsing, selector querying, cascading, etc. and then simply asks it for the resulting property values. This means that when PIE gets a property value, it has no knowledge of the context from which that value originated.</p> <p>As a result, for properties which contain URL values (such as border-image or -pie-background), PIE cannot resolve those URLs relative to the CSS file in which they appear. It resolves them instead relative to the JavaScript execution context, which is the location of the source HTML document.</p> </blockquote>

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