I have a problem with a lyout where I can't get the slider alligned correctly in IE. It works fine on the first slide but with the second and third slide it moves to far to the left. The problem is only in IE
The layout: http://osours.com/
The slider css: http://osours.com/css/style.css
The index cs: http://osours.com/css/index.css
I hope someone can help because I've been struggeling for quite a while now.
Thank you.
Which IE? when referring to
Which IE? when referring to IE it is one time when one must acknowledge the version - although few seem to do so.
Remove all that stuff at the top of the page. A html document begins with the line:
<!DOCTYPE the only time there is anything placed before that is if it is server side scripting If you really feel you have to have those comments then move them into the head section.
Next you need to validate your markup as there are errors, in fact make your life easier and remove that JavaScript to an external file.
That is not really an awnser
That is not really an awnser to my problem;
The stuff at the top of the page has no influence on this problem, also I know the layout isn't valid (yet) however this is also of no influence on this problem. How do I know; the layout was allready fully functional however I had several files open and my pc closed without saving. After that I had a lot of problems and this is the last one left, however I can't seem to find the problem.
I first want to have any problems solved before I start cleaning up the html
Well. If you know better than
Well. If you know better than us, why did you come here?
Why do you say that? I just
Why do you say that? I just said that's it's not an awnser to my question. Sorry if this seems rude as this was not intended.
Any data rendered before a
Any data rendered before a doctype WILL put Internet Explorer into QUIRKS mode.
As Hugo suggests, remove all those comments, and if they are necessary, move them below the doctype.
Also, you still have refused to state which version of IE you are having difficulties with.
Most of us here will not waste our time digging through code that can't even validate, so if you refuse to validate as well, then there is little we will probably do to help.
You have to help yourself before we will help you.
homann wrote: That is not
That is not really an awnser to my problem;
Actually, yes it is but you, who came here asking for free help choose to reject it out of hand.
The stuff at the top of the page has no influence on this problem
Your belief that it doesn't has no influence on the fact that it does.
The IE version is 7 > "Most
The IE version is 7 >
"Most of us here will not waste our time digging through code that can't even validate, so if you refuse to validate as well, then there is little we will probably do to help.
Honestly I allways made sure everything worked before I start validating. Is the other way round a better solution?
(and it really wasn't my intention to be a wiseass)
Quote: I first want to have
I first want to have any problems solved before I start cleaning up the htm
Oh really! that I'm afraid is what's known as 'arse about face' everything else has been said really but did you actually try either of the things I mentioned?
Just seen your last post.
Just seen your last post. Emphatically yes you MUST validate as you develop that is absolute and unconditional. Mal-formed markup produces unpredictable results and due to the nonsense known as the tag soup rendering engine trying to correct these errors you can get a cross browser mess, there are no standard rules to govern how browsers are meant to correct errors they each do as they see fit, which is problematical. The only way to know if you really have an issue to deal with is by ensuring that firstly your markup is error free.
I really have to appoligise
I really have to appoligise here :
Removing all junk at the top and moving it between the head section did the job. I truelly had no idea. So, another day, another lesson learned.
Thank you very much
Pays to listen, eh? These
Pays to listen, eh? These guys are pros, man. They wouldn't tell you something that wouldn't help.
Being able to admit ones
Being able to admit ones wrong counts for a lot! I know I have to do it often
I would also remove the JavaScript to an external file as that will clear up a few other validation issues.
"I would also remove the
"I would also remove the JavaScript to an external file as that will clear up a few other validation issues."
This is new to me so I am looking into this now.
homann wrote: Honestly I
Honestly I allways made sure everything worked before I start validating. Is the other way round a better solution?
You must validate as you go, and frequently. With various Firefox add ons this is easy, quick, and free. Valid html is a necessary precondition for success, as important as the foundation is to building a house.
If you validate often, you will find yourself making many less mistakes in coding and get much better results as a consequence. You need to validate your CSS too, but it's the HTML validation that is by far the most important, as already explained in this thread.
Now I'm just being
I should have added "validate
I should have added "validate to a STRICT document type", as Hugo has shown. Use a STRICT doctype and validate against it frequently as you write the markup.