Library Navigation adding 'library' to path of menu

Question

Not sure what I'm doing wrong here - I created a library item for my navigation to include in all the pages of my site.  Looks like this:
<ul class="menu">
                <li><a href="_products.html">Products</a></li>
                <li><a href="_events.html">Events</a></li>
                <li><a href="_documents.html">Documents</a></li>
                <li><a href="_contact.html">Contact</a></li>
                              </ul>
HOWEVER
When I upload the site none of the links are working because the library item has added /library/ to the link path.  For example the code now looks like this:
<ul class="menu">
                <li><a href="/Library/_products.html">Products</a></li>
               </ul>
Any suggestions?  Much appreciated.

Answer 1

1 - In the past this is how I always created a navigation - using a library item - and I have never had to update them to include 'library' - meaning my experience is that DW would not add the path to the library item but honor the actual code in the library item.  This is why I am wondering if something in CS6 has changed or if I am doing it wrong as I have never seen this before.
Nothing has changed since DW v 2, and perhaps even DW v 1.  What has always been true is that whether you are creating a template or a library item, or a server-side include, or any file, the link in the file MUST BE CORRECT.  If you would open your Library item file in DW, and click on the link, it would fail.  If you would change your link so that it is correct from the Library item's location, and then click on it, it would succeed, and it would succeed in any target file at any location in your site. That has always been the case, and will always be the case.
2 - Is it not a good practice to just let DW make relative links?  Are you recommending that I create full links instead - for example the entire url in the link - http://www.etcetcetc ?
It is a good practice to understand HTML well enough to grasp when one should use ROOT relative links and when one should use DOCUMENT relative links, and the impact that using either can have on your page's functionality.  In your case, you showed a ROOT relative link -
<li><a href="/Library/_products.html">Products</a></li>
My comment is that it's not a good practice to use a ROOT relative link (as opposed to a document relative link) unless you have a good reason to do so, and I could not discern that you did.  The consequence of that root relative link is that it will fail when you preview the page locally unless you are also using temporary files to preview (see Preferences > Preview in browser).  Now - I am not sure if that's actually what you have or if it was just a typo.  The link in the Library item is indeed a document relative link, and I'm not sure how that would become a root relative link in your target file so I suspect now that it might have been a typo....
Anyhow, no, I'm not recommending that the link be an absolute one.  Doing that would eliminate DW's ability to manage the link in the event that you would move or rename the target file.