Works on IE... looks like shit on Firefox

[alexvgtb]

Why oh why... do we have two browsers ?

Take a look... Version 0.13

http://villers.customer.attikh.net/~vil ... hp/visites

I'd like to get a space between the horizontal menu and the vertical one.
Works on IE but not on Shitfox !

Also... do you guys know how to retrieve the default templates ?

Thanks.

Alex

[KnightWolfJK]

I was going to ask what version of Shitfox you were using, but then I realized that anything called Shitfox would have to be labeled as "Number 2".

[alexvgtb]

No !

Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.0.4) Gecko/20060508 Shitfox/1.5.0.4

It's Shitfox 1.5.0.4 !

[Dr.CSS]

cause IE reads this and Firefox don't...

* html .clearfix {
/* Hides from IE-mac \*/
height: 1%;
/* End hide from IE-mac */
}

your menu_vert has no margin for Firefox to read....
you also have your header at a fixed width and the rest is set at a %, it's making your menu go under itself on window resize....

[alexvgtb]

Thanks Mark !

What do I need to change to fix this ?

Sorry but I'm a newbie, I admit...

[uptoeleven]

re calling it shitfox...

Mind your language chaps. Also the reason we need 2 browsers is because Microsoft won't release their source code to allow Internet Exploder to be open source - so can't use it in Linux. Also some of us don't like leaving our machines wide open to the world with a "come and get me I'm running ActiveX, I like trojans" sign on it.

And firefox is cool apart from the memory leaks when it goes into a loop, then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop and then has a memory leak and goes into a loop...

[Russ]

I think the sensible advice here is to design in the most 'web standards bowser' you can and design to web standards with accessibility to the fore. For many this means using something other than IE and then patching for the various IE Quirks in the various IE versions. This is not to say that Opera or Firefox or Safari don't have their quirks

Russ

[alexvgtb]

Well, still 85% of users prefer IE... So... I design for IE first...

Mark, can you help me with :

  * html .clearfix {
      /* Hides from IE-mac \*/
      height: 1%;
      /* End hide from IE-mac */
  }

Thanks !

Alex

[uptoeleven]

Don't do it this way. It's a recipe for real annoyances as every sane browser barfs at IE's idiosyncracies.

I build in Firefox first, not least because in the extensions there are a really good set of developer tools and DOM inspectors which make IE look like a real amateur thrown together job...

Then in IE you can add stuff like that asterisk thing to make stuff that firefox ignores but IE will work with.

[Ron@Spikecity]

Don't do it this way. It's a recipe for real annoyances as every sane browser barfs at IE's idiosyncracies.

I build in Firefox first, not least because in the extensions there are a really good set of developer tools and DOM inspectors which make IE look like a real amateur thrown together job...

Then in IE you can add stuff like that asterisk thing to make stuff that firefox ignores but IE will work with.

Exactly, for me the order of building is Opera, Firefox and finally check in IE, 99% chance it looks OK in all three that way, the other way around is a sure recipe for disaster.

There is no browser out now that is completely 100% following W3C guidelines, but Opera does a goed job, closely followed by Firefox ...then there is nothing then void space..... and then IE the "free choice" of 85% of the n00b PC users.