View Full Version : CSS / DHTML Hybrid Navigation Bar

02-16-2003, 04:34 AM
This is what I'm making at the moment - but I have a CSS-positioning conflict, that perhaps some of you can advise upon.

It's all explained on the page http://www.brothercake.com/scripts/navmeister/page.php

02-18-2003, 09:48 PM
<bump/> :D

Perhaps I asked too much in one question ... so I'll precis:

I have a positioning discrepancy between

- mozilla1.2a+; and
- all other versions of mozilla, ie5+, opera 7 and safari.

I want forward compatibility, so I need to decide which is right and which to hack.

How can I find out which is right? Is there some kind of tool or empirical method by which I can test the specifications for behaviour in a particular circumstance? Would it help to sit and read the CSS specs?

Or do I have to guess, and either ...

1 - assume that mozilla is right and all the others are wrong, and code a hack for the benefit of the others; or

2 - assume that mozilla is wrong, and code a hack just for it.

I'm leaning towards the latter ... but I would appreciate input on this.

Given that - does anyone know of a CSS hack that identifies either of these discreet groups?

02-18-2003, 10:26 PM
I am unaware of any CSS parser hacks you can use to make Mozilla not see a rule. However, there are hacks for every single other browser, even Safari.

Anyway, try this:

ul.navmeister > li {
position: relative;

ul.navmeister ul {
top: 0;

Inserted things have been italicized. It looks to me like Mozilla 1.2a+ is picking up the line break preceding the nested <ul>?

02-18-2003, 11:16 PM
well that solved the discrepancy .... but now the menus are underneath their parent ... and have different browser discrepancies :(

at least it's progress :rolleyes: Just for fun, I tried removing all the line breaks from the list HTML ... didn't help mozilla, but it did break IE completely!

Thanks anyway - I may end up having to hack after all. What i'd really like to know is which one is correct? That way, I can build forward compatibility into my hacks :)

02-19-2003, 07:13 PM
Success of a kind anyway ... I just downloaded the latest Phoenix nightly (slippery slopes those nightly builds ...;)) and it's based on 1.3b .. and guess what ... it's fine :) Someone else sent me a screenshot of moz1.3b on OSX and it's also fine.

So if 1.2a and 1.3a are the only offenders, the solution is clearly to apply the global margin and just don't worry about it.

How many people are going to be using an older first-party mozilla build for very much longer ...?

02-19-2003, 07:23 PM
Alpha builds are just that. People who download them should know that, so I wouldn't worry. :)

That's why you don't see branded builds based on prerelease alphas.

02-19-2003, 07:36 PM
cool, that's what I figured :thumbsup: