Well if you spent some time poring over the forum you'd be sure to find
numerous posts regarding random odd problems that in the end I resolve by
finding that the customer was using the background/master page.
And in tests I've done across the versions I've never had 100% accurate
results when implementing it in a web publication. Now when I've on occasion
asked MS about this I've been told that that function is designed for use on
print publications versus web publications. Though on one occasion I was
told by MS testing that they could not find a problem with using it. The
short answer to your question is that based on my experience it's best to
NOT use it.

In your case the graphic menu kept you from doing what you wanted. Of course
you had done that to do something else you wanted. Namely drop underlining
from the hyperlinks. That's an unnecessary workaround, the proper way to
implement that is thru a CSS snippet, which I provided on your page. I guess
my short answer would be, why do you need it to be graphical? If you want a
button based menu, then sure, it makes sense that it's a graphical menu. But
if you have a text menu, why make that complicated, leave text as text. Also
it's just one more thing to slow down page load time, Publisher has enough
images it's loading already. But if you've got a design decision that you
feel justifies it, well then do what you want.

David:
http://www.microsoft.com/communities/mvp/mvpdetails.mspx?Params=%7eCMTYDataSvcPa
rams%5e%7earg+Name%3d%22guid%22+Value%3d%22bf6cf53b-b656-4f9b-81ee-d2e4a2589728%
22%2f%5e%7esParams%5e%7e%2fsParams%5e%7e%2fCMTYDataSvcParams%5e

Syd aka Analog:
http://www.logwell.com/WRFN/index.html (Please note: I *think* this is Syd
and the photo is several years old.)

Take your pick  ;-)