I've been implementing the Blueprint CSS framework along with CFWheels lately and ran into a couple of hours of headaches today with the display in IE.
Spans were not displaying correctly. It was like IE didn't recognize the width assigned to the spans. IE also wasn't displaying the colborder correctly and there was this horrid 5 to 10 pixel gap between divs.
I had all kinds of things going on (a jquery cycle, a dropdown menu, etc) so I initially thought that all these things just weren't playing well together like naughty children.
I worked around things in an IE specific css file and then it occurred to me - I didn't have a doctype declared.
That was the root of all the IE display problems. Once I declared a doctype, I was able to eliminate all the workarounds I had so painstakingly created over the last couple of hours.
So next time, I will check to make sure I've declared a doctype first!
3 comments:
which doctype do you end up using?
Tony, I used transitional, but checked and strict also solved all the problems.
I plan on going back today and making sure I specified doctypes on all my recent cfwheels projects (even the ones I didn't use blueprint on).
You know wheels starts your template off with <html> and <head> tags and I guess it was very "blonde" of me but I thought the doctype was baked into wheels.
It wasn't until I really looked at the source code that I saw that wasn't so.
before html5 i dreaded having to declare a doctype because they were so long. now it's just a simple:
and you're done.
Post a Comment