Curious link problem

[LEICJDN1]

Hello all,

Have noticed while checking site in Netscape 7.02 that some links just do not work, but most do!

If you go here:

http://www.cardioweb.co.uk/mrcpstartpage.html

and try the 'start here' link at the bottom right of the main panel. In IE 6.02 it works fine. All other links on the page work fine as well in NS 7.02 except that one!

Have checked the code and cannot fathom why it does not work. If I try and edit the page in NS it does find the <a> tag and highlight it.

Any ideas??

 

[Tracey]

I had a look it works on NS 7.1, IE6, but not mozilla 1.0 so i had a play and it seems to be your position:absolute; attribute for that div.

i set a new style
h5.righter {
position:relative;
bottom: -13px;
right: -1px;
width: 100%;
margin: -9px 0px 1em;
height: 20px;
padding-top:2px;
text-align: right;
background: #333;
color: #ffffff;
letter-spacing: 0.1em;
text-transform: lowercase;
font-weight:bold;
font-size: 12px;
font-family: arial, sans-serif;
white-space: normal;
z-index:10;
}

which seems to work, try it on NS 7.02

Tracey
Remember... True happiness is not getting what you want...

Its wanting what you have got!

 

[Vragabond]

Hmmm strange problem. The only thing I did not understand about your source is the part in bold:

<h5 class=&quot;left&quot;><a href=&quot;& nbsp;&quot;></a></h5><h5 class=&quot;right&quot;><a href=&quot;mrcp/mrcpmenupage.html&quot;>start here</a> </h5>

What exactly is this doing here? I am sure there is no need for this, if you need to put something in the left <h5> put only   without the empty link. Maybe this could be throwing off Netscape.

 

[LEICJDN1]

Thanks, will try the amended CSS code.

Vragabond, I was working through various problems and that was just a way to ensure that having an empty link was not the issue so I shoved a backspace in the href, and it just so happens that was what was there when I posted. It had previously just read <a href=&quot;&quot;></a> - I left the link tag there as I may go back and put something in.

Will let you know if thee CSS change works or not.

Thanks.

 

[LEICJDN1]

Hmmm... Thinking about it a little more I don't think it can be that CSS code as some of the links done in the same manner work quite normally. Also, chaning the position to relative screwed my layout in IE 6.

Compare the bottom right links at:

http://www.cardioweb.co.uk/index.html

and

http://www.cardioweb.co.uk/ecg/ecgstartpage.html

which work fine...

against

http://www.cardioweb.co.uk/mrcpstartpage.html

and

http://www.cardioweb.co.uk/mrcp/questions/part1/part1startpage.html

which don't!!

Maybe it is a NS 7.1 bug although I see you say it also fails in Mozilla 1.0.

Any more ideas ??

 

[Tracey]

Yes, the relative did change the positioning, thats why the difference in width.

did you try that? did your link work with the relative? Certainly fixed the problem in mozilla


Tracey
Remember... True happiness is not getting what you want...

Its wanting what you have got!

 

[LEICJDN1]

Tracey,

Tried your suggestion. Fiddled with the CSS layout to get the desired appearance in NS, but link still failed. Plus, I cannot see how a CSS problem could explain the differences between very similar pages.

Thanks for your help though.

I wonder if this is just NS 7.1 playing me around, but if anyone can explain this curious behavious then I would be very grateful!

JDN

 

[Tracey]

of course NS is fooling around. obviously a different fooling to that of mozilla tho. sorry i couldnt help you solve this.

Tracey
Remember... True happiness is not getting what you want...

Its wanting what you have got!

 

[ChrisHirst]

I've had similar problems, It will be something about the z-index that will be the problem and the navigation is in a lower layer.

IE is the one that will be fooling you by handling something that is not strictly compliant. Mozilla and NS being strict will be the ones that are behaving correctly.



Chris.

Indifference will be the downfall of mankind, but who cares?

 

[LEICJDN1]

Will fiddle with the layer sequence, and let you know.

 

[LEICJDN1]

Changing the layer sequence had no effect.

After much comparing of the two files, it seems the key difference was in the end code.

If it was:

</div>

</body>
</html>

then the link failed, but changing to:

</div>
<br />
</body>
</html>

cured the issue!

Bizzare, I cannot explain why that should have an effect. Please enlighten me if you can!

 

[ChrisHirst]

What that would do is increase the body length one line maybe the bottom margin of the body was overlapping the last line in the preceding <div>.

I've just come across the same kind of thing with a new site I'm doing, where I could never scroll to the end of the pages in NS and Mozilla but ok in IE. There would always be a couple of lines that were hidden, the solution to this was to increase the height of the bottom div by about 30px.

I've just tried reducing the browser window in NS on your site and the same thing happens, you can't scroll beyond about halfway down the bottom bar. Another one to add to the list of tricks.



Chris.

Indifference will be the downfall of mankind, but who cares?

 

[LEICJDN1]

Will increase bottom div!

Thanks.