It’s funny, cuz the majority of websites that are like “YARR!!! HTML SUXXX NO TABLES 4 LYFE W3C IS YOUR GOD NOW TREBEK” often have one or two fatal flaws that make it so Firefox can’t read them correctly.
And they all use those fucking dotted lines as separators. Jesus Christ.


    1. Well, Firefox certainly isn’t either.
      To tell the truth, I’ve been able to acheieve W3C compliance but it only showed up correctly in IE. Not that I use it, and not that I try to be W3C compliant at all. I don’t see the use.

    1. Additionally, lots of design-related problems and cross-browser incompatibilities when it came to turning my page into CSS – some things like aligning “tables” and everything just didn’t seem like it could be done – I asked for help.
      Screw W3C validation; it’s totally not necessary.

      1. The above referenced page shows renders correctly even at 640×480. I don’t buy into the idea that pages should degrade perfectly at resolutions lower than that. Anyway, even at lower resolutions, the content div just moves down below the sidebar. Someone browsing at that res should be used to scrolling.
        Not that I’m a big fan of this particular page. I think it’s pretty ugly, and definitely NOT a shining example of XHTML+CSS design.
        I am a big fan of validation and standards, though. Firefox isn’t perfect. IE is pretty much horrible. Opera comes the closest of the big three to being 100% compliant. Attitudes like yours don’t go very far to help close that gap.
        There’s nothing necessarily wrong with using tables for layout, as long as the only thing you care about is how the page renders in one browser for Desktop or laptop users. When you start getting into mobile devices, accessibility, and so on, CSS makes things SO much easier.
        I guess my point is that just because you don’t see it’s use, doesn’t make it unecessary. The tide is definitely turning towards these standards.

Leave a comment

Your email address will not be published. Required fields are marked *