I have often wondered about this and always just found a workaround, but it would be useful to know what/why this happens.
I have a ‘block’ of buttons on my site. They are all buffered up against each other. However, when I try and make them into rollovers, sometimes I cannot isolate the button from the others either side of it (they are ‘combined’) unless I leave some visible space between them. Other times, I can make them ‘touch’ and it works just fine.
Can anyone tell me what is going on and how I can have the buttons touching, without their rollovers being affected by the others either side of them?
(You can see the buttons on my site www.grantsymon.com. When editing them, the ‘Patate’ button on the english language pages, is the first one coming down from the top, that won’t work properly as a rollover (it combines those either side of it) unless I leave at least a single pixel of space above it.)
But having looked at your site you would probably be better to use the CSS Menu action and set your rollover parameters in the action interface.
Thanks Dave.
I already use the CSS Menus on a mobile site (non-flash). Why do you think they would be better suited to this site? Are suggesting I set it up the same way, without actually using menus in CSS Menus? Just using it to make rollovers?
Are suggesting I set it up the same way, without actually using menus in CSS Menus? Just using it to make rollovers?
Yes - exactly.
Doesn’t this mean that the typeface/font for the text of the buttons would be reliant on what the viewer has installed on their system?
Yes but it is best practice to use HTML text for important stuff like navigation anyway and if you want to use a particular non web safe font then there are Actions to help you do that.
I use Stone Sans Semi on my site, which is uploaded as a gif (I think!) and I was using Helvetica Neue prior to … now having rebuilt my navigation with CSS Menus! You’re quite right, it looks way better. But if I’m going with CSS, then it is important for me to understand the advantages/limitations going forward, e.g. changing typeface on a whim, only to later discover that it’s replaced by Times by 80% of visitors browsers.
