Hi,

I am working on developing a page here:
www.iongeo.com/aram_test_dev/secondary.html

A friend pointed out that the navigation bar isn't showing up in google chrome, even though it's working in IE and FF.

I am a little stumped as to what the issue is, can someone please take a look and let me know?

Here's the code for the nav bar:

<div id="navbar2">
<ul>
<li><a href="link1.html">Aries II</a></li>
<li><a href="link2.html ">Customer Service</a></li>
<li><a href="link3.html ">About ARAM</a></li>
<li><a href="link3.html ">Rental Services</a></li>
<li><a href="link3.html ">Contact Info</a></li>
<li><a href="link3.html ">About ION</a></li>
</ul>
</div>

Here's the CSS for the nav bar:

div#navbar2 {
    height: 30px;
    width: 100%;
    border-top: solid #000 1px;
    border-bottom: solid #000 1px;
    background-color: #D31145;
}
div#navbar2 ul {
    margin: 0px;
    padding: 0px;
    font-family: Arial, Helvetica, sans-serif;
    font-size: small;
    color: #FFF;
    line-height: 30px;
    white-space: nowrap;
    float: right;
}

div#navbar2 li {
    list-style-type: none;
    display: inline;
}
div#navbar2 li a {
    text-decoration: none;
    color: #FFF;
    padding-top: 7px;
    padding-right: 10px;
    padding-bottom: 7px;
    padding-left: 40px;
}
div#navbar2   li a:hover {
    color: #000000;
}

div#navbar2 lia:link {
    color: #FFF:
}
div#navbar2 lia:visited {
    color: #CCC;
}
div#navbar2 lia:hover {
    font-weight: bold;
    color: #FFF;
    background-color: #3366FF;
}

Any help would be greatly appreciated.

Thanks.

Im not sure if this would be the problem, but I noticed that the last 3 definitions have selectors that say "lia:hover". Try adding a space between the "li" and the "a:hover". It might be confusing the browser. So that part should look like: "li a:hover"

Thanks for your response,

I deleted any references of li:a, but it still looks like the issue is happening in google chrome only.

hmm... I am really stumped why google chrome isn't liking the css for it.

Chrome is based on WebKit, just like Safari, so the problem is likely also occurring in Safari 3 as well. You might want to search for bugs/hacks for Safari and/or Webkit.