Firefox v.4 CSS issues

[limelites]

Up until now I've never had a problem with Firefox displaying my sites correctly. Now, with Firefox v.4 I'm finding that it's displaying certain elements differently from earlier verisons. For example, look at my instalments page in Firefox v3.6.1:

http://www.silkblooms.co.uk/index.ph...oducts_id=1652

Then look at it in Firefox v.4


You'll see that there are two issues I've noticed so far:

1. is the header menu bar. div#dropMenu which seems to have developed a bit of a padding problem.

2. is that the .gif files I'm using to hide the unit values are not placed where they're supposed to be. #instalmetnsEnterAmount and #instalmetnsHideMin

This type of problem has always been an issue with different versions of ie and I'e always used browser specific CSS files to deal with ie. However, I've never experienced this in Frirefox. Does anyone know how to tackle this? A way of targeting Firefox v.4 using CSS specific stylesheet?

[limelites]

Or, if I fix the CSS so that it works with Firefox V.4, then is there a way to target all earlier versions of Firefox?

[Kim]

Instead of trying to patch things with bandaids, perhaps fixing the root of the problems would be better - your site has 272 html errors and 270 warnings.

http://validator.w3.org/check?verbos...ucts_id%3D1652

[limelites]

Instead of trying to patch things with bandaids, perhaps fixing the root of the problems would be better - your site has 272 html errors and 270 warnings.

http://validator.w3.org/check?verbos...ucts_id%3D1652

..........and eBay.com has 509 Errors, 24 warning(s). But that seems to work just fine. I don't have a lifetime to spend fixing an endless stream of validation errors I'm afraid. Someone once said, 'if it looks right then it is right'. Up until Firefox v.4 it did 'look' right.

[torvista]

I don't have a lifetime to spend fixing an endless stream of validation errors I'm afraid

Kim is correct, if you don't invest an hour or so to fix what is obviously wrong (and easily fixed) you will spend a lifetime looking for what is not obviously wrong.

With every browser update comes stricter application of the rules of html and css, if your site does not abide by those rules it will break in that browser.

You will find most of the errors are caused by other errors, you may only have 20 or so to fix and the rest will disappear.

Use the html validator for firefox to track the errors down.
This continuously shows if a page is valid so you will always know when you have introduced invalid code with a new mod or incorrect tags in a product description.

When it works in FF, you can do additional css files to patch the formatting for older versions of IE if needed.

[limelites]

272 html errors and 270 warnings wouldn't take me twenty minutes unfortunately. I'm a florist you see, everything I've done with the site has been self taught from reading this forum and experimenting with things. I don't think I've done a bad job, but I did try to fix the validation errors a whole back and gave up. I couldn't figure out what most of them meant

It'd be easier to find a way of cheating, with a browser specific CSS file that handles FF4 or FF1,2 and 3

[kuroi]

I don't have a lifetime to spend fixing an endless stream of validation errors I'm afraid.

So why do you think we do?

They only need to be fixed once. And there's a finite number of them.

If they're endless, it's because you keep creating them. That's a cycle that only you can break.

... and to ask other people to fix stuff you can't be bothered to fix yourself - I'm doubting you'll get many takers on that.

[torvista]

272 html errors and 270 warnings wouldn't take me twenty minutes unfortunately

You are not reading the replies people are taking the time to write. You don't have 270 different errors.

I couldn't figure out what most of them meant

The html validator for firefox TELLS you what the error means and usually how to fix it.
You have already spent more time replying to this thread than it would have taken you to fix over half the errors that are flagged.

for example

ERROR:
line 127 column 144 - Error: general entity "langpair" not defined and no default entity...

Cause:
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text.

So change

href)+'&langpair=en%7Czh-CN&hl=en&ie=UTF8');

to

href)+'&langpair=en%7Czh-CN&hl=en&ie=UTF8');

That's half the errors fixed with bit of educated find-and-replacing.

While this probably wont fix your css issues it will give you more incentive to clear the few errors that are left and people may be more inclined to help you fix them if they do prove to be difficult to find.

[limelites]

So why do you think we do?

They only need to be fixed once. And there's a finite number of them.

If they're endless, it's because you keep creating them. That's a cycle that only you can break.

... and to ask other people to fix stuff you can't be bothered to fix yourself - I'm doubting you'll get many takers on that.

Where did I ask anyone to fix my validation errors? I think you'll find I didn't ask that, I merely stated that I don't have time to fix them. I didn't ask you to fix them.

If you read the OP and my subsequent posts here, you'll see that my question is about Firefox specific styling, not validation errors. It was Kim who brought up validation errors.

At the moment I don't have time to fix them. I'm hoping to cheat a little by introducing a browser specific workaround for the time being.

[limelites]

OK, I'll have a blast at fixing them. I didn't realise that the 220 errors weren't individual errors. The & one was the one that made the throw in the towel last time. I have dozens and dozens of files with the & in them, so it was taking too long. Extremely busy with the business you see.... Any takers in the old freelance side wanna take this on?