Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Edit:</strong></p> <p>Yes, this is exactly the problem. I just checked the link you posted, and the browser is looking for an image located at: <a href="http://www.156.onl.checit.info/CSS/images/pg_menu_bg.png" rel="nofollow noreferrer">http://www.156.onl.checit.info/CSS/images/pg_menu_bg.png</a> - which doesn't exist.</p> <p>See that "CSS" in there? I'm 99% sure that's unintentional. It's an absolute/relative path issue. Read on...</p> <hr> <p>if your image is not appearing I'm gonna go out on a hunch and say it's because your image paths are messed up.</p> <p><strong>Solution:</strong></p> <p>This:</p> <pre><code>/* ABSOLUTE PATH solution */ background-image: url(/images/pg_menu_bg.png); </code></pre> <p>or maybe even this (depending on your file structure):</p> <pre><code>/* RELATIVE PATH solution. This is FROM YOUR CSS FILE.*/ background-image: url(../images/pg_menu_bg.png); </code></pre> <p><strong>Explanation:</strong></p> <p>There is a big difference between:</p> <pre><code>background-image: url(images/pg_menu_bg.png); </code></pre> <p>and</p> <pre><code>background-image: url(/images/pg_menu_bg.png); /* note the leading slash */ </code></pre> <p>The leading slash means an <em>absolute path</em> (ie. "path from your root domain url"), whereas no leading slash means a <em>relative path</em> (ie. "relative to the location of this file, in this case, your CSS file").</p> <p>That means, presuming you have a file structure like this:</p> <pre><code>root | ----images | pg_menu_bg.png | ----css | mycss.css </code></pre> <p>from your css file, calling:</p> <pre><code>background-image: url(images/pg_menu_bg.png); </code></pre> <p>actually results in:</p> <pre><code>http://yourdomain.com/css/images/pg_menu_bg.png /* note the "css" */ </code></pre> <p>whereas calling:</p> <pre><code>background-image: url(/images/pg_menu_bg.png); </code></pre> <p>results in:</p> <pre><code>http://yourdomain.com/images/pg_menu_bg.png </code></pre> <p>So I think you need to have a look at your directory structure, and work from there. My guess is you need to use <em>absolute paths</em>.</p> <p>But if you wanted to use <em>relative paths</em> with the dummy file structure above, you can use:</p> <pre><code>background-image: url(../images/pg_menu_bg.png); /* ".." means "parent directory" </code></pre> <p><strong>More info:</strong><br /><a href="https://stackoverflow.com/questions/940451/using-relative-url-in-css-file-what-location-is-it-relative-to">Using relative URL in CSS file, what location is it relative to?</a></p> <hr> <p><strong>Second problem:</strong></p> <p>You have another issue, this style:</p> <pre><code>* { background-color: #6FF; margin: 0px; padding: 0px; } </code></pre> <p>This style applies a blue background TO EVERY ELEMENT. So even if your paths to that background image are ok, they're being hidden by foreground elements with blue backgrounds.</p> <p>Try change <code>*</code> to <code>body</code>:</p> <pre><code>body { background-color: #6FF; margin: 0px; padding: 0px; } </code></pre> <p><strong>Note:</strong> if you actually want a <code>margin:0;</code> and <code>padding:0;</code> on every element, leave the above style as you had it (but remove the <code>background-color</code>), and define a new <code>body</code> style and put the <code>background-color</code> in there instead. Like this:</p> <pre><code>* { margin: 0px; padding: 0px; } body { background-color: #6FF; } </code></pre>
    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. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      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