That's a known bug in Explorer. It happens when the containing element that
houses the "buttons" are part of a larger construct and it is not the first
element in the construct. For instance, in a 2-column table, if your buttons
are in the first cell, IE will work perfectly. If they are in the second
cell, they will not. The easiest fix is to declare the <a> element as having
position: relative.
#foobar a {
display: block;
position: relative;}
This fix, however, will cause Dreamweaver MX to prompt you to save your page
even if no changes have been made. To circumvent that, you can use a
conditional statement to present the fix only to IE-PC:
Place this in your page (not inside an external style sheet)
<!--[if gte IE 5]>
<style>
#foobar a {
position: relative;
}
</style>
--
Al Sparber - PVII
http://www.projectseven.com
Dreamweaver Extensions - DesignPacks - Tutorials - Books
---------------------------------------------------------------------
The PVII Newsgroup | news://forums.projectseven.com/pviiwebdev
The CSS Newsgroup | news://forums.projectseven.com/css
---------------------------------------------------------------------
"Plato-vs-Derrida" <webforumsuser (AT) macromedia (DOT) com> wrote
Quote:
Good afternoon,
I'm working with CSS buttons with no images. Just using the display: block
command and hover effects.
In netscape 7 if I mouse over any part of the block the entire button
hightlights, in Explorer, however, the button will highlight only if I mouse
|
over the text. Does anyone know of a work around for this?