My OperaThis topic has been closed. No new entries allowed.
Reason: You can now post comments on articles on Dev Opera
You need to be logged in to post in the forums. If you do not have an account, please sign up first.
MAMA: Markup validation report
This is the first of a series of reports summarizing the results found by Opera's MAMA (Metadata Analysis and Mining Application) project. MAMA's full datasets are very detailed, so we are providing these reports as lighter reading for anyone who wants a quick insight. This report looks at markup validation - how well does our beloved Web validate in 2008? MAMA can tell you!( Read the article )
Originally posted by stancza:
I wonder if the "Typo" in CMS table refers to the TYPO3 CMS [typo3.org]?
Yes it does.
I wasn't familiar enough with it at the time of writing and didn't know it was officially called typo3. I'll work on getting this changed for all existing and future mentions.
Thanks!
Meh. The W3C validator is braindead, beginning with its fragile parser (trying not to swear here) and continuing with its blissful ignorance of newer technical recommendations such as WAI-ARIA. A Web designer has to give up a lot of useful features to make a "valid" website (whatever that means... weren't unkown tags/attributes supposed to be IGNORED?) and I just don't think it's worth it.
How about well-formedness? And well-formedness excluding unencoded &? Could you add stats for that too?
Not passing validation because of silly error like non-standard attribute is harmless compared to failing because of improperly nested tags.
Not passing validation because of silly error like non-standard attribute is harmless compared to failing because of improperly nested tags.
Originally posted by claudeb:
A Web designer has to give up a lot of useful features to make a "valid" website (whatever that means... weren't unkown tags/attributes supposed to be IGNORED?) and I just don't think it's worth it.
We have always been able to acheive validation. What have you had to give up in order to acheive validation?
Standards cost nothing!
Originally posted by active1:
We have always been able to acheive validation. What have you had to give up in order to acheive validation?
First of all, i didn't give up the features, I gave up the validation.
Second, I gave you an example right there in my first post: WAI-ARIA support. And here's another example: support for the new HTML5 <input> types in Opera. Haven't tried <canvas>, but I have a suspicion it doesn't work either. And soon we'll have <video> and <audio> support in several browsers. But I suppose one can always do whitout any of these... and have a website stuck in 2005. YMMV.