I have a page that I just developed using a combination of stylesheets and
div layers. It uses a 'tab' style system placing four div layers in the
same space with visibility 'hidden' and position absolute. They are inside
of another parent div container with position set relative so that as I make
the objects visible, I can also set their position to relative so they
redraw the container size. The parent div is inside of a table cell that is
part of what builds the entire 'tab/index' style GUI on the webpage. In
addition to the selector tabs at the top of this table, I also included a
couple of dynamically generated tabs at the bottom that point to related
content and these bottom tabs are where most of the strange behaviors seem
to be occuring. The page can currently be seen at:
http://www.accuhomes.com/Communities/CommDet.asp
The primary stylesheet that controls the way the bottom tabs display is at:
http://www.accuhomes/styles/master.css
and the contextual stylesheet that builds the properties of the div layers
holding the content areas is:
http://www.accuhomes.com/Communities...ommunities.css
The first strange behavior that I noticed is that the .botTabCls that
includes pseudo classes for a:hover and a:active does not seem to be
applying to these links. Just the body a:hover and a:active, etc. seem to
be applying to it. But if I save the finished page after the asp code
generates it, dreamweaver does properly show those as being the dominant
style properties. (but they still don't work in explorer) I ultimately had
to reset the values for body from white to off-white as a temporary fix.
The second strange behavior someone just pointed out to me this morning.
When you first load the page, the two tabs that show up in the bottom, even
though they contain an <a href="..."> tag around them, will not work as a
link nor will the hover behaviors work at all. I thought this might have
been a result of the hidden div layers at first until I started playing
around with them (trying to set a higher z-index didn't work either).
It seems that if you change the state 'twice' by clicking any of the top
tabs that do that change of state, the links start to work. If you navigate
away then go 'back', they stop working again, but now they only need a
change of state 'once' and they start working as they should - regardless
which <div> is made visible in all cases.
It may or may not be related, but I also noticed that some permissions
seemed to be screwy on the server and I believe I have now reset all of
them. For example, I was having trouble initially retrieving the master.css
directly without getting an error
Can anyone lend me insight as to why these two behaviors may be occuring?
Kathy Lynn
