So I should escape characters that are already inside of double quotes.. great. And the fact that all browsers support unescaped HREFs means nothing in the face of the almighty "Look! I validated!" claim.
ALT attributes provide descriptive text and are replacements for missing images. Great! Now, why are they required? Not to mention, any use of any attribute not on the list will get you unvalidated. Suppose I want to include some extra data for JS, like "_droptype" or "_isDraggable". Sorry! It's not on W3C's list of acceptable attributes so you fail validation, even though all browsers ignore attributes they don't know about.
An empty tag... why do I have one? Well, maybe because inside the tag I have server generate text.. .and instead of doing;
if ($text) echo "<tr>$text</tr>"
I do
echo "<tr>$text</tr>"
Would it be so hard to make the standard: "If theres nothing in the tag, treat it like it doesn't exist"? No.
Furthermore, I have blank DIVs to take up width/height sometimes. Then again, I'm sure there's some clever way to wrap 20 DIVs and put browser specific hacks so it actually validates... but I prefer to do it the way that works.
Major browsers are nice enough to allow me to not care. So show me errors that I need to care about. W3C validation, to me, is like saying "I memorized every little gotcha that W3C implemented... and still, everything works! Aren't you impressed? Five years from now, the site should still work! Forward validation! Yay!"
Comments
So I should escape characters that are already inside of double quotes.. great. And the fact that all browsers support unescaped HREFs means nothing in the face of the almighty "Look! I validated!" claim.
ALT attributes provide descriptive text and are replacements for missing images. Great! Now, why are they required? Not to mention, any use of any attribute not on the list will get you unvalidated. Suppose I want to include some extra data for JS, like "_droptype" or "_isDraggable". Sorry! It's not on W3C's list of acceptable attributes so you fail validation, even though all browsers ignore attributes they don't know about.
An empty tag... why do I have one? Well, maybe because inside the tag I have server generate text.. .and instead of doing;
I do Would it be so hard to make the standard: "If theres nothing in the tag, treat it like it doesn't exist"? No.Furthermore, I have blank DIVs to take up width/height sometimes. Then again, I'm sure there's some clever way to wrap 20 DIVs and put browser specific hacks so it actually validates... but I prefer to do it the way that works.
Major browsers are nice enough to allow me to not care. So show me errors that I need to care about. W3C validation, to me, is like saying "I memorized every little gotcha that W3C implemented... and still, everything works! Aren't you impressed? Five years from now, the site should still work! Forward validation! Yay!"