Chrome Bug

[Snitz]

Hello everyone,

I have a minor css bug on chrome that is driving me crazy!

Website url: http://www.icarwakim.com/demo/

If you look at the top, you'll notice 2 flags. Viewed on firefox or IE, the flags will horizontally align with the facebook button and search field. However on Chrome, it will align to the top, or maybe its adding some sort of padding-bottom that I can't find.

I am using firebug.

Any advise?
Thank you in advance.

[djm0219]

What happens when you correct the 154 validation errors and 4 warnings as well as the 123 CSS errors?

[Snitz]

Originally Posted by djm0219

What happens when you correct the 154 validation errors and 4 warnings as well as the 123 CSS errors?

I can see now that the website is not opening properly on IE. but on firefox and chrome it's good.

EDIT: it's not working properly on IE. I have no clue why

[Snitz]

The menu on IE behaves weirdly. on the main page it doesn't show the css styling, on other pages it works perfectly and on other pages, it shows but it doesn't display the sub-categories.

Any advise?

[Nightfire]

http://validator.w3.org/check?verbos....com%2Fdemo%2F sort them errors out, that'll help, as already mentioned

[Snitz]

I am using Joomla 1.5 platform with Ja_Teline_iii as a template.
This is the original demo of the template: http://templates.joomlart.com/ja_teline_iii/
If you validate that url, you'll get the same errors you're getting on my page. I don't think this is the problem here.

[drhowarddrfine]

Why we won't help you.

[Snitz]

The validator will spit out dozens or even hundreds of errors on your page, and finding the one that is actually causing your problem will be like finding a needle in a haystack.

I KNOW!!!!
The validator is giving me 1000 errors and it's giving the same errors on the original template demo page.

Anyway, thanks for the link.

[VIPStephan]

So – why don’t you start sorting the errors out at the top of the list and work through all the way to the bottom then? That something is published on the internet doesn’t mean that it’s all impeccably perfect. So, in this case the author of the theme has done a bad job at that (or simply overseen something simple).

I see that the first 50 or so errors come from imporperly used quote characters inside a title attribute value. You can fix them the easy way by using typographically correct quotation marks (“”) or not using any quotes at all. If you have the control over the input then you can also convert them to their respective HTML entities: “ and ”.

If you know PHP then you can make the input of straight quotes to be automatically converted to these entities or escape special characters. Lastly, you could scrap these titles at all to avoid issues.

The rest are relatively simple errors like unclosed elements or unencoded ampersands (&) or wrongly nested elements like div inside p, etc.