Yes, it is indeed broken in IE but it is fine in Firefox.
I think the problem is related to your heavy use of Tables. A clue that the problem is related to tables is gleaned just by looking at how the site is displayed in IE, where all the content components are displayed as one vertical column.
In Firefox the rendering of the tables is fine, from looking at the source code. When I view the source under IE, there seems to be mismatching of table and related tags (td, tr). Try viewing the source under IE and you will see the mismatching is color coded.
If you know HTML, you can try to fix it yourself. There may be some elements that are breaking the table rendering (perhaps javascript, etc, just guessing).
But if you don't know HTML much and have bought the site from someone, you may want to get back to the developer and ask him to fix for you.
Failing that I suppose you can always pay someone (not me) on this forum to fix it for you.
Perhaps some of your problems have to do with the 32 coding errors you have? You can view them here.
Generally, the vast majority of websites will have errors when validated with W3C markup. As I posted above, I think his key issue is related to the broken html table rendering in IE. That would be the starting point for him to solve the problem.
Generally, the vast majority of websites will have errors when validated with W3C markup. As I posted above, I think his key issue is related to the broken html table rendering in IE. That would be the starting point for him to solve the problem.
The "vast" majority of sites may indeed have errors, but errors I noticed the OP having could cause his rendering issues. Just because the "major" sites have coding errors doesn't mean we as designers/developers should relax and code sloppy incorrect webpages.
Moreover, if a site is having issues, the first step to debugging an issue should and would be having clean valid code to eliminate bad code such as unclosed elements, improperly nested elements, and the like. Youc an expect browsers to render a page when it diesn't know if that div was meant to close at line 38, or way down on line 50.
Lastly, even though table layouts are discouraged and outdated, that doesnt mean a well coded table wouldn't work in any and all browsers. So it's not the fact that he used a table for his layout, but perhaps his poorly coded table is the culprit.
Perfect examples of sloppy code here:
Improperly constructed comment tags. One poing he uses them is correct: <!-- Some Comment --> another place is wrong: <!--Some Comment--!>
Another error thats major is inserting a style tag below the head section. On line 47 I believe he had:
Opening <tr> tags outside the <table> tags. Improperly closed <br /> tags. Since he's using xhtml, <br> is invalid and <br /> should be used. Although this one would not break his layout, I thought I would throw it in.
Again, first things first. Fix your mark-up errors and then see what you've got.
Well it seems like the index page is working now. I got rid of the comment errors and now its not as bad as it was before. There is still a weird redish color that's supposed to be a gradient
Ever want to see inside of a rave? Check out RedRoll and join our community of EDM lovers and rave fanatics.
which of those errors should i fix? im halfway decent at coding but i dont know which things in that list I should fix.
All of them...lol
I realize sometimes code from plugins, google analytics, and facebook and such might have validation errors in it, but the code you write can and should be as close to valid as possible.
The "important" ones to fix though would be the mismatched opening and closing tags and the improper comment tags. Those will break a page quickly.
Comment