Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy would background-attachment:scroll not work?
    primarykey
    data
    text
    <p>I have an absolutely positioned DIV with overflow auto. When I scroll down, the background clearly looks fixed, even though the default for everything on my site is scroll. It still had this behavior when I tried both ways of defining the background on the DIV:</p> <p><code>background-attachment: scroll;</code> <code>background: url() repeat top center scroll #000</code></p> <p>Extremely lost. Thought it might be because it was absolutely positioned DIV but even when I undid that, it still failed. Problem in FF, Safari, Chrome, and IE.</p> <p>UPDATE: Here is the latest code I tried.. on the actual site the CSS is in a file that I point to in a head tag. </p> <pre><code>&lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"&gt; &lt;html xmlns="http://www.w3.org/1999/xhtml"&gt; &lt;body&gt; &lt;style type="text/css"&gt; .template-body { background-attachment:scroll; background-color:#151515; background-image:url("http://www.fake.com/images/2183ba03681e577511e6589e554b7a86.jpg"); background-position:center top; background-repeat:repeat; } &lt;/style&gt; &lt;div class="template-body" style="position: absolute; margin: 0px; left: 332px; right: 0px; top: 93px; bottom: 0px; width: 1094px; z-index: 1; visibility: visible; display: block; background-color: rgb(21, 21, 21); height: 696px;"&gt; &lt;div&gt; Here lies all the content that makes .template-body scroll &lt;/div&gt; &lt;/div&gt; &lt;/body&gt; &lt;/html&gt; </code></pre> <p>Attempting to set heights in firebug on the inner/content DIV did not help in any way.</p>
    singulars
    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