Slashdot Mirror


Only 4.13% of the Web Is Standards-Compliant

Death Metal writes "Browser maker Opera has published the early results of an ongoing study that aims to provide insight into the structure of Internet content. To conduct this research project, Opera created the Metadata Analysis and Mining Application (MAMA), a tool that crawls the web and indexes the markup and scripting data from approximately 3.5 million pages."

406 comments

  1. Well, that depends.... by AltGrendel · · Score: 5, Funny

    ...on which standard the designer chose.

    --
    The simple truth is that interstellar distances will not fit into the human imagination

    - Douglas Adams

    1. Re:Well, that depends.... by morgan_greywolf · · Score: 5, Funny

      'Looks good in Internet Explorer and doesn't seem to crash Firefox or Opera' is not a standard.

    2. Re:Well, that depends.... by Anonymous Coward · · Score: 1, Funny

      The great thing about standards is, there's so many to choose from.

    3. Re:Well, that depends.... by theaveng · · Score: 2, Funny

      Does using make my code non-standard?

      --
      FOX NEWS.com should be BANNED from television and internet. Have the Congress take it over and give us Truespeak.
    4. Re:Well, that depends.... by g0dsp33d · · Score: 5, Funny

      But if we completely reverse the standards we should be at 95.87% compliance!

      --
      lol: You see no door there!
    5. Re:Well, that depends.... by Anonymous Coward · · Score: 0

      Choose a W3C standard.. make it fit to a triple AAA compliance level and you've created something which should work in any browser.

      Adding on wings to fish can still be useful, as long as it doesn't stop the fish from swimming.

    6. Re:Well, that depends.... by remmelt · · Score: 4, Funny

      It sure makes your Slashdot comment non-standard!

    7. Re:Well, that depends.... by andy19 · · Score: 3, Funny

      I disagree- I'd say that's a pretty standard Slashdot comment.

    8. Re:Well, that depends.... by Anonymous Coward · · Score: 0

      You're not in some standards committee now are you? Like ISO ;)

    9. Re:Well, that depends.... by elrous0 · · Score: 4, Insightful

      There are only two standards that I care about: "How does my page look and work in Internet Explorer?" and "How does my page look/work in Firefox?" Beyond that, I couldn't really give a shit less if the W3C does or doesn't like it. My clients aren't paying me to spend extra time designing perfectly W3C-complaint sites, they are paying me to design a site that reaches real-world customers in as efficient a manner as possible.

      --
      SJW: Someone who has run out of real oppression, and has to fake it.
    10. Re:Well, that depends.... by gnick · · Score: 4, Insightful

      'Looks good in Internet Explorer and doesn't seem to crash Firefox or Opera' may not be a standard, but it satisfies the bulk of most web-sites' customers. I'm a FF user and include myself in that group. I realize that sites are tuned for IE because it's the leader and accept that my browser choice and add-ons sometimes make things look a little funny - As long as they work I don't care. I would guess that most visitors feel more or less the same (slashdot standards nazis excepted).

      Besides, if most of a web site's traffic is coming from a browser that doesn't support any standard but their own anyway, what motivation do they have to conform?

      --
      He's getting rather old, but he's a good mouse.
    11. Re:Well, that depends.... by jellomizer · · Score: 4, Insightful

      Internet Explorer is really the big trouble maker here. Any Professional knows that their site needs to render flawlessly in IE first, Good enough in Firefox, and perhaps workable on others. Following the "standards" bairly leads to this operation as IE so poorly handles the standards that you really need to break them. I am still trying to find the HTML tag that gives IE users an electric shock.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    12. Re:Well, that depends.... by theaveng · · Score: 1

      That was supposed to say:

      Does using "blink" make my code non-standard?

      --
      FOX NEWS.com should be BANNED from television and internet. Have the Congress take it over and give us Truespeak.
    13. Re:Well, that depends.... by Bill,+Shooter+of+Bul · · Score: 2, Insightful

      Yes it is. It is the standard that everyone shoots for. The defacto standard if you will. It is not a rigorously defined standard published by an internationally recognized standards body. I'm afraid there is not a single standard definition of the word standard in the English language.

      Isn't English fun, my compeer?

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    14. Re:Well, that depends.... by Bogtha · · Score: 4, Insightful

      'Looks good in Internet Explorer and doesn't seem to crash Firefox or Opera' may not be a standard, but it satisfies the bulk of most web-sites' customers. I'm a FF user and include myself in that group.

      The problem with that attitude is that not so long ago, Firefox wouldn't be in the list, and for many developers (including some I worked with this week) Opera is still not on that list. It's like Internet Explorer only websites, except only slightly laxer. So you use Firefox. Lucky you! How about all the people who use something less popular, e.g. Konqueror? How about all the people who must use something that will never be popular, such as people with disabilities? Shall we just say "tough, get off the web"?

      As long as they work I don't care.

      "Working" is not a property of a website. "Working" is a property of a combination of a website and a browser. You can't say that a website "works", only that it works in particular browsers.

      --
      Bogtha Bogtha Bogtha
    15. Re:Well, that depends.... by Anonymous Coward · · Score: 0

      Keyword here is 'should'. Most of the time it most definately does not work. :)

      And what do you mean triple AAA compliance level, either it complies, or it doesn't - there's no distinctions to be made.

    16. Re:Well, that depends.... by Bogtha · · Score: 4, Funny

      I am still trying to find the HTML tag that gives IE users an electric shock.

      Don't be silly, everybody knows you use CSS for that. (Cruelly Sadistic Styleshocks).

      --
      Bogtha Bogtha Bogtha
    17. Re:Well, that depends.... by Lachlan+Hunt · · Score: 5, Informative

      Does using "blink" make my code non-standard?

      Yes, because blink is not defined as conforming in any standard. However, it is possible to make a page containing blink (or any other element or attribute you like) pass validation by providing a custom DTD or an internal subset.

      But note that the claim that "4.13% of the Web Is Standards-compliant" isn't quite accurate. The study only used the W3C markup validator, which is only able to detect a subset of the machine checkable conformance criteria. It's trivial to create a non-standards compliant page that passes validation.

      --
      By reading this signature, you hereby agree with the content of the above comment.
    18. Re:Well, that depends.... by andy19 · · Score: 3, Funny

      Oh, well in that case, not at all.
      Both blink and marquee are two very useful tags that should be used on every website.

    19. Re:Well, that depends.... by bunratty · · Score: 4, Insightful

      If you haven't validated an HTML page, you can fairly safely assume it's not valid HTML. Just like if you type in a program and never run it through a compiler, it probably has a syntax error in it somewhere. It's the exception that a non-trivial program compiles on the first try. Likewise, if you don't validate your HTML, it likely contains syntax errors that cause it not to validate. You should cross your fingers that all browsers, past, current, and future, deal with the syntax error in the way that's favorable to you.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    20. Re:Well, that depends.... by morgan_greywolf · · Score: 2, Funny

      Unfortunately, the CSS attribute that gives IE users an electric shock is one of those that IE doesn't support.

    21. Re:Well, that depends.... by noidentity · · Score: 1

      'Looks good in Internet Explorer and doesn't seem to crash Firefox or Opera' is not a standard.

      Calm down, it takes up to a week for your bribe^H^H^H^H^Hcheck to be delivered and processed by ISO.

    22. Re:Well, that depends.... by gnick · · Score: 3, Insightful

      How about all the people who use something less popular, e.g. Konqueror?

      Web pages will be tailored to suit the bulk of their traffic. Konqueror will learn to display them properly, regardless of adhesion to standards, or fall by the way-side as users get frustrated. It's not fair, it's not right, and it's not changing. Sorry.

      How about all the people who must use something that will never be popular, such as people with disabilities? Shall we just say "tough, get off the web"?

      Some pages are practical to conform to people with disabilities. Some aren't. When practical, web-admins should make their pages accessible to the handicapped. Adhering to standards may make it easier to tailor specialized browsers for use, but the fact remains that pages will be written to display properly in the most popular browsers and people that write "unpopular" browsers need to conform to that.

      I'll tell you what, why don't you volunteer to re-write all of the flash-games on the web so that blind people can play them? When you're done, I'll assign you some music sites that you can re-code for the deaf.

      Should we say "Tough, get off the web"? No. We should say "Sorry, but because of your disability there are a lot of things in this world that you'll never be able to enjoy. We'll try to help you enjoy the rest." Sorry if that sounds heartless, but I'm a realist.

      As long as they work I don't care.

      "Working" is not a property of a website. "Working" is a property of a combination of a website and a browser. You can't say that a website "works", only that it works in particular browsers.

      I should have said "as long as they work for me" as in "as long as when I visit them using my browser with my configuration settings under my OS using my I/O devices they behave well enough that I can use them". I thought that I had successfully implied that. Sorry.

      --
      He's getting rather old, but he's a good mouse.
    23. Re:Well, that depends.... by AndrewNeo · · Score: 1

      Well you can ~make~ working a property of the website..

      <html working="true">
      <body>
      It works!
      </body>
      </html>

    24. Re:Well, that depends.... by Bogtha · · Score: 1

      I'll tell you what, why don't you volunteer to re-write all of the flash-games on the web so that blind people can play them? When you're done, I'll assign you some music sites that you can re-code for the deaf.

      This is a total red herring. The fact that there are some media-specific situations that cannot be made accessible to people with certain disabilities is not at all relevant to the point, which is that by targeting only popular browsers, you may exclude people with disabilities who cannot switch to more popular browsers. Can this be justified in specific instances like Flash games? Sure! Does that make any difference to the 95% of invalid web pages we are talking about? Nope.

      --
      Bogtha Bogtha Bogtha
    25. Re:Well, that depends.... by plague3106 · · Score: 1

      How about all the people who use something less popular, e.g. Konqueror? How about all the people who must use something that will never be popular, such as people with disabilities? Shall we just say "tough, get off the web"?

      Pretty much, ya. If I'm paying to have a website built, I'm not going to spend a lot of money making a very small number of people happy. They choose to use an almost unknown browser, they need to live with the consequences of that choice.

    26. Re:Well, that depends.... by Bogtha · · Score: 1

      "Damn idiots shouldn't have chosen to be blind in the first place!"

      --
      Bogtha Bogtha Bogtha
    27. Re:Well, that depends.... by interploy · · Score: 2

      Really though, if over 95% of the web isn't "standard" then maybe they need to rethink what is and isn't standards-compliant.

      I haven't read TFA, but I assume they're only going by what the W3C standards are, and anything outside of those parameters gets knocked. But really, there isn't a single browser that's 100% standards compliant, so it'd be a better judge to see how many sites work across all the major browsers instead of how many sites' code matches a standard not even the browsers fully support.

    28. Re:Well, that depends.... by Anonymous Coward · · Score: 0

      It's interesting that the 'won't somebody think of the children' poster championing standards compliance on behalf of the disabled is accusing somebody else of tossing out a red herring. The truth is that you're both grasping at straws.

      Pot, meet kettle.

    29. Re:Well, that depends.... by Jellybob · · Score: 4, Insightful

      The point is that if the site is built to standards, you don't have to spend a lot of money making that small number of people happy. Their browser is probably built to render sites as the standards specify, and so it'll probably work anyway.

      I build web applications at work, and only have to make it work in Firefox, but because I'm using standards, and think about what I'm doing, I can be fairly confident that it's going to work in most other things as well. I have users happily using my apps in some barely known browsers, without problems.

    30. Re:Well, that depends.... by tuxgeek · · Score: 1

      Your logic is lame

      The internet protocol is a standard. M$ is not. M$ is just some wacked out monolopy that wants the world to conform to their business model. To code a web site to look good for the IE users excludes millions of visitors that don't use M$ products.

      I am a Linux user and run the latest FF version complete with script blocking and all the safe surfing plugins. It really pisses me off to go online to shop, only to find a site renders like shit and is completely unusable. Business lost for them. I go elsewhere.

      --
      "Suppose you were an idiot...and suppose you were a member of Congress...but I repeat myself." Mark Twain
    31. Re:Well, that depends.... by billcopc · · Score: 2, Informative

      Standards do help, but the problem is the leading browser doesn't follow the standards too well.

      My primary browser is Firefox, so I do 90% of the development in there. The last 10% is spent adjusting little bits and bobs for IE6/7. It doesn't matter that my pages validate, and that I'm pretty damned good at making my spaghetti code spew proper XHTML - IE is still a retard.

      Where I work, we guarantee only one browser: IE6. Anything else costs extra, because of the testing involved. If someone wants us to guarantee their site will run perfectly in Opera or any other browser, they have to cover our time spent testing and massaging the markup. Sometimes that can amount to another 2-3 days of billable time on a big site/app.

      I don't use Konqueror at all for web browsing. Frankly I wish it would just embed the Gecko engine and be done with it.

      --
      -Billco, Fnarg.com
    32. Re:Well, that depends.... by al3 · · Score: 1

      Enter: HTML 5.

    33. Re:Well, that depends.... by Anonymous Coward · · Score: 0

      Give it time, Microsoft's trying as hard as they can.

    34. Re:Well, that depends.... by Bogtha · · Score: 1

      If you haven't validated an HTML page, you can fairly safely assume it's not valid HTML. Just like if you type in a program and never run it through a compiler, it probably has a syntax error in it somewhere.

      Actually, I've been writing HTML for about a decade, and programming for about fifteen years, and I find that my HTML is usually valid on the first attempt, even though the same is not true of programs I write. I think perhaps it's because the syntax is simpler. It's easier to spot an unclosed tag than it is a missing semicolon because syntax highlighting gives it away much more readily.

      But yes, you should validate routinely, or better yet, incorporate validation into your development practices. For instance, I like to use WSGI middleware that automatically validates each page, and if there are any errors (including on pages generated in response to a POST), they are displayed prominently in the page itself. As soon as I make a mistake, I see it. And I use XML-based template engine, so if there's a formedness error, it doesn't even get that far. When you make it impossible to ignore your mistakes, you end up making far fewer.

      --
      Bogtha Bogtha Bogtha
    35. Re:Well, that depends.... by Anonymous Coward · · Score: 0

      Don't vote this November.

    36. Re:Well, that depends.... by pbhj · · Score: 1, Insightful

      Tripe.

      It's not a standard it's a compromise used by website designers that can't/won't code properly - be that through technical or temporal (ie financial) restrictions.

      It's fine to make a design decision that says screw the standards 70% of visitors can view it as I intended and the customer won't know any better. That's up to the individual "designer" (by which term I include Frontpage-monkeys).

      But trying to suggest that this is adhering to web-standards, outside of an intellectual exercise in breaking the boundaries of the semantics of the English language, is rediculous [sic].

    37. Re:Well, that depends.... by Bogtha · · Score: 1

      And what do you mean triple AAA compliance level, either it complies, or it doesn't - there's no distinctions to be made.

      No, WCAG is an instance of a specification that can't be machine-checked, because human judgment comes into it. For example, checkpoint 14.1:

      Use the clearest and simplest language appropriate for a site's content.

      You don't think that's a grey area?

      --
      Bogtha Bogtha Bogtha
    38. Re:Well, that depends.... by gnick · · Score: 0

      It's simple economics.

      It costs A to make a web-site that complies to standards, compared to B to hack something together that 'Looks good in Internet Explorer and doesn't seem to crash Firefox or Opera'. A > B.

      X fraction of site visitors use IE. Y fraction of people use something else but will stay to shop even if the site looks a little funny. Z fraction of people use something other than IE and will bail out annoyed because of poor rendering. X > Y > Z. (You can argue that Z is possibly greater than Y, but for most cases my guess is Y > Z).

      Average profit from someone who stays to shop is M.

      If you make a site render well across the board and M * (X + Y + Z) > A, you have a good return (neglecting expenses constant to both choices).

      If you tailor your site to IE, only half-acknowledge that other browsers exist, and M * (X + Y + Z) > B, you have a positive return.

      Basically, if A - B > M * Z, you hack a site together and ignore the lost sales. Anything else would be bad business. I strongly suspect that this holds true for most sites - If it didn't they would change their practices to recover your lost business.

      So, I understand that you feel neglected and I share your frustration that the world is conforming to MS instead of MS conforming to the world. But, assuming that you want to have a successful site as opposed to a failing business that spreads peace and harmony by adhering to web standards, please explain again why my "logic is lame".

      --
      He's getting rather old, but he's a good mouse.
    39. Re:Well, that depends.... by BenoitRen · · Score: 1

      Actually, professionals develop their website according to standards first, then do what is necessary to make it render properly in all other web browsers. Usually this is only needed for IE, for which you can use its conditional comments to serve it a specific stylesheet that fixes the problems.

    40. Re:Well, that depends.... by sanosuke001 · · Score: 2, Interesting

      Actually, I wish browsers would fail miserably when they find a non-compliant error instead of working around it like with HTML.

      In a program using [insert favorite (real)language here], when you have a syntax error it dies a horrible death. In testing, that's fine. You can fix it. Fixing things keeps them tidy and requires it to fit certain rules.

      If your compiler saw ints=5; instead of int s = 5; and decided that ints should be a string, would you be happy? Then, when you wanted to do s = s + 6; and got 6 (because s hasn't been declared and your compiler decided that was ok, too) would you be happy? Would that suck to try and debug?

      That's HTML.

      --
      -SaNo
    41. Re:Well, that depends.... by osu-neko · · Score: 1

      If you haven't validated an HTML page, you can fairly safely assume it's not valid HTML. Just like if you type in a program and never run it through a compiler, it probably has a syntax error in it somewhere.

      It might, but "probably" is stretching it. I usually catch syntax errors long before I try compiling. Which doesn't mean my code is error free, far from it, but actual syntax errors are pretty rare. They tend to catch my eye long before I save the source, much less attempt compiling it.

      --
      "Convictions are more dangerous enemies of truth than lies."
    42. Re:Well, that depends.... by AmberBlackCat · · Score: 1

      Jackass.

    43. Re:Well, that depends.... by Anonymous Coward · · Score: 1

      Won't somebody think of the children?

      I've got nothing against blind people, but doubling your operating costs to help less than 1% of your customer base is stupid. Doubling may even be conservative. Making a parallel site that's blind-friendly will likely be more expensive than making the site that 99%+ of your users will use. And then you need another for people that can't use keyboards. And another for people who've suffered brain damage and can't remember logins or passwords.

      Sometimes ignoring a group of people is both sad and a really good decision.

    44. Re:Well, that depends.... by gnick · · Score: 1

      While I find your counter-argument compelling and well though-out, there are a couple of points that I find unaddressed. Specifically:

      1) Do you object because I don't advocate spending exorbitant amounts of resources conforming things that are not naturally handicap-friendly to the handicapped or because my argument is not well thought-out? I.e. is this a difference in opinion or a criticism of my train of logic?

      2) "Jackass" is a rather vague term, although it confers the tone perfectly reasonably. Are you implying that I'm a jerk because I rebutted the "What about the handicapped?" assertion or are you calling me a moron? I.e. "asshole" or "dumb as a mule"? Possibly both?

      Thank you for your careful consideration of my post and insightful reply.

      Cheers.

      --
      He's getting rather old, but he's a good mouse.
    45. Re:Well, that depends.... by pizzach · · Score: 1

      My clients aren't paying me to spend extra time designing perfectly W3C-complaint sites, they are paying me to design a site that reaches real-world customers in as efficient a manner as possible.

      With the direction that IE8 is taking, making a W3C-compliant site may actually be the way to "design a site that reaches real-world customers in as efficient a manner as possible." I understand why you do what you do, but don't miss the boat when it comes either. IE7 already has relatively good standards support.

      --
      Once you start despising the jerks, you become one.
    46. Re:Well, that depends.... by Anonymous Coward · · Score: 0

      Yes, because blink is not defined as conforming in any standard.

      Not quite true (for better or worse). I give you: CSS 2.1.

    47. Re:Well, that depends.... by genghisjahn · · Score: 1

      Developers of 95.87% of all websites disagree with you.

      --
      Sorry about the mess.
    48. Re:Well, that depends.... by nschubach · · Score: 1

      I hope you never complain about someone butchering the English language, because you are basically saying that it's fine to ignore the rules as long as everyone else does the same.

      --
      Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
    49. Re:Well, that depends.... by morgan_greywolf · · Score: 2, Insightful

      Well, I'm not person who called you a jackass, obviously, but I would say that your argument is not well thought-out. First you, said it's "not fair, not right and not changing" or something like that. That's completely factually incorrect. IE 8 has "compatibility mode" (aka "render this page like IE 6") turned off by default. IE 8 is much closer to standards-compliant than any Microsoft browser that came before it.

      What does this mean? It means that Microsoft is taking action to change the current situation. That means that it is changing -- for the better.

      Secondly, I believe the person named 'AmberBlackCat' was obviously offended by your insensitivity to the plight of people with disabilities. And so was I. I think you wrong folks with disabilities with your attitudes towards their plight. Wouldn't you want people to be more sensitive to you if you suddenly became disabled? Because it could happen -- one day you walk out on the street and get hit by a driver who wasn't paying attention, for instance.

      Note that for certain U.S.-based Web sites, at least, it might even be illegal for say, an e-commerce site to fail to make reasonable accommodations for the blind under the Americans with Disabilities Act. Other countries have similar laws on the books. (IANAL and this is not legal advice, blah, blah)

    50. Re:Well, that depends.... by interploy · · Score: 1

      I hope you never complain about someone butchering the English language, because you are basically saying that it's fine to ignore the rules as long as everyone else does the same.

      On the contrary, I'm thinking more along the lines of 'if the standard to do x is using code y, but everyone is using code z to make it work in the browser, then maybe z should become part of the standard'.

      And btw, people butchering the language is exactly how languages evolve. Otherwise we'd still be using words like thou and forsooth and such wonders as ginormous would never have come into being.

    51. Re:Well, that depends.... by elrous0 · · Score: 1

      Any designer who doesn't think FIRST and FOREMOST about how his site is going to look in Internet Explorer is performing a major disservice to his clients. As a designer, I design for IE first, Firefox second, and every other browser third. If I started with W3C compliance and built out from there, I would have to double my rates (and the resulting sites would be a lot wonkier in IE to boot).

      --
      SJW: Someone who has run out of real oppression, and has to fake it.
    52. Re:Well, that depends.... by Lachlan+Hunt · · Score: 1

      yes, but this was about markup validation and I was only referring to the blink element in HTML, not the text-decoration value in CSS.

      --
      By reading this signature, you hereby agree with the content of the above comment.
    53. Re:Well, that depends.... by Anonymous Coward · · Score: 0

      I'm a web developer myself. The problem I see is that often some Joe Schmo hires a developer to build a site for them. Their idea of cost is, "Hey I could probably do a site for $300-$400 bucks that has a full administration section, blogging, custom forms, email capabilities and a layout that only I could dream of that totally defies HTML or CSS." The developer says, "Here's the price. 10k." Joe Schmo says "Ouch."

      In the end the owners of a lot of these sites just aren't willing to pay to build to standards. Granted, I always test to make sure my sites work with Internet Explorer, Firefox, and Safari. If a employer wants Opera or Konqueror support, that will be extra.

      Ultimately, there are too many inexperienced developers to care about standards. Site owners don't want to spend the money to standardize or don't even know there are standards out there. And let's face it, economics runs the process.

    54. Re:Well, that depends.... by riceboy50 · · Score: 1

      Most "slashdot standards nazis" are people who create websites and therefore have a responsibility to care about more than just whether their site works well in their browser of choice—or even in just the most popular browser. As an enlightened tech-savvy person, I would have thought you'd understand the necessity of standards to foster competition. For example the PC market would be quite a mess if each manufacturer decided to implement their own standards for RAM chips, HDDs, peripheral slots, etc.

      --
      ~ I am logged on, therefore I am.
    55. Re:Well, that depends.... by amn108 · · Score: 1

      Have you been developing Web content yourself? It was a goddamn pain in the ass to be working overtime to acccomodate for the quirks of "the leader" and simultaneously cater for standards. The worst part was not getting payed for the overtime, because the customer was (is?) completely oblivious to the fact that there are millions of people out there who did not use IE even at that time. Even now situation is marginally better when it comes to customer awareness. So it is not about user only, but developers who hate their job, because instead of being truly productive and get their insight from standards documentation they have to dig like rats into internals of a particular technology that noone but vendor knows much about, and dig they do. You missed the "good" days when you had to read a 10 page blog post of a guy who discovered how to make a three column layout work in Internet Explorer 6. That was like, web development on acid, man.

      Opera does not endorse "its own" standard, but the ones outlined by W3C. HÃ¥kon Lie, the Opera guy, has been about standards even before he did Opera.

      Now I hope thats some food for thought for you ;-)

    56. Re:Well, that depends.... by BenoitRen · · Score: 2, Insightful

      Okay, tell me where the document is that defines and explains how IE renders things. What is that? It doesn't exist?!

      You're coding on borrowed time. It's far easier to tweak a standards compliant site that will reliably work in non-IE browsers to work in IE than fumble around with code, hoping that it will display in IE and other web browsers.

      Developing to standards ensures that your website will look how you want it to in browsers to come. Browsers you can't test. You have far less chance of this being the case if your code doesn't conform to a well-defined standard.

      For the record, I actually practice what I preach, and it works well!

    57. Re:Well, that depends.... by gnick · · Score: 1

      I believe the person named 'AmberBlackCat' was obviously offended by your insensitivity to the plight of people with disabilities. And so was I.

      That's what I assumed, and I fully expected that some folks wouldn't like it. And, while I find the ADA flawed in some respects, demanding "reasonable accommodation" seems fine. Like I said in a previous post, "When practical, web-admins should make their pages accessible to the handicapped". I believe that and I would certainly appreciate the assistance if I were the one with the disability. I also admit that I may have adopted an overly heartless tone because I think that Bogtha's implication that "Failure to adhere to HTML standards == Not caring about the handicapped" was kind of B.S. I have handicapped friends and neighbors and I'm guessing that they visit roughly monthly - Apart from my immediate family, 2 wheel-chair ridden individuals make up ~10% of the traffic coming into/out of my house. I care about them and make accommodations, but I don't feel that the fact that I don't have ramps or handicap-accessible bathrooms makes me insensitive. [I realize that home != commercial, I'm just tossing an example out.]

      But I think that you're inferring insensitivity when I intended only a realistic assessment of the situation. Barring interference from the law and assuming that two businesses are on even ground regarding market share, talent pool, etc, the company that focuses 100% on pleasing 99% of their customer base will succeed over the company that divides its resources to take care of everyone. That holds true even if making a poor business decision is the morally right thing to do.

      The ADA may have provisions demanding that sites make themselves handicap accessible, but until those provisions are enforced they mean very little - Loosely enforced provisions do not affect the bottom line. Sad but true.

      Also, I didn't know that about IE8 - Thanks for the heads-up. It's always a relief when we see Microsoft do something right.

      --
      He's getting rather old, but he's a good mouse.
    58. Re:Well, that depends.... by Bill,+Shooter+of+Bul · · Score: 1

      But trying to suggest that this is adhering to web-standards, outside of an intellectual exercise in breaking the boundaries of the semantics of the English language, is rediculous [sic].

      No boundaries of the semantics of the English language were harmed in my previous post (I think, sort of hard to parse that sentence it may have been garbled in transmission, please make sure your sentences are properly sent in accordance with RFC 1149). What every one does is by a definition of the word "standard", a standard. It is at times important when talking to non technical types that they may not know of the formal technical standards that have been agreed upon. They may be using the other definition of standard (as in what every one does).

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    59. Re:Well, that depends.... by Bogtha · · Score: 1

      Perhaps that says more about the complexity of your pages than your skills.

      I wasn't trying to say anything about my skills, I was trying to say something about the difference between programming and markup.

      For example, it's very difficult to get a three column fluid layout that a) works cross-platform and b) validates.

      Not particularly, not when you know the common techniques, e.g. the "holy grail". But any difficulty in that situation has nothing to do with the validity of your HTML, it has to do with understanding the CSS rendering model.

      There are lots of mid-level cases where HTML becomes convoluted because the presentation isn't a simple flat document. It's very difficult to keep that kind of document standards compliant without using a syntax checker that respects those standards

      Why? Simple syntax highlighting catches the typos, indentation catches nesting errors and forgotten closing tags, which just leaves the content model for you to remember. You really find it difficult to believe that a decade isn't long enough to memorise something as simple as HTML? Maybe if you've spent the whole time coasting and not bothering with QA, but if you actually use a validator, and get exposed to what is and isn't correct, how can you not pick it up?

      --
      Bogtha Bogtha Bogtha
    60. Re:Well, that depends.... by morgan_greywolf · · Score: 1

      The ADA may have provisions demanding that sites make themselves handicap accessible, but until those provisions are enforced they mean very little - Loosely enforced provisions do not affect the bottom line. Sad but true.

      You mean until they get sued, or at least hire a legal team worth his or her salt, that is.

      Also, I didn't know that about IE8 - Thanks for the heads-up. It's always a relief when we see Microsoft do something right.

      No problem. Since I do some Web development from time to time, and run Linux, I have the IE 8 beta running under VirtualBox. ;)

    61. Re:Well, that depends.... by hobo+sapiens · · Score: 1

      I agree with Bogtha.

      Do anything for long enough and it becomes part of your nature. This is precisely why people who trot out the old "I don't write standard markup because it takes too long! I have *real* work to do." excuse are just lazy hacks. Once you know how to write good markup, you just do it right the first time. Sure you make mistakes sometimes, but more often than not you can get it right the first time. As for validating, if you use a good validator (like Firefox's tidy validator) the act of validating your page is painless.

      As for the point about not being able to crank out a three column layout perfectly the first time, well, a good css layout actually consists of very little html. It's all in the CSS. Besides, you DO use templating, right? You should only have to write your page's layout code once and just reference it from then on. The real complexity shouldn't be written time and again, it should be in your template. If you have your web site properly designed, you should just be able to write content and the little bit or markup to make that content look right.

      --
      blah blah blah
    62. Re:Well, that depends.... by hobo+sapiens · · Score: 1

      well, if said browser adheres to standards and the site doesn't work, then you need better web developers.

      --
      blah blah blah
    63. Re:Well, that depends.... by hobo+sapiens · · Score: 1

      If you lay out a web page the way you construct an argument, I don't think it matters HOW you code it.

      Sheesh! Mr. http://www.havenworks.com/ is this you?

      --
      blah blah blah
    64. Re:Well, that depends.... by plague3106 · · Score: 1

      I realize that no one choses to be blind... but at the same time, I don't see the need to spend a lot of money I won't get back. Sometimes, life just sucks. Sorry.

    65. Re:Well, that depends.... by nschubach · · Score: 1

      Don't get me wrong, I completely agree. I kind of went about it the wrong way. I'm sure Shakespeare would make much more sense if I viewed it through whatever standard dictionary was out at the time.

      --
      Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
    66. Re:Well, that depends.... by izomiac · · Score: 1

      It seems like economics would push businesses to spend a bit more to make "a very small number of people happy". Say that small number is .5% of internet users. There are ~1.5 billion internet users, so .5% is 7.5 million (~1.5 million if you just care about your continent). Why wouldn't you want a monopoly on those users if your competitors are choosing to ignore them?

      Besides, it's not always a choice for people. .6% of people are blind, >2% have visual impairment, color blindness is fairly common (~7% of males), as is the inability to purchase a fast internet connection or an up-to-date computer due to geographic or financial reasons.

    67. Re:Well, that depends.... by Anonymous Coward · · Score: 0

      Not making pages validate by anyone that calls them self a professional is just plain lazy. If you code your html right the first time, your initial validation errors should be as minor as tacking on a semi-colon to a c program that doesn't immediately compile.

      The reason we validate our pages is not just so we can say we're elite, or to be CSS/HTML Nazis, we do it to ensure it renders correctly on browsers that stick with the standards. From my experiences, it's easier to build for standard complaint browsers first, then go in and hack it a little for IE.

      After you've been in the business a while, you know exactly where you need to throw your hacks in for IE before you are even checking it on IE, so you can throw them in at the same time you are developing for the standards compliance. Then all you have left at the end is the "weird" IE bugs, which in the usual case have something to do with position relative or floats.

      No I'm not one of those people that opposes tables in the design just because you don't "need to use them"... believe me, I know you don't "need them", but it sure does make your life easier when it comes to some of the weird shit graphic designers come up with.

      And I'm posting anonymously because I'm mainly a lurker here and I'm too lazy to fill out the forgot password form.

    68. Re:Well, that depends.... by svank · · Score: 1

      Reverse shield polarity! Fire a tachyon beam through the phaser array! Reroute the standards through the deflector dish!

    69. Re:Well, that depends.... by KDR_11k · · Score: 1

      A flash game is one thing, a web site that implements its navigation menu in flash with no alternative is something else entirely.

      --
      Justice is the sheep getting arrested while an impartial judge declares the vote void.
    70. Re:Well, that depends.... by TheoMurpse · · Score: 1

      Yes, because blink is not defined as conforming in any standard.

      Au contraire, "blink" is proper CSS:
      text-decoration:blink;
      It is an optional CSS property that is defined as the standard, but browsers are not required to recognize it if they choose not to.

    71. Re:Well, that depends.... by blackest_k · · Score: 1

      Strange but in practice I have found that if you make standards based web pages you can largely group opera konquerer firefox safari ect into the group with no problems and then IE into a second group of has varying issues depending on version.

      I have seen problems displaying javadocs in firefox which seems related to a skype plugin in firefox(3.0.3, 3.0.6) and about a month ago ebay.co.uk 's home page locked up ie6 and 7 on Xp (admittedly that page when submitted for testing came up with 600+ errors and over 1100 warnings) Firefox handled the page fine.

      I think if you talk to people who build sites that IE in its various versions is what causes the most problems for a sites design. As a positive note IE gets better with each release. So if your paying for a site to be built ensure that it is standards compliant and eventually there will be little need for a separate css page specifically for ie quirks.

       

    72. Re:Well, that depends.... by TheQuantumShift · · Score: 1

      Right, but it's what the other 95.87% live by. Well, more like the other 5.87%. The remaining 90% live by "It didn't crash IE 6" and call it good.

      --

      Shift happens. Fire it up.
    73. Re:Well, that depends.... by KGIII · · Score: 1

      There is a hell made just for you. Just... For... You...

      --
      "So long and thanks for all the fish."
    74. Re:Well, that depends.... by Anonymous Coward · · Score: 0

      Why is the prior comment scored "Informative"? It's not clear to me that it's factual at all. Can someone cite an example of such a non-standard, but validating page?

    75. Re:Well, that depends.... by tuxgeek · · Score: 1
      Your logic is to accept that there are no standards and M$ rules the day. I say BullShit!
      It takes the same amount of time to code a web page incorrectly as it does to do it right. It's that simple.

      The problem here is that most web site developers are hacks that don't know their asses from a hole in the ground. This is the problem.

      --
      "Suppose you were an idiot...and suppose you were a member of Congress...but I repeat myself." Mark Twain
    76. Re:Well, that depends.... by AnotherDaveB · · Score: 1

      There is a big difference between IE versions. IE7 has markedly fewer quirks than IE6.

    77. Re:Well, that depends.... by gnick · · Score: 1

      It takes the same amount of time to code a web page incorrectly as it does to do it right.

      Double bullshit.
      If you code a page "right", then it will render properly in browsers that adhere to the standards (not IE - possibly excepting IE8 as pointed out by another poster) and satisfy the users with standard-adherent browsers. If you code a page custom-tailored to IE, it will render correctly for 90%+ of your user base. Coding it in such a manor to conform to both will take more time/effort than it would take to conform to either.

      Standards compliant != IE compliant
      IE compliant != Everyone compliant

      You play to your market base, not to what's right. The only exception is when the market objects in a voice loud enough to affect stock price.

      --
      He's getting rather old, but he's a good mouse.
    78. Re:Well, that depends.... by Seraphim_72 · · Score: 1

      Any Professional knows that their site needs to render flawlessly in IE first,

      Any professional knows that it needs to be standards compliant FIRST. I can make you a car that only uses bolts of my own design, it may work, hell it may even work better than a Honda, but do you really want to have to reverse engineer my damn bolts???? If IE and MS don't want to be like SAE that is up to them, but at that point maybe (just maybe) it is time to pull out a new version of their old saw to the tune of "Best viewed in a browser known to be OK by all of the real nerds in the world."

      --
      Slashdot, where armchair scientists get shouted down and armchair theologians get modded up.
    79. Re:Well, that depends.... by AmberBlackCat · · Score: 1

      The comment was not meant to be a counter-argument. It was meant to call you a jackass. I did not comment further because I don't think it's very practical to argue with one of those, and I assumed I would get modded invisible as usual anyway. But I like to answer questions so I will revisit the topic.

      Do you object because I don't advocate spending exorbitant amounts of resources conforming things that are not naturally handicap-friendly to the handicapped or because my argument is not well thought-out? I.e. is this a difference in opinion or a criticism of my train of logic?

      Both. A difference of opinion because I don't consider it to be exhorbitant. A difference of logic because I believe making a website available to the widest audience is an expense in the short term, but maximizes the potential return over the lifetime of the site, so it's practical.

      "Jackass" is a rather vague term, although it confers the tone perfectly reasonably. Are you implying that I'm a jerk because I rebutted the "What about the handicapped?" assertion or are you calling me a moron? I.e. "asshole" or "dumb as a mule"? Possibly both?

      The first one. I think the way you responded was condescending. I'm not disabled myself, so I don't personally need "accessible" webpages. But while you are a realist, I am an idealist. I am also Black, Female, self-proclaimed Christian, and a borderline hippie. If you put all of those together, I'm bound to call a realist a jackass for something.

    80. Re:Well, that depends.... by gnick · · Score: 1

      The first one. I think the way you responded was condescending. I'm not disabled myself, so I don't personally need "accessible" webpages. But while you are a realist, I am an idealist. I am also Black, Female, self-proclaimed Christian, and a borderline hippie. If you put all of those together, I'm bound to call a realist a jackass for something.

      As I said to a previous responder, I may have been overly sarcastic because I found Bogtha's assertion that "Deviation from HTML standards == Hating the handicapped" offensive. I have handicapped friends, but only make the most basic modifications to my lifestyle to accommodate them - I still do not feel insensitive to their needs.

      I respect your ideals - In a completely serious manner, thanks for responding. If it wasn't for the friction likely to be caused by the "self-proclaimed Christian" issue, I'd expect that we'd get along in the real world. You're arrogant, stick to your beliefs even when they're obviously not applicable, and honest. I like that - I'm the same way.

      Personally, I find idealists too idealistic, but I respect the spirit. I used to describe myself as an idealist before my... Conversion... Corruption... Realization... I'm convinced that I see things more clearly now, but I'm probably not as happy as I was before chopping off my pony-tail (literally). Good luck saving the world - In all seriousness, best wishes.

      Cheers.

      --
      He's getting rather old, but he's a good mouse.
    81. Re:Well, that depends.... by Lachlan+Hunt · · Score: 1

      Sure, this page is non-conforming but validates.

      http://damowmow.com/playground/not-html-yet-valid.html

      It's also possible to, for example, include bogus values in attributes that won't be detected by a DTD based validator. e.g.

      <script type="bogus">non-conforming but valid</script>

      (Note that this particular error is caught by the HTML5 conformance checker which checks a lot more than DTDs can.)

      --
      By reading this signature, you hereby agree with the content of the above comment.
    82. Re:Well, that depends.... by Fred_A · · Score: 1

      Actually if browsers just announced errors without failing, it would be more productive IMO.

      A little mandatory bar (like the popup blocked bar or a similar temp widget) announcing "This page contained 103 errors" on each load would probably do wonders to promote a fix.

      Just failing could be dangerous given the complexities of current parsers. No two browsers have the same feature set.

      --

      May contain traces of nut.
      Made from the freshest electrons.
    83. Re:Well, that depends.... by Anonymous Coward · · Score: 0

      Does using "blink" make my code non-standard?

      Yes, because blink is not defined as conforming in any standard.

      You sure about that? I could have sworn blink is in CSS.

    84. Re:Well, that depends.... by Lachlan+Hunt · · Score: 1

      Please read the other comments that said basically the same thing before posting, and then read my reply pointing out that this discussion is about HTML, not CSS.

      --
      By reading this signature, you hereby agree with the content of the above comment.
    85. Re:Well, that depends.... by Anonymous Coward · · Score: 0

      In that case, your clients are fools and you are unprofessional. Designing to standards is the cheapest way to ensure that you reach the widest audience, including future browsers.

    86. Re:Well, that depends.... by Anonymous Coward · · Score: 0

      What does Opera know about what is, and what isn't "Standards-Compliant"? When they only have 0.71% (Q3, 2008) of the web browser market - surely the most "compliant" browser is IE - as it is used the most (72.22% Q3, 2008) - hence a much greater number of websites will be coded for it.

    87. Re:Well, that depends.... by Jellybob · · Score: 1

      You might not use Konqueror, but because it's the basis for Webkit, which runs Safari, it makes a lot of sense to test it.

    88. Re:Well, that depends.... by Anonymous Coward · · Score: 0

      > On the contrary, I'm thinking more along the lines of 'if the standard to do x is using code y, but everyone is using code z to make it work in the
      > browser, then maybe z should become part of the standard'.

      Thanks for promoting an ever more complex and unmaintainable standard that will make sure the number of security issues in browsers will be ever increasing.
      Sometimes you have a point, but most of the time you probably will be just promoting bad practices, standardizing bugs and useless complexity.

    89. Re:Well, that depends.... by leedsj · · Score: 1

      you guys compile TOO much code.. HTML is more like literature - it's a way of getting a message across. It doesn't matter that the i's are crossed and the T's dotted - we're not running nuclear submarines. it just needs to communicate - if it's doing that, it's ok.

    90. Re:Well, that depends.... by david_thornley · · Score: 1

      There's a problem in "Looks good in Internet Explorer and doesn't seem to crash Firefox or Opera" as a standard. New web browsers come out. A significant number of people have Macs of one brand or another, and they will frequently run Safari. I browse a lot on my iPhone, and I have made commercial transactions on it. If you're trying to sell something I might buy, your site needs to work on the iPhone. As smart phones get better and easier to use, there's going to be more of us out there, and frequently we're stuck with one browser.

      In other words, which browsers you need to code for changes over time. Something that works on IE 6 and IE 7 and can be hacked to work on Firefox may satisfy 95% of your customer base right now (although you might well want to go for the other 5%, as they have money also), but that can change. Once you've got a big site laid out for the main current browsers, it's going to be hard to change if Chrome gets popular, or Macs get more popular, or (and this is almost certain) smart phones get more prevalent.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    91. Re:Well, that depends.... by mikael_j · · Score: 1

      Perhaps that says more about the complexity of your pages than your skills. For example, it's very difficult to get a three column fluid layout that a) works cross-platform and b) validates. But that's an extreme example to introduce my point:

      Interestingly enough, I've done several sites with a three column fluid layout that validated fine on the first try and rendered the way they were supposed to in IE, Firefox and Safari. That's not to say that the design was "finished" at that point, still had a lot of little tweaks along the lines of "just how wide should the left column be?", but that's just changing values, the actual layout was rendering as intended on all three major browser families and validated.

      Once you've done the work a few times you tend to know how to get things right the first time, but you'll still end up experimenting wildly when doing something out of the ordinary.

      /Mikael

      --
      Greylisting is to SMTP as NAT is to IPv4
    92. Re:Well, that depends.... by mikael_j · · Score: 1

      ... 'if the standard to do x is using code y, but everyone is using code z to make it work in the browser, then maybe z should become part of the standard'.

      Ah, methinks you are missing the points. The problem could better be described as [a_1...z_1] are the ways that people use to do [1...26], the standard then specifies that [a_2...z_2] are the proper ways to do this, and a lot of times sites will only miss out on a few of these, not everyone breaks the rules in the exact same way. In general I blame this on inexperienced and lazy developers who either don't understand why standards are good (or even that there are standards) or they simply can't be bothered since they'd be forced to relearn, I've worked in an environment where the latter attitude was fairly common, "We'll just do it with tables/frames" and "It's easier to do that with an iframe than with CSS" were typical excuses for using an inferior solution.

      /Mikael

      --
      Greylisting is to SMTP as NAT is to IPv4
    93. Re:Well, that depends.... by Anonymous Coward · · Score: 0

      That's easy. Your clients will point the finger right back at you when they get sued by someone, because they could use one of the sites and it is illegal to discriminate against potential users. And discriminating is exactly what you are doing by not trying to cater for accessibility issues.

    94. Re:Well, that depends.... by billcopc · · Score: 1

      Right, WebKit runs Safari, and Chrome: two browsers that have the carpet-bombing vulnerability, as well as being a bit goofy with the rendering in more situations than I'm willing to tolerate.

      My issue with WebKit is that it doesn't seem to have a real niche. Competing with IE and Firefox is redundant and hopeless. At least Opera have found themselves a cozy place in the mobile/embedded world, where they can actually do some good. At least if WebKit were slim, stable and hyperfast, that would be a very welcome improvement over the competition, and if it could render 95% of the sites I need, I might actually consider it. Right now, it is none of those things, and thus is gets none of my love.

      --
      -Billco, Fnarg.com
  2. How compliant? by TubeSteak · · Score: 1

    Depends on how strict they're being.
    For example, I never close paragraph and line break tags, but otherwise my html is compliant.

    --
    [Fuck Beta]
    o0t!
    1. Re:How compliant? by DrSkwid · · Score: 4, Informative

      It is very simple http://validator.w3.org/

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    2. Re:How compliant? by sakdoctor · · Score: 1

      Are there degrees of strictness?
      If you claim your code is HTML 4.01 or XHTML 1.0 or whatever, then it either is or it isn't.

    3. Re:How compliant? by morgan_greywolf · · Score: 5, Insightful

      Isn't that a bit like saying, "my C code fails to compile whenever I pass it the flag for strict ANSI checking, but other than that my code is ANSI C compliant"?

    4. Re:How compliant? by DZign · · Score: 2, Interesting

      Also depends on how old the websites they searched are..
      only recently added websites or also websites and old pages that exist longer than the standard they validated against exists ?

    5. Re:How compliant? by alexhs · · Score: 1

      I never close paragraph and line break tags, but otherwise my html is compliant.

      In that case I think you're compliant when using the transitional doctype

      --
      I have discovered a truly marvelous proof of killer sig, which this margin is too narrow to contain.
    6. Re:How compliant? by DrSkwid · · Score: 1

      How many websites around now are pre November 1995 when the HTML2.0 standard was released.

      "HTML has been in use by the World Wide Web (WWW) global information initiative since 1990. This specification roughly corresponds to the capabilities of HTML in common use prior to June 1994. HTML is an application of ISO Standard 8879:1986 Information Processing Text and Office Systems; Standard Generalized Markup Language (SGML)."

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    7. Re:How compliant? by Bogtha · · Score: 4, Informative

      only recently added websites or also websites and old pages that exist longer than the standard they validated against exists ?

      MAMA didn't validate against a single document type. They validated against the document type that each individual document claimed to be. So all the ancient HTML 2.0 pages out there will correctly be identified as valid in they are, in fact, valid HTML 2.0.

      --
      Bogtha Bogtha Bogtha
    8. Re:How compliant? by Bogtha · · Score: 2, Informative

      Depends on how strict they're being.

      There aren't degrees of validity. A document is either valid or it isn't. You can't be "more strict" when validating something, if a tool offers you an option like that, then it is doing something other than validating, it's probably linting as well. There's at least one widely-used "validator" that doesn't actually validate at all.

      For example, I never close paragraph and line break tags, but otherwise my html is compliant.

      Yes you do. If you didn't close them, your pages wouldn't work in any browser. What you mean is that you don't explicitly close your paragraph and line break elements. And you don't have to. The closing tags for <p> elements are optional and the <br> element type is empty. Those are not errors.

      --
      Bogtha Bogtha Bogtha
    9. Re:How compliant? by Anonymous Coward · · Score: 0

      closing paragraph and line breaks is not necessary for compliance with some versions of html.

    10. Re:How compliant? by SanityInAnarchy · · Score: 1

      Is there a particular reason you don't?

      Do you understand why XHTML exists? How much more work it is to parse straight HTML, and less work it is for a browser to simply fire up an XML parser instead?

      <br /> isn't that difficult.

      --
      Don't thank God, thank a doctor!
    11. Re:How compliant? by lysergic.acid · · Score: 1

      why don't you close paragraph breaks? both HTML and XHTML require paragraphs to have end tags.

      line breaks don't need to be closed with a separate tag. in XHTML you simply write <br /> just like you would close other empty tags.

      it's not hard to follow conventions that are universal across all browsers. there's no reason to break open standards other than a.) ignorance (which clearly is not the case here since you know you're breaking standards) or b.) your site needs to render on a browser that does not follow web standards.

      i mean, what is achieved by intentionally flouting web standards? saving a couple bytes on your source code?

    12. Re:How compliant? by gnick · · Score: 1

      I think you nailed him - That's a perfect analogy. But, for web sites just like for application users, the target for compliance is not typically the end-user. When I download a new application, I don't care whether it was coded with 'ANSI C compliant' code. I just want it to work properly. When I load a web-page, I don't care if it meets some HTML standard. I just want it to display and function properly in my browser.

      --
      He's getting rather old, but he's a good mouse.
    13. Re:How compliant? by rgo · · Score: 1

      In HTML 4.01, open tags are valid in many cases (like p, br, hr), even in strict mode.
      In fact, if you close some of those tags the validator will warn you that although it is valid to close them, it is better not to do so.

      Also, HTML 5 won't require closing those tags either, only XHTML x.xx require closed tags because they also validate for XML correctness.

    14. Re:How compliant? by rgo · · Score: 1, Interesting

      It is more like saying that the code compiles in the widespread standard C89 but not in barely implementated C99, as analogies to HTML 4.01 and any version of XHTML. They are both standards.

    15. Re:How compliant? by Bogtha · · Score: 1

      why don't you close paragraph breaks? both HTML and XHTML require paragraphs to have end tags.

      No, closing tags for <p> elements are optional in HTML 4, HTML 3.2 and HTML 2. I don't think any version of HTML has required them.

      --
      Bogtha Bogtha Bogtha
    16. Re:How compliant? by skeeto · · Score: 1

      There aren't degrees of validity.

      With XHTML, there are two different types of validation, "strict" and "transitional" (more casual allowing some old-style things). And one may argue, from some certain point of view, that these might be degrees of compliance to XHTML.

      The closing tags for <p> elements are optional and the <br> element type is empty.

      This is true for plain old HTML4, however the newer (and arguably improved) XHTML standard is a bit more strict about it. The XHTML specs, section 4.3 it says "For non-empty elements, end tags are required" and in 4.6 "Empty elements must either have an end tag or the start tag must end with />." That is, for both strict and transitional, all <p> tags must be closed with a closing </p> tag, and <br> is not allowed without either a closing tag or instead as closed start tag, <br/>.

      Now, most browsers won't choke on not closing your paragraph tags and will get along as if you did close them, probably due in great part to HTML4, which is why the grandparent doesn't bother with it, but this doesn't really make it a standard. Implementation defined behavior is not a good way to go about things if you want to have many different compatible browsers (for example, this is why there is only one Perl5 interpreter), because different browsers may choose different ways to handle the ambiguous code.

    17. Re:How compliant? by Myen · · Score: 1

      For example, I never close paragraph and line break tags, but otherwise my html is compliant.

      Yes you do. If you didn't close them, your pages wouldn't work in any browser.

      http://www.w3.org/TR/REC-html40/struct/text.html#h-9.3.1

      <p> has an optional end tag in HTML 4.0. And <br> is forbidden to have an end tag. Sounds like that's perfectly valid to me!

      Being standards-compliant is fun when your standard is so confusing!

    18. Re:How compliant? by Bogtha · · Score: 1

      You missed my point. Please keep in mind the difference between tags and elements. This is "an unclosed p tag":

      <p Hello world!

      This is a <p> element without an explicit closing tag:

      <p>Hello world!

      If you don't close your tags, all your pages will break and no browser error correction will save you.

      --
      Bogtha Bogtha Bogtha
    19. Re:How compliant? by Bogtha · · Score: 1

      With XHTML, there are two different types of validation, "strict" and "transitional"

      No, there are not two different types of validation. There are three different document types, each of which has non-negotiable strict rules.

      And one may argue, from some certain point of view, that these might be degrees of compliance to XHTML.

      One may argue, from some certain point of view that the moon is made of cheese. The fact that somebody might make the argument does not make the concept any more valid.

      If you write a document that conforms to XHTML 1.0 Transitional, it is totally 100% valid and totally 100% in compliance with the XHTML 1.0 specification. You can't get "more valid" or "more in compliance" by switching to Strict. It's considered a best practice, but best practices are not validity or conformance. If they were, then they wouldn't be best practices, they would be required by the specification.

      This is true for plain old HTML4, however the newer (and arguably improved) XHTML standard is a bit more strict about it.

      The OP didn't say that he was using XHTML, he said he was using HTML.

      Now, most browsers won't choke on not closing your paragraph tags and will get along as if you did close them, probably due in great part to HTML4, which is why the grandparent doesn't bother with it, but this doesn't really make it a standard.

      No, it being in a standard makes it a standard.

      Implementation defined behavior is not a good way to go about things if you want to have many different compatible browsers (for example, this is why there is only one Perl5 interpreter), because different browsers may choose different ways to handle the ambiguous code.

      It's not "implementation defined behaviour", the behaviour is defined in the ISO 8879:1986 (SGML) standard, and the closing tags for <p> elements are optional precisely because this can be determined in an unambiguous way.

      --
      Bogtha Bogtha Bogtha
    20. Re:How compliant? by Anonymous Coward · · Score: 0

      I always viewed XHTML as expert HTML.

    21. Re:How compliant? by Jim+Hall · · Score: 2, Insightful

      It is very simple http://validator.w3.org/

      Actually, not quite that simple. My top-level page currently gives 66 validation errors. Guess how many are from content I've had to include from a third party, where I have no control over their standards compliance? 66 of them - 65 are from WebRing, 1 is from a news feed.

      For those of you who are bad at math, that's all of the errors on that page. Note that all my other pages validate just fine, since I don't include third-party content there.

      Being part of the WebRing is still important for my site, so I have to live with the 65 errors. Not much I can do about it, so I wrote some code into the PHP to not display the WebRing content if I pass it a flag/option, and I use that flag when I validate since I know I'll get errors otherwise.

      If there's a better way, let me know.

    22. Re:How compliant? by Anonymous Coward · · Score: 0

      Great, now tell me how I put privileged code through that validator without breaching my confidentiality agreement.

      Yes--I know it's absolutely stupid, it's HTML and any client can read it.... but...that's the terms of it...

    23. Re:How compliant? by pbhj · · Score: 1

      I don't think closing tags were required up to HTML 4.0, but I don't really recall as when I started to design commercially I went in for XHTML1.0 transitional.

    24. Re:How compliant? by BenoitRen · · Score: 1

      XHTML was a good idea, poorly executed. HTML is the way forward. Current web browsers are tag soup parsers with an XML parser tacked on. XML's draconian error handling has no place on the web.

      XHTML isn't necessarily easier to parse than (valid) HTML.

    25. Re:How compliant? by spinkham · · Score: 1

      Wrong.
      HTML 4.01 compliant would pass as compliant in this test. Heck, even valid HTML 2 or 3.2 would be compliant.

      What this survey says is that 96% of webpages have at least one non-standard element included, or other violation of the standards.

      I'd be interested in seeing a more detailed breakdown on the reasons: If a page is 99% standards compliant with one non-standard element for telling the browser not to store the password(for example, reddit.com), that's a lot different from badly nested and missing tags, etc.

      I write and use security tools that parse HTML, and getting them to correctly handle all the poorly formed HTML out their is an absolute b*tch. Even libraries like beautifulsoup that are supposed to handle that still miss and break on a lot of input that modern web browers accept.
      I can't tell you how much easier full XHTML compliance would make my work, but even valid HTML 4.01 would be a FAR improvement over what passes for websites out there.

      Unfortunately, even my employers site is not valid HTML of any sort either... That wasn't one of the qualifications of the system that was chosen, instead ease of use of the system was the qualifier. It claims to be XHTML transitional, but does not validate.

      The good news is that standards compliance is on the rise. They included this table, showing % compliance found in their survey and similar surveys in the past:
      Parnas Dec 2001 0.71%
      Saarsoo Jun 2006 2.58%
      MAMA Jan 2008 4.13%

      They also found that 33% of pages used flash! Really? Noscript has kept me from noticing that I guess..

      --
      Blessed are the pessimists, for they have made backups.
    26. Re:How compliant? by Carewolf · · Score: 1

      Please don't use XHTML. The only way to make it work in IE is to serve it as text/html, and then it is parsed by HTML parsers not by XHTML parsers. On top of that it gets parsed as quirky HTML not even strict.

      No one actually uses XHTML, but many people tries and makes this mistake and just end up getting XML parsed at quirky HTML, which is much worse than just writing strict HTML.

    27. Re:How compliant? by l0b0 · · Score: 1

      Include the content instead of copying it. The content displayed to the user might not be compliant, but at least your web site will be.

    28. Re:How compliant? by guruevi · · Score: 1

      Run it through your own parser and then spit out the relevant stuff in good html. You could also put it in an object tag (<object data="page.html" type="text/html" width="100">) or use some JavaScript to import it after the page has been loaded (given you're not using an XML based option).

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    29. Re:How compliant? by Anonymous Coward · · Score: 0

      I don't really care what IE users see, which is something I can afford because the websites I write are not for people who would be using IE.

    30. Re:How compliant? by lysergic.acid · · Score: 1

      that's technically true. but XHTML requires all tags to be closed. that's why it's better to write line breaks as <br /> and to close paragraph elements with an end tag. this ensures that your code will be future-proof.

      to quote the W3C:

      The XHTML family is the next step in the evolution of the Internet. By migrating to XHTML today, content developers can enter the XML world with all of its attendant benefits, while still remaining confident in their content's backward and future compatibility.

      besides, closing non-empty elements you make the code more organized/legible.

    31. Re:How compliant? by SanityInAnarchy · · Score: 1

      XHTML was a good idea, poorly executed.

      So... your response is to throw it out wholesale?

      XML's draconian error handling has no place on the web.

      That "draconian" error handling is causing problems how?

      I consider it to be a good thing. If I forgot a closing tag, or something like that, an XML parser will tell me, and I can fix it. Even if a "tag soup parser" attacks it later, it will be more likely to do the right thing.

      Yes, having a browser be able to tolerate errors is a good thing, as long as people continue to build things that aren't XHTML. The problem is, exactly which algorithm should a browser use to parse sloppy HTML? Different browsers will parse it in different ways.

      And XML parsers are consistent enough, at this point, that if it doesn't break for you, it's not broken for anyone else. The whole reason for being flexible about what you receive is gone -- it's a bit like trying to tolerate broken ASCII (or Unicode).

      XHTML isn't necessarily easier to parse than (valid) HTML.

      Actually, it kind of is. You just fire an XML parser at it -- any XML parser -- and you have a DOM.

      With HTML, you have to handle tons of quirks and cruft before you even get to the DOM -- where there's still plenty of quirks and cruft to handle before you attempt CSS...

      Of course, it's not necessarily easier for browsers which don't support it, like IE, and... IE...

      --
      Don't thank God, thank a doctor!
    32. Re:How compliant? by BenoitRen · · Score: 1

      So... your response is to throw it out wholesale?

      It wasn't going anywhere. Look at the XHTML2 drafts. It's out of touch with reality.

      As Opera's study confirms, 95+% out there is tag soup, and this is not going to change in the coming 5 years. Supporting XHTML isn't worth it when there's barely any page out there that is actually served as XHTML (or even validates properly as such), even now, after all these years.

      Consider also that XHTML 'solves' only the less important of the real problems, which are the lack of validity, semantics, and separation of content and style.

      That "draconian" error handling is causing problems how?

      No user should be faced with a cryptic XML error when they want to access a page.

      I consider it to be a good thing. If I forgot a closing tag, or something like that, an XML parser will tell me, and I can fix it. Even if a "tag soup parser" attacks it later, it will be more likely to do the right thing.

      That's why the W3 Validator exists. The web browser is a viewer, not a development tool.

      Yes, having a browser be able to tolerate errors is a good thing, as long as people continue to build things that aren't XHTML. The problem is, exactly which algorithm should a browser use to parse sloppy HTML? Different browsers will parse it in different ways.

      That was always a problem indeed. Which is why HTML5 will address this.

      And XML parsers are consistent enough, at this point, that if it doesn't break for you, it's not broken for anyone else. The whole reason for being flexible about what you receive is gone -- it's a bit like trying to tolerate broken ASCII (or Unicode).

      Rendering XHTML properly takes more than just an XML parser. XML has slightly different rules for the DOM, and this impacts JavaScript, for example. The point is that the XHTML mode is much less tested.

    33. Re:How compliant? by SanityInAnarchy · · Score: 1

      It wasn't going anywhere. Look at the XHTML2 drafts.

      XHTML and HTML5 aren't mutually exclusive.

      As Opera's study confirms, 95+% out there is tag soup

      No, Opera's study confirms that it's not standards-compliant. That has nothing to do with whether it's valid XML.

      and this is not going to change in the coming 5 years.

      And how is this an excuse for letting your own tags slide?

      Supporting XHTML isn't worth it when there's barely any page out there that is actually served as XHTML (or even validates properly as such), even now, after all these years.

      Supporting XHTML, and XML namespaces, even if you cheat on it with the occasional script tag, still gives you microformats. And believe it or not, browsers are not the only things trying to crawl your crappy HTML.

      No user should be faced with a cryptic XML error when they want to access a page.

      Nor should users be faced with a cryptic 404 error, but shit happens.

      And if you put a page out there as XHTML, and left off a closing tag, you absolutely deserve for your users to see a cryptic XML error -- because it means you never bothered to check it yourself.

      The web browser is a viewer, not a development tool.

      Spoken like someone who has never done actual web development. Have you heard of Firebug?

      --
      Don't thank God, thank a doctor!
    34. Re:How compliant? by BenoitRen · · Score: 1

      XHTML and HTML5 aren't mutually exclusive.

      You can use XHTML with HTML5, but the focus is on HTML. The sole deciding factor will be the MIME type. We all know where this leads...

      No, Opera's study confirms that it's not standards-compliant. That has nothing to do with whether it's valid XML.

      How about the study done by Ian Hixie, then? The result of that study was that 95% of the web is tag soup, malformed HTML.

      And how is this an excuse for letting your own tags slide?

      Of course not, and I wasn't implying as such.

      Nor should users be faced with a cryptic 404 error, but shit happens.

      That's something you can't always avoid, and for which there is no fallback content or possible recovery, save for a custom 404 error page.

      And if you put a page out there as XHTML, and left off a closing tag, you absolutely deserve for your users to see a cryptic XML error -- because it means you never bothered to check it yourself.

      No. Users who had nothing to do with the development of the page do not deserve it.

      Spoken like someone who has never done actual web development. Have you heard of Firebug?

      Of course I have. It's not compatible with SeaMonkey, though. I use the DOM Inspector. I've done a fair share of web development, actually. In HTML4 Strict!

      Firebug and DOM Inspector are web development tools that hook into the web browser. That doesn't make the web browser itself a development tool.

    35. Re:How compliant? by SanityInAnarchy · · Score: 1

      Users who had nothing to do with the development of the page do not deserve it.

      Again, you're assuming users will ever see this page. Why would they?

      It's kind of like avoiding ODF because someone could leave off a closing tag. I suppose technically they could, but it's no longer something we have to hand edit.

      It's also a bit like suggesting that Javascript parsers should be able to detect (and compensate for) missing close brackets.

      --
      Don't thank God, thank a doctor!
    36. Re:How compliant? by DrSkwid · · Score: 1

      You download it and run it internally.

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    37. Re:How compliant? by BenoitRen · · Score: 1

      Again, you're assuming users will ever see this page. Why would they?

      Because shit happens? I know I saw a pretty XML error a year back or so when I tried to visit the site that had the Home Button extension. It also happened for a long time with Microsoft's Live Spaces. There are other documented instances out there if you look them up.

      It's also a bit like suggesting that Javascript parsers should be able to detect (and compensate for) missing close brackets.

      A scripting language is a totally different beast than a mark-up language.

    38. Re:How compliant? by SanityInAnarchy · · Score: 1

      Because shit happens?

      Shit happens regardless. I'd rather have instant feedback when shit happens.

      A scripting language is a totally different beast than a mark-up language.

      A parser is a parser is a parser. Why should HTML be less strict than Javascript? Be more specific than "they're different"...

      --
      Don't thank God, thank a doctor!
    39. Re:How compliant? by BenoitRen · · Score: 1

      Shit happens regardless. I'd rather have instant feedback when shit happens.

      Then what's stopping you from using the W3 Validator or a browser extension that validates locally? As a bonus, it will check for more than just "are all the elements closed neatly"?

      A parser is a parser is a parser. Why should HTML be less strict than Javascript?

      The difference matters because JavaScript has no set structure, while HTML does. You can make educated guesses on what is missing in many cases.

      As for why HTML should be less strict... This way we have a low barrier for entry for newbies who want to make their own page. There's also user-generated and third-party content that you can't always control. Finally, there are legacy pages and legacy tools that don't always output good HTML, which can't always be fixed or replaced.

    40. Re:How compliant? by SanityInAnarchy · · Score: 1

      JavaScript has no set structure, while HTML does.

      How so?

      If I forget so much as a comma, a semicolon, or a close bracket, there's a fair chance that my entire Javascript file will be thrown away. I actually strongly dislike how tolerant the Firefox parser is, as it means that this will occasionally happen only on certain other browsers, and not on Firefox.

      This way we have a low barrier for entry for newbies who want to make their own page.

      Newbies aren't editing raw HTML, they're using WYSIWYGs. And no WYSIWYG should be putting out invalid markup.

      If newbies were editing raw HTML, then they absolutely should be seeing XML parse errors. Let them develop good habits early.

      There's also user-generated and third-party content that you can't always control.

      HTMLtidy. Or parse it and pull out just what you want.

      That parsing part, by the way, is again made easier by actual XHTML, rather than tag soup. Especially if what you want is kept in some sort of microformat.

      Finally, there are legacy pages and legacy tools that don't always output good HTML, which can't always be fixed or replaced.

      If we're talking about legacy pages, those would be served as HTML, not XHTML. I see no reason they should have any bearing on which I choose to develop with for the future.

      --
      Don't thank God, thank a doctor!
    41. Re:How compliant? by Bogtha · · Score: 1

      that's technically true.

      Well we are discussing a technical matter...

      but XHTML requires all tags to be closed.

      So? The person you were responding to said he was using HTML. And the thing I took issue with was your claim that "both HTML and XHTML require paragraphs to have end tags". It's not "a technicality" to point out how wrong this is, it's a basic fact about the syntax rules, the very topic of discussion.

      that's why it's better to write line breaks as <br />

      No! It's better to write line breaks as <br> when you are using HTML, like the OP said he was, and as <br /> when you are using XHTML. You don't just pick one that is "better" because neither is better, one is always wrong for HTML and one is always wrong for XHTML.

      this ensures that your code will be future-proof.

      No, it doesn't. Adhering to the syntax rules of the document type you are using aids transitions, fucking things up by doing things like using XHTML syntax in an HTML document only makes it more difficult to do automatic conversions because you are working with non-standard code.

      to quote the W3C

      Most developers can't "migrate to XHTML today" because Internet Explorer doesn't support it. And in any case, migrating to XHTML and using XHTML syntax in an HTML document are two entirely different things. You want to tell him to use XHTML instead of HTML? Go ahead. I'll disagree with your subjective opinion, but you won't be objectively incorrect. But you want to tell somebody using HTML that he should write <br /> ? No. Wrong. And pointing out that the W3C tells people that migrating to XHTML is good can't save you with that.

      besides, closing non-empty elements you make the code more organized/legible.

      The topic here is validity, not legibility.

      --
      Bogtha Bogtha Bogtha
  3. More like by ODiV · · Score: 5, Funny

    OMG 4.13% of the Web is Standards-compliant!?

    1. Re:More like by WK2 · · Score: 1

      I agree. That number seems implausibly high.

      --
      Write your own Choose Your Own Adventure. http://www.freegameengines.org/gamebook-engine/
    2. Re:More like by Yvan256 · · Score: 1

      Drugs are bad, mmmkay?

    3. Re:More like by rgo · · Score: 1

      Yeah, and I betcha that's the spam and porn free part of the web. Cause who would care about correctness (HTML or moral) when you are trying to sell fake watches and transexual horse porn.

  4. W3C by eldavojohn · · Score: 4, Informative

    W3C's validation tools

    Normally I'd go on my own rant but I'm feeling lazy today and recently I read a good article at A List Apart that sums it up. As for the W3C, I like this list they compile:

    W3C's Pros & Cons

    Pros:

    • Global
    • Academic and scientific body
    • Multiple interests represented, but mostly from paid member companies
    • Attempting to be more open via certain teams such as the HTML5 and CSS Working Groups
    • Attempting to appeal more to work-a-day world via redesigns, blogs, and more human-friendly language throughout the site

    Cons:

    • Creates "open standards" by ideal, not necessarily fact
    • Incredibly slow moving in a highly evolutionary environment
    • Poor economic model that relies on membership monies
    • Discourages independents and open process
    • Passive: only creates specs and recommends, does not do real outreach
    • "Ivory tower" perception

    You should read that article, it's pretty spot on for this subject.

    --
    My work here is dung.
    1. Re:W3C by morgan_greywolf · · Score: 1

      Um...isn't that pro/con list rather contradictory?

    2. Re:W3C by Bogtha · · Score: 5, Insightful
      • Incredibly slow moving in a highly evolutionary environment

      That's hilarious. We still can't use CSS tables or generated content on the web - features that were published by the W3C in the CSS 2 specification over a decade ago because Internet Explorer doesn't support them yet. We need to use JavaScript frameworks or otherwise normalise event handling because Internet Explorer doesn't support DOM 2 Events - a specification published by the W3C eight years ago (event Internet Explorer 8 won't support this). And SVG anyone? XHTML? MathML?

      Get back to me when browsers make it out of the 90s before telling me the W3C is "incredibly slow moving".

      --
      Bogtha Bogtha Bogtha
    3. Re:W3C by schklerg · · Score: 1

      The Pros seem like the idea, with the Cons the reality.

      --
      Be Excellent To Each Other
    4. Re:W3C by SanityInAnarchy · · Score: 1

      In fact, this is pretty much entirely due to IE.

      Do you suppose, if Google started blocking IE from their homepage by user-agent, that the situation would improve?

      --
      Don't thank God, thank a doctor!
    5. Re:W3C by Jeff+Hornby · · Score: 1

      I think it would be a great boon for LiveSearch.

      Let's face it, the average user isn't going to think to blame their browser, they're going to blame Google.

      --
      Why doesn't Slashdot ever get slashdotted?
    6. Re:W3C by Anonymous Coward · · Score: 0

      As an actual Web dude myself, I say ditto on this! Nothing is more aggravating to me than browsers that fail to implement standards, and correctly. They ALL fail to some extent in that regard. Though I must say that some are better than others...

    7. Re:W3C by barzok · · Score: 1, Insightful

      Let's face it, the average user isn't going to think to blame their browser, they're going to blame Google.

      Unless Google puts on the page "your browser is an ancient, decrepit, backwards, non-compliant, security-hole-ridden POS. Upgrade now" with links to Opera, Firefox, Chrome, Safari and any other reasonably decent browser.

    8. Re:W3C by Jeff+Hornby · · Score: 1

      Most people (and when I say most people I mean non-technical people) don't think about their choice of browser. When they want to search for something, they "Google" it, the don't "Internet Explorer" it. They'll only understand that "I went to Google and it didn't work. What else can I use?"

      And Google is not stupid enough to alienate 80% of the people surfing the web, especially when they depend so much on their search business to drive their advertising revenue.

      --
      Why doesn't Slashdot ever get slashdotted?
    9. Re:W3C by jabelli · · Score: 1

      Google is not exactly the poster-child for W3C compliance. I've seen lots of web pages that are compliant, except for the Google ads. Also, their home page is not even compliant.

    10. Re:W3C by Anonymous Coward · · Score: 1, Insightful

      Ah yes, incredibly slow-moving and punitive.

      IE was the first browser to implement CSS 2 as specced by the W3C, who then, faced with a working implementation from a large company, decided to make major changes to the spec. Microsoft said "sod this for a game of soldiers" and the web we have today is a testament to the W3C's utter stupidity.

    11. Re:W3C by Anonymous Coward · · Score: 1, Informative

      Oh come on, what the hell is with the Warning about the &tab thing?

      It is inside a URL for crying out loud, did W3C forget that URLs can use &any-word=something-else?
      Oh wait, they say that you need to encode them even inside a URL... well, that kinda takes the biscuit...

      Also, what is with the terrible wording here?
      "This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details."
      Someone should rub it in W3Cs nose that they aren't perfect either. (i shall be doing so in a second)

    12. Re:W3C by Bogtha · · Score: 3, Insightful

      IE was the first browser to implement CSS 2 as specced by the W3C, who then, faced with a working implementation from a large company, decided to make major changes to the spec.

      This is quite simply delusional. Here is the first released specification for CSS 2. Go and read the tables section. Go and read the generated content section. Go and find out when Internet Explorer had a working implementation of these features. Then go and inform Microsoft, because they, along with the rest of the world, seem to be under the impression that these are new features in the Internet Explorer 8 betas.

      In actual fact, there have been changes made to CSS 2 that make Internet Explorer more compatible. For instance, display: inline-block was originally an Internet Explorer proprietary feature that was added to CSS 2.1.

      --
      Bogtha Bogtha Bogtha
    13. Re:W3C by Bogtha · · Score: 1

      It is inside a URL for crying out loud, did W3C forget that URLs can use &any-word=something-else?

      Yes, it's inside a URL. And that URL is inside HTML for crying out loud. Did you forget that ampersands need to be encoded inside HTML?

      Someone should rub it in W3Cs nose that they aren't perfect either. (i shall be doing so in a second)

      Please, just grow up instead. It's like whining that a spelling checker is pointing out mistakes. Just because somebody builds a tool to find errors, it doesn't mean they are attacking you or saying that they are perfect themselves, and pointing out things that they've got wrong doesn't make your mistakes disappear.

      --
      Bogtha Bogtha Bogtha
    14. Re:W3C by Anonymous Coward · · Score: 0

      I believe you should grow some humor, it was obviously a joke.
      You haven't been on here long, have you?

    15. Re:W3C by Curate · · Score: 1
      Do you suppose, if Google started blocking IE from their homepage by user-agent, that the situation would improve?

      The situation would certainly improve for Live Search and Yahoo Search...

    16. Re:W3C by dtabraha · · Score: 1

      W3C might move fast, but not in an "evolutionary environment".

      I believe by this they're implying slowness in adopting mutations outside of the W3C's own developments, hence the other con listed as the "ivory tower" perception.

      There's a big difference between de jure standards and de facto standards.

      Browser market share defines what standards are de facto, and the W3C defines what standards are de jure.

      I prefer the de facto route honestly, let companies come up with new developments themselves and let the consumers be the judge of whether to use the browser.

    17. Re:W3C by SanityInAnarchy · · Score: 1

      Google is officially a verb. IE isn't.

      --
      Don't thank God, thank a doctor!
    18. Re:W3C by SanityInAnarchy · · Score: 1

      When they want to search for something, they "Google" it, the don't "Internet Explorer" it.

      Which is exactly the point.

      If they want to search for it, and it doesn't work, I imagine they'll assume something is wrong with their computer, or the Internet, or even their browser, if they know what that is.

      And yes, Google.com has been down. And when this has happened, that was exactly the reaction.

      They'll only understand that "I went to Google and it didn't work. What else can I use?"

      No, they'll understand "I wanted to Google and it didn't work. How can I fix it?"

      How they interpret "fix it" is up for debate. But I'm guessing Google is far, far more popular than IE right now.

      Maybe the problem is that it's so easy to swap one search engine for another?

      Consider: What if Myspace started doing that? How many people would actually drop Myspace for Facebook (who haven't already)?

      --
      Don't thank God, thank a doctor!
    19. Re:W3C by Anonymous Coward · · Score: 0

      Get back to me when Internet Explorer make it out of the 90s before telling me the W3C is "incredibly slow moving".

      There, fixed that for you.

    20. Re:W3C by Jeff+Hornby · · Score: 1

      My point is that people don't think about the browser, their focus is on the site they're at. It's only technical people like us (and I assume that you are in some way technical from the way you write) that think about things like the browser and the operating system. To most people searching the internet, they are using the computer and they are using Google. They're not even aware that they are using Linux or Windows, wouldn't be able to tell you what a shell is, and are only vaguely aware what the browser is. Because IE is part of the background, they won't think to blame IE.

      If MySpace started screwing around so that they didn't work in IE, they would have the same problem. IT would take longer because people have invested a lot of time in their MySpace pages and so will accept a little more pain to avoid switching but eventually more and more people would move to Facebook and MySpace would disappear.

      --
      Why doesn't Slashdot ever get slashdotted?
    21. Re:W3C by Jeff+Hornby · · Score: 1

      Which is exactly my point.

      --
      Why doesn't Slashdot ever get slashdotted?
    22. Re:W3C by SanityInAnarchy · · Score: 1

      My point is that people don't think about the browser, their focus is on the site they're at.

      And my point is that most people do realize computers "break", and if Google tells them their computer is "broken" somehow, they'll believe it.

      Because IE is part of the background, they won't think to blame IE.

      Even if there was a big page from Google saying so?

      IT would take longer because people have invested a lot of time in their MySpace pages and so will accept a little more pain to avoid switching but eventually more and more people would move to Facebook and MySpace would disappear.

      Do you honestly believe that these people who have so much invested in Myspace -- so much so that they'll download a Myspace-specific IM client -- wouldn't install a good browser in order to use Myspace?

      Your assumption is that people would simply tolerate Myspace not working, and not use it, until they'd gotten everyone switched over to Facebook. I sincerely doubt that. It seems far more likely that they'd install Firefox at least once before doing this -- and, since the web browser is so transparent to them, they'd forget that there was ever a problem.

      --
      Don't thank God, thank a doctor!
    23. Re:W3C by Nicolay77 · · Score: 1

      Google can't do that. But a security policy in all companies, can let us do it.

      So you block the Web by HTTP_USER_AGENT.

      IE gets a whitelist of job related domains, a secure browser like Firefox or Opera gets to browse the entire net.

      Then, a HUGE part of the population will use other browsers.

      --
      We are Turing O-Machines. The Oracle is out there.
  5. I wonder if by Jane_Dozey · · Score: 2, Interesting

    I wonder if they're throwing away every page that doesn't fully comply or if they're actually including the pages that almost comply but have a typo or missing doctype or missing closing tag. I'm guessing the former by the numbers which seems a little unfair to me.

    --
    Silly rabbit
    1. Re:I wonder if by Anonymous Coward · · Score: 1, Insightful

      Why is it unfair? If you're going for compliance for a good reason, a missing doctype or tag could be pretty serious. Try and run a page with a missing closing tag through a parser other than a web-browser once and see how minor an issue it is.

      If you're going for compliance just because you can, it's not big deal, but you're still non-compliant.

    2. Re:I wonder if by Anonymous Coward · · Score: 0

      A missing closing tag where one is required is an error and shouldn't validate. I wonder about warnings. A webpage without any error but full of warnings, does it count as valid?

    3. Re:I wonder if by thetartanavenger · · Score: 1

      A typo makes something non-standards compliant. Missing/not closing a tag makes it non-standards compliant. There's no question of fairness about it, it's just fact.

      Trying to make your page standards compliant (or as close to as you can without breaking the shittier of web browsers) is a good thing to do, but there are easy ways of checking if it is or not, so the laziness not to correct the typo/close the tag is the writers problem, not the standards makers.

      --
      Who need's speling and grammar?
    4. Re:I wonder if by Bogtha · · Score: 1

      Why is it unfair?

      An immense number of people are taught in school that so long as you try, it doesn't matter if you don't succeed. It's for self-esteem or something. So they grow up thinking that if they make even the barest half-hearted attempt at getting it right, it's "unfair" to point out that they have in fact failed.

      --
      Bogtha Bogtha Bogtha
    5. Re:I wonder if by Jane_Dozey · · Score: 1

      What I was trying to say is that some pages are 99.9% compliant but the author forgot to put in that extra "\" at the end of an input field. I know I've done it before and unfortunately forgot to re-run it through a validator. The page rendered and behaved just fine in every browser I threw at it but in this case it would be thrown into the same box as pages that are not even trying

      --
      Silly rabbit
  6. Only 4.13% of the Web Is Standards-compliant ... by cosmocain · · Score: 4, Insightful

    ...the rest just renders perfectly in IE.

    (i would prefer if there wasn't any truth in it.)

  7. Some standards are just too strict... by Spy+der+Mann · · Score: 1

    For example, xhtml-strict does not include support for "target" attributes in links. What kind of idiotic decision was that?

    So, people then choose xhtml-transitional, which is much more relaxed, etc.

    Another thing is the inclusion of embedded xml inside html, which due to lack of support in the standards, completely break "standards-compliance", whatever that means.

    Now, if you're talking about DOM, then that's another story.

    1. Re:Some standards are just too strict... by sakdoctor · · Score: 4, Insightful

      Well not in the least bit idiotic actually.
      It's up to me as a user to choose where a url opens, especially since we are all using the tabbed paradigm now.

    2. Re:Some standards are just too strict... by mikael_j · · Score: 3, Informative

      For example, xhtml-strict does not include support for "target" attributes in links. What kind of idiotic decision was that?

      A very good decision, there are two main uses for the "target" attribute:

      • Frame-based sites - Old-school, annoying way of designing sites that I and many others feel should not be used for new sites.
      • To automatically open links in a new window - Annoying behaviour by web developers who think no one could possible want to, god forbid, leave their site in favor of another site.

      /Mikael

      --
      Greylisting is to SMTP as NAT is to IPv4
    3. Re:Some standards are just too strict... by hansamurai · · Score: 2, Interesting

      The lack of a target attribute really bothered me when I first ran into it. Their argument was something like how websites shouldn't be controlling the browser, as in creating tabs/windows, etc. Of course you can hack it in with Javascript which is something I refused to do, what's the point of striving to be standards compliant when you break it a minute later with Javascript? Anyways, I thought about it and kind of agreed with the notion, so now I just externally link a lot less.

    4. Re:Some standards are just too strict... by flynt · · Score: 0, Troll


      tabbed paradigm

      Who do you think you are?
      Surely not Kuhn
      You probably thought it deep
      When Neo said "no spoon"

      I'd finish this poem
      but there's no word to rhyme
      with so pretentious a concept
      as 'tabbed paradigm'

    5. Re:Some standards are just too strict... by El_Muerte_TDS · · Score: 1

      I wouldn't want to browse API documentation in a non-frame based environment.

    6. Re:Some standards are just too strict... by 0100010001010011 · · Score: 1

      There are good and bad times to open a new window. I use it on my sites for when ever I'm showing a Map to something. "This week's game will be played Here (Map)". That lets me link to google maps. If it's something on my 'link' page then I let it open in the current window. It's the difference between an aside and a new paragraph.

    7. Re:Some standards are just too strict... by tepples · · Score: 4, Informative

      It's up to me as a user to choose where a url opens, especially since we are all using the tabbed paradigm now.

      User agents currently do not allow the user to submit a form into a new window or tab. This is the nearly nine-year-old bug 17754 on bugzilla.mozilla.org with 99 votes.

    8. Re:Some standards are just too strict... by l0ungeb0y · · Score: 4, Interesting

      XHTML-STRICT is not for everyone, it's intended for those (like me) who are more development oriented and wish to completely separate structure from presentation. A "target" attribute is clearly a presentation attribute since it defines how the linked reference is presented to the user and as the parent noted, it should be up to the user to make that choice.

      When wanting to control presentation in XHTML STRICT, you should use DOM or CSS, that way, they structure (XHTML) is removed from the presentation (JS/CSS). I typically link all scripts and stylesheets. That way the XHTML is made portable in terms of data with the JS/CSS being limited to only effecting a web client. In the OPs case, a simple ID attribute for that particular anchor would work just fine, you could bind an event listener for a click event to that element and then execute your javascript popup code when that event is triggered, canceling the event so that the browser does execute the link on it's own. That way, your default browser clients could execute the JS instructions, while a 3rd party app (an AIR desktop or mobile device) could put their own custom behavior in if desired.

      While that sort of practice may seem extreme to a designer, as a developer I can swear to it's scalability and transportability for supporting 3rd party access such as when developing a web UI that needs to support many types of clients via one codebase.

      If none of those features make sense nor strike you as worthwhile, I suggest you stick to XHTML TRANSITIONAL, which is probably better suited to your needs.

    9. Re:Some standards are just too strict... by Bogtha · · Score: 1

      User agents currently do not allow the user to submit a form into a new window or tab.

      Webkit based browsers do.

      --
      Bogtha Bogtha Bogtha
    10. Re:Some standards are just too strict... by Relic+of+the+Future · · Score: 1
      I am so full of hate at sites that continually want to open new windows. When I can, I use a browser that lets me turn that off. So what's the point of you breaking the standard in ugly javascript, only to have me turn it off?

      You don't need multiple windows. If you think you do, you're wrong. If you're not wrong *I'll* open a new window.

      --
      Those who fail to understand communication protocols, are doomed to repeat them over port 80.
    11. Re:Some standards are just too strict... by foniksonik · · Score: 1

      Actually there is another very good use for automatically opening a window (not mentioning target as it's just a vehicle to get you there)

      When a link is possibly important to a user but would in fact break the flow of their current activity, a link should be set to open in a new window - preferably one which does not go full screen to hide the window they are really using.

      This is a usability issue. You should not make the user think about having to open a link in a new tab or window if they click a link to something like a privacy policy while filling out a form.

      You have completely ignored the possibility of opening a new window which is still within the site but is tangential to the user's main activity.

      --
      A fool throws a stone into a well and a thousand sages can not remove it.
    12. Re:Some standards are just too strict... by SanityInAnarchy · · Score: 1

      I wouldn't mind it -- have you seen some of the better API doc sites?

      What's more, "no frames" doesn't have to imply "no frame-like behavior" -- CSS can give you a little box whose contents scroll independently of the parent, and Javascript can give you links that don't refresh the entire page.

      --
      Don't thank God, thank a doctor!
    13. Re:Some standards are just too strict... by SanityInAnarchy · · Score: 2, Informative

      Not really a lot of point to it, though -- savvy users will simply middle-click on the link if they want it in a new tab/window. If they don't, that generally implies they want it right where it is, and your attempt to open a new tab/window is going to be annoying.

      But hey, at least using a target for that is better than linking to a javascript: URL. A lot of sites are even worse -- they add an onClick event, and they set the link href to #, or to javascript:void(), meaning that middle-clicking on it inevitably does something unexpected.

      My preferred method (if I ever need to force a new window) is to use a plain old link, and progressively enhance it with Javascript to open a new window. That way, if people middle-click, it does exactly what they want.

      --
      Don't thank God, thank a doctor!
    14. Re:Some standards are just too strict... by SanityInAnarchy · · Score: 1

      Of course you can hack it in with Javascript which is something I refused to do, what's the point of striving to be standards compliant when you break it a minute later with Javascript?

      Well, Javascript is a standard.

      I prefer progressive enhancement -- make the link a plain old link, and useful on its own, then override onClick to do whatever you want. Browsers that support middle-click-open-in-new-tab don't seem to count that as an onClick event.

      --
      Don't thank God, thank a doctor!
    15. Re:Some standards are just too strict... by hansamurai · · Score: 1

      Javascript may be a standard but I don't consider it an excuse to break usability. I use Noscript and I don't even bother to explore sites that are totally borked without their Javascript crutch. I spend a lot of time making sure everything works whether Javascript is on or not.

    16. Re:Some standards are just too strict... by mikael_j · · Score: 1

      Ah yes, for those special purposes it can be useful, unfortunately it has been proven that by giving developers the possibility of opening links in a new window/tab is something that will be abused, especially by people who seem to think that their site is oh-so-important and that the user couldn't possibly want to leave it.

      /Mikael

      --
      Greylisting is to SMTP as NAT is to IPv4
    17. Re:Some standards are just too strict... by Corporate+Troll · · Score: 1

      I think you just should take a look at the Google Maps API and embed the maps directly instead of linking with an annoying popup window.

    18. Re:Some standards are just too strict... by lysergic.acid · · Score: 1

      why? so you can save .025 seconds by not reloading an index or menu?

      there's no good reason to use frames or even iframes in a modern site. it's bad for search engine indexing, and it's bad for usability. that is why major API documentation sites like those for the YUI Library, MySQL, PHP, and even MSDN do not use frames in their layout.

      even if there were a need to keep persistent layout elements, you can use AJAX to simulate all of the desirable behaviors of frames/iframes without the drawbacks.

    19. Re:Some standards are just too strict... by Corporate+Troll · · Score: 1

      Have a link, that shows a hidden div. User clicks, div becomes visible, user clicks again, div becomes invisible. No need for popups.

    20. Re:Some standards are just too strict... by Sancho · · Score: 1

      Sites requiring the use of Javascript are pretty evil. And what CSS style are you referring to--I don't think I've run across that one. Usually, when I see behavior like that, it's an iframe.

    21. Re:Some standards are just too strict... by Sancho · · Score: 1

      The web is not, and should not be designed for savvy users.

      Savvy users will get around the stupid measures put into place for everyone else.

    22. Re:Some standards are just too strict... by Sancho · · Score: 1

      *fills out a long web form*
      *gets to bottom of page, sees privacy policy*
      *thinks "Hmm, there's a lot about privacy and facebook on the news, maybe I should check this out*
      *clicks policy. policy opens in current window.*
      *reads policy*
      *clicks back*
      *screams as entire form has been erased*

    23. Re:Some standards are just too strict... by lattyware · · Score: 1

      overflow is what you are looking for, I believe.

      --
      -- Lattyware (www.lattyware.co.uk)
    24. Re:Some standards are just too strict... by Bogtha · · Score: 2, Insightful

      When a link is possibly important to a user but would in fact break the flow of their current activity, a link should be set to open in a new window - preferably one which does not go full screen to hide the window they are really using.

      If you use the target attribute, you have no control over the size of the window and it is very likely that it will obscure the current window. You need JavaScript to get the effect you desire, and if you are using JavaScript, why bother with a new window when you can dynamically display the content in the context of the current page?

      --
      Bogtha Bogtha Bogtha
    25. Re:Some standards are just too strict... by vadim_t · · Score: 1

      That's easy, so long it's a normal link and not some weird JS thing, I can middle click the link and open it in a new tab. That way I get to choose whether I want to replace the current page with a new one or not.

      And why should the form get erased? My browser (konqueror) certainly doesn't do that.

    26. Re:Some standards are just too strict... by CaptSaltyJack · · Score: 1

      Exactly.

      So, web devs, let your users decide. Give the 'rel="external"' attribute to your external links, and put a simple checkbox or dropdown on your web site saying "Open external links in new tab/window?" And if that option is enabled.... (jQuery code follows)

      $('a[href!=""][rel="external"]').attr("target", "_blank");

      Problem solved.

    27. Re:Some standards are just too strict... by Sancho · · Score: 1

      Just because the tools you use work that way does not mean that the majority of them do.

      I wonder how many people actually think to open links in new windows/tabs? Geeks aside, I bet it's pretty few.

    28. Re:Some standards are just too strict... by kchrist · · Score: 1

      'position: fixed;' is the CSS property/value that can give you that. The linked page explains it and also shows an example.

    29. Re:Some standards are just too strict... by Sancho · · Score: 1

      That's a little different from what I was picturing. "A box whose contents scroll independantly of the parent", compared to what I would describe as "an element always visible at the same position of the page, irrespective of the parent's scroll position."

      Slashdot has the latter if you're using D2 with Javascript enabled.

    30. Re:Some standards are just too strict... by coryking · · Score: 1

      The big problem with that approach is that depending on were you put the javascript that does the prgressive enhancement, there could be a few seconds where the javascript hasn't "hooked into" the HTML and added it's magic.

      This is especially true when a visitor is on a slower connection. Those visitors will click on the non-progressive link and get, for them, unexpected behavior.

      Unless I'm missing some "right way" to do what you suggest, and if there is, please let me know because I think, minus the technical problems, progressive enhancement is the right way to go.

    31. Re:Some standards are just too strict... by icebrain · · Score: 2, Insightful

      The trick is making it work for the average or new person, while not screwing it up for the experienced. For this example, if you want the link to open in a new window with a normal click, make sure that middle-clicking on the link doesn't break it.

      --
      The meek may inherit the earth, but the strong shall take the stars.
    32. Re:Some standards are just too strict... by Mystra_x64 · · Score: 1

      That's why you should have used Opera.

      --
      Quick way to get 30% Funny 70% Troll: defend Opera browser on /.
    33. Re:Some standards are just too strict... by Spy+der+Mann · · Score: 1

      Javascript may be a standard but I don't consider it an excuse to break usability. I use Noscript and I don't even bother to explore sites that are totally borked without their Javascript crutch. I spend a lot of time making sure everything works whether Javascript is on or not.

      Exactly! With the constantly found vulnerabilities in javascript, there must be a fallback so that links CAN be opened in a new window (or a specific window for that matter).

      The problem I have with the target attribute is that some websites have abused it (target=_blank). Just as websites abuse javascript by making it painfully slow (digg, can you hear me?).

      What use is forcing arbitrary restrictions for people who want to do things right, and yet allowing everyone else to break the web as they please?

      In the first place, if standards (HTML / CSS) had been designed right, we wouldn't need so many javascript workarounds.

      Idea: specifying target in XHTML-strict webpages.
      Justification: To have better control of which frame/window receives a certain info (like help pages)
      Excuse not to implement it: The user should decide!
      Workaround: Javascript and using the rel="external" attribute.

      Idea: Client-side includes.
      Justification: Save redundancy, bandwidth (for example, in menus - and to save us from using frames. Did you know blogger uses an iframe for its top menu?)
      Excuse not to implement it: SSI works just as well.
      Workaround: AJAX.

    34. Re:Some standards are just too strict... by kchrist · · Score: 1

      That's easy too. Give a 'position: fixed' box a specific height and it will automatically grow a scrollbar if the contents extend beyond the height you specified. If you use JavaScript to get the size of the viewport (ie, window height) you can create what looks exactly like a side frame.

    35. Re:Some standards are just too strict... by Sancho · · Score: 1

      Ah, ok, that makes sense. Thanks!

    36. Re:Some standards are just too strict... by Bogtha · · Score: 1

      The problem you describe is really only an issue if you are hooking into the load event of the window object, which only fires after each and every embedded resource - images, ads, etc) has finished loading. There are alternative ways of executing JavaScript before this time, and any decent JavaScript framework includes a way of doing so.

      --
      Bogtha Bogtha Bogtha
    37. Re:Some standards are just too strict... by pbhj · · Score: 1

      It's up to me as a user to choose where a url opens, especially since we are all using the tabbed paradigm now.

      User agents currently do not allow the user to submit a form into a new window or tab. This is the nearly nine-year-old bug 17754 on bugzilla.mozilla.org with 99 votes.

      I presume you mean submit the form and have the form page stay open and the submission complete page show in a separate tab/window. Not sure how useful that is (you can page back to view a forms submitted content in FF) but it sounds more like a feature request than a bug.

    38. Re:Some standards are just too strict... by Anonymous Coward · · Score: 0

      chromium/chrome doesn't

    39. Re:Some standards are just too strict... by Anonymous Coward · · Score: 0

      Opera does. I use it frequently at Wikipedia. Just type something in the search box, shift+enter, and the page (or search results) shows in a new tab.

    40. Re:Some standards are just too strict... by Anonymous Coward · · Score: 0

      Why in gods name would you even want to do that??
      A form is on a page, you click the button, it changes the page in almost all cases, be it loading a new page, or doing some AJAX call and updating the page layout in some way.

      Bug or not, still seems pointless to me, and the exact reason as to why it is nearly nine years old.

    41. Re:Some standards are just too strict... by tepples · · Score: 1

      Why in gods name would you even want to do that??
      A form is on a page, you click the button, it changes the page in almost all cases, be it loading a new page

      Because I want to use information on the new page to help fill out a separate form on the old page.

    42. Re:Some standards are just too strict... by inKubus · · Score: 1

      Yeah, Important point about XHTML is that it's XML. So it's extensible. Basically, you should have your controller output in your XML format (your middleware format or whatever), and reformat it with XSL to whatever presentation format X the user is using. XHTML is a standard for the structure of the data, but the way it actually renders is up to the browser. So even if you are 100% compliant, there might be some order of operations thing in a specific browser that kills you.

      In this case standards ARE the problem. XHTML is a data formatting standard and not actually a display/design standard (although it tries to be). Therefore yes, your page presentation is being accurately transmitted to the browser, and the browser is doing everything it's supposed to but it still doesn't work.

      From a design perspective, XHTML sucks, because you cannot get very creative with your design because you don't know what might be on the other end. It is, on the other hand, very easy to make a form that functions in every web browser...

      The ideal solution is to avoid the design entirely and have a single framework for UI design in the browser. Of course you'll find that Microsoft uses Active X, whereas everyone else uses Java applets.

      Thus Javascript has filled the hole, and the major Javascript frameworks are filling the smaller browser design holes with transparent workarounds. It just shows that even if Microsoft tries to go monolithic, the market demands openness and standards. So, since designers couldn't rely on HTML they went behind MSFT's back to JS which still conforms to standards on all platforms.

      Which reminds me, MS has adopted jQuery as it's official framework for JS. What do you know.

      --
      Cool! Amazing Toys.
    43. Re:Some standards are just too strict... by Kneo24 · · Score: 1

      Well not in the least bit idiotic actually. It's up to me as a user to choose where a url opens, especially since we are all using the tabbed paradigm now.

      I hate this mantra. If you want it to open in a new window, right click it. If you want it to open in a new tab, right click it. If you choose to left click it, guess what? You don't get any choice regardless.

      Besides, it is my website, not yours. I should have every right to dictate how you view it, and what you do with it.

    44. Re:Some standards are just too strict... by Shin-LaC · · Score: 1

      Safari does. Hold down the command key when you submit the form, and the results open in a new tab.

    45. Re:Some standards are just too strict... by ttys00 · · Score: 1

      To automatically open links in a new window - Annoying behaviour by web developers who think no one could possible want to, god forbid, leave their site in favor of another site.

      Please don't assume it's the actual developers who do this. I've worked as a contractor at half a dozen web shops, and in every place the developers want to follow the standards completely. They have been overruled by managers that want users to open every link in a new window or tab, so that they stay on their sites a little longer to increase one of their page view metrics by 0.25%.

    46. Re:Some standards are just too strict... by SanityInAnarchy · · Score: 1

      I use Noscript and I don't even bother to explore sites that are totally borked without their Javascript crutch.

      In other words, it doesn't even occur to you that Gmail might be useful.

      Javascript is a tool. Like any tool, it can become a crutch, but it actually does provide things which are not possible -- and should never be possible -- with straight HTML/CSS.

      --
      Don't thank God, thank a doctor!
    47. Re:Some standards are just too strict... by SanityInAnarchy · · Score: 1

      In the first place, if standards (HTML / CSS) had been designed right, we wouldn't need so many javascript workarounds.

      Javascript isn't always a workaround -- it's a client-side programming language. That means you can, I don't know, write programs in it.

      I don't think HTML or CSS need to be Turing-complete. I'd be a bit frightened if they were.

      Excuse not to implement it: The user should decide!

      I actually agree with this, but it's also a case where it's progressive enhancement. Leave the link target as something sane, and use a Javascript onClick handler.

      Excuse not to implement it: SSI works just as well.

      Bull.

      Workaround: AJAX.

      Which provides more than just this.

      Granted, that's most of what people use it for, but it's far from the only possibility. Simplest thing I can think of is displaying how long ago a given event happened -- Javascript can update this dynamically, without having to hit the server at all.

      Another example would be anything requiring live updates -- granted, it's a hack, but how would you implement a Comet-style push protocol in HTML/CSS? How would you implement a decent chat client without it?

      --
      Don't thank God, thank a doctor!
    48. Re:Some standards are just too strict... by SanityInAnarchy · · Score: 1

      In other words, as everyone else gets more and more savvy, they get punished for their savviness by having to get around stupid measures?

      For that reason, and many others, I say hell no.

      Now, if you can make it easier for everyone else, without ruining it for savvy users, be my guest.

      --
      Don't thank God, thank a doctor!
    49. Re:Some standards are just too strict... by SanityInAnarchy · · Score: 1

      Right. The appropriate place is onDocumentLoad, which is done by jQuery. I suppose there's still the possibility that a browser will show part of the document, while the rest is still loading...

      The hack I've been doing, which isn't particularly friendly to non-Javascript users, is to disable elements I want to jQuery-ify, either with standard HTML form disabled attributes, or with display:none for links.

      --
      Don't thank God, thank a doctor!
    50. Re:Some standards are just too strict... by mikael_j · · Score: 1

      Oh, I'm well aware of this, I had the same problem when I was getting paid to do web development, but I ended up overruling my boss by arguing that usability and standards-compliance were more important than artificially inflating the stats and that if the user wanted to stay on the site in question he/she would choose to open the link in a new window/tab.

      Of course, not everyone has a boss who is reasonable about this sort of thing.

      /Mikael

      --
      Greylisting is to SMTP as NAT is to IPv4
    51. Re:Some standards are just too strict... by hansamurai · · Score: 1

      Actually, Gmail works perfectly fine without Javascript enabled, they have a basic HTML mode just for that. Though I admit, I do use it with Javascript on. Basically the situation I was describing was if I'm using StumbleUpon or something.

    52. Re:Some standards are just too strict... by SanityInAnarchy · · Score: 1

      Actually, Gmail works perfectly fine without Javascript enabled, they have a basic HTML mode just for that.

      Gmail without Javascript is pretty much an entirely different app.

      Though I admit, I do use it with Javascript on.

      So you admit that it's not always a crutch.

      --
      Don't thank God, thank a doctor!
  8. Surprised? by secondhand_Buddah · · Score: 4, Insightful

    Why is this a surprise? We are limited by non-standards compliant browsers.
    Unfathomable amounts of development time has been wasted over the years trying to set sites running and usable in multiple browsers.
    To complicate the issue, over the last few years there has been an explosion in the number of browsers on the market. It is really no fun navigating this modern tower of Babel.
    If I had one wish that would be granted, it would be that all browsers would be compliant to a standard. Literally millions of man years in development time could have been saved if this issue was somehow nipped in the bud earlier on.

    --
    Participatory Governance : The only feasible option for a real democracy, where everyone really does have a say.
    1. Re:Surprised? by SanityInAnarchy · · Score: 1

      To complicate the issue, over the last few years there has been an explosion in the number of browsers on the market. It is really no fun navigating this modern tower of Babel.

      To simplify the issue, maybe every few months, I have to fix an issue where our site works on Firefox, but not Safari.

      Every few days, I have to fix an issue where our site works everywhere else except IE.

      If we didn't have to deal with IE, the problem would be a complete non-issue. Any page I build that I'm not being paid to make usable in IE, I don't.

      --
      Don't thank God, thank a doctor!
    2. Re:Surprised? by westlake · · Score: 1
      Any page I build that I'm not being paid to make usable in IE, I don't.
      .

      It's a lovely ideal. But you code for IE or you learn to live on a diet of Ramen Noodles and Jolt Cola.

    3. Re:Surprised? by SanityInAnarchy · · Score: 1

      It's a lovely ideal. But you code for IE or you learn to live on a diet of Ramen Noodles and Jolt Cola.

      No, I code for IE when I'm being paid to.

      But take intranet sites, or simple pseudo-desktop apps -- I can develop a web app about as well as I can a desktop GUI app, and then it's as cross-platform as the browser I target. Since people were expecting me to tell them to install some Visual Basic crap, it's not that big a deal to make them install Firefox.

      --
      Don't thank God, thank a doctor!
    4. Re:Surprised? by Anonymous Coward · · Score: 0

      Why is this a surprise?

      Who said it was a surprise? That word (or any form thereof) doesn't appear in the summary, nor the article.

  9. It is not funny. by siyavash · · Score: 1

    Some seem to find this funny, but I don't think this is funny at all. It is actually very sad. I used to be a huge IE fanboy until I learned some w3c standards. All my websites are now 100% w3c validated. People should wake up. Well, not people but "webmasters/developers". This is a serious issue.

    Although, one big problem might be the huge marketshare of IE6 in many corporates and homes. I wish we could somehow get rid of IE6 very quick. IE7 isn't perfect, but it's MUCH BETTER than IE6.

    1. Re:It is not funny. by Shados · · Score: 2, Interesting

      Even if your app is 100% standard compliant, it may not be cross browser. Not even if you pull IE out of the equation. Not even if you ONLY TARGET FIREFOX (there are differences between FF2 and FF3. FF2 doesn't even fully implement CSS 2 itself...)

      So by now, devs have reverted to another philosophy: make websites that are crossbrowser, and -mostly- standard compliants.

      If you look at some of the most heavily cross browser web sites out there, especially the ones that are extremely backward compatible (down to Netscape 4), they are in HTML 4 quirk mode, and not standard at all. But they work better than most.

      The standard also doesn't dictate defaults, which is quite the big hole. Being standard compliant doesn't help too much. Add that the standard evolves extremely slowly, and if you want to get the job done, you need to bypass it.

      Thats why the W3C stuff is a standard proposition. No one "has" to adopt it. There are good standards out there, but as a general rule, anything coming out of the W3C is a joke of a swiss cheeze. Looked at the XQuery specs lately? My significant other works on a project to implement a full XQuery engine. A -lot- is left to interpretation, is loosely defined, etc. Same with XHTML and CSS. Even fully implemented, its vague, poorly designed (hellllooo.... versioning anyone? API 101?), and all around pathetic.

      The faster we get rid of it, the better. Either by a proprietary spec (Flash may not be open source, but at least it freagin work, mostly cross platform if you don't care to use the latest version at all time...better than XHTML/CSS anyway...), either by a new standard body that doesn't suck at -everything- they do. XQuery, XHTML, CSS, SOAP, XSD, XML... can they do ANYTHING right?

    2. Re:It is not funny. by zappepcs · · Score: 1

      Serious issue? Do you mean like preventing Iran from having nucular weapons serious? Perhaps, saving the thousands that die of starvation every day kind of serious? Global climate change kind of serious? AIDS kind of serious? or are you simply talking about 'what costume will I wear this year?' kind of serious?

      If it works, nobody will rush out and pay to change it, no matter how much bitching goes on. If it was as serious as malaria, BG would have forced everyone to upgrade to IEfirefox by now. Apparently it's not THAT serious. I mean, when I go to the bank to cash a check, I don't worry they won't give me money unless I can prove I'm using Firefox at home.

      geeesh

    3. Re:It is not funny. by Fallingcow · · Score: 1

      Even if your app is 100% standard compliant, it may not be cross browser. Not even if you pull IE out of the equation. Not even if you ONLY TARGET FIREFOX (there are differences between FF2 and FF3. FF2 doesn't even fully implement CSS 2 itself...)

      So by now, devs have reverted to another philosophy: make websites that are crossbrowser, and -mostly- standard compliants.

      Bingo.

      It's one thing when you're developing something as a hobby, but it's another when your boss gives you a .psd from a graphic designer and says "the client wants to see something by tomorrow" and you have no idea which browser he or she will be using.

      Any, any time I have to lay out a non-trivial site that will have to work well in IE6 and in modern browsers, I don't even bother trying for standards compliance. Even on the simple ones, I usually design to standards using FF3 as a testbed, then have to break it to get the damned thing working on IE6 (and sometimes even IE7!) in a reasonable timeframe.

      Deadlines are great at making you prioritize. I need the site to look good NOW in several browsers, and I need to have extra time for any javascript and PHP work to design it in such a way that it's extensible and maintainable (or pay for it later). (X)HTML/CSS standards compliance is my very last concern, and one of the first things I cut, not because I want to, but because it's my best bad option.

    4. Re:It is not funny. by Firehed · · Score: 2, Interesting

      You can make a site that works fine in every browser that's XHTML 1.0 Strict. Chances are that you'll have to use some non-standard (and probably invalid) CSS in a conditional stylesheet, but that a) doesn't count in terms of X/HTML validation and b) is only linked from the inside of a comment read only by IE, so even if CSS validity was part of being valid X/HTML it wouldn't be checked by the validator.

      Granted, you may need to add in some extraneous tags in order to implement the proper CSS hacks, but that makes them extraneous not invalid. But that's just as true for implementing rounded corners, which is in CSS3 (and accessible in Safari and Firefox by using the -webkit-border-radius and -moz-border-radius properties respectively) but is an unnecessarily large pain in the ass to implement on any element that isn't of a fixed width and height.

      You're absolutely correct that IE6 is a huge PITA to code for (as is IE7, but less so), but if you start with valid code that displays identically in Opera/Webkit/Gecko engines, you usually end up with something that doesn't take _too_ much hacking unless you have a really weird layout. My biggest problems, aside from those random 3px gaps that seem to occur mostly with floated elements, is font color inheritance on links and the various pseudo-classes, :hover in particular.

      For plenty of the projects I've been working on recently, I can safely ignore IE6 entirely (making a conditional stylesheet wouldn't be TOO hard, but I can't be bothered right now) and IE7 doesn't usually have too many issues. It's certainly a nice change. Combined with fully cross-browser JS libraries like jQuery, my life as a web developer is a whole hell of a lot easier than it once was.

      --
      How are sites slashdotted when nobody reads TFAs?
    5. Re:It is not funny. by SanityInAnarchy · · Score: 1

      Even if your app is 100% standard compliant, it may not be cross browser. Not even if you pull IE out of the equation.

      However, the working subset that you can use is much larger, and the browser-specific hacks are almost nonexistent.

      Add that the standard evolves extremely slowly, and if you want to get the job done, you need to bypass it.

      Erm, it's not the standard that moves slowly. It's adoption.

      Consider, again, how much better life is when you take IE out of the equation.

      Same with XHTML and CSS. Even fully implemented, its vague, poorly designed (hellllooo.... versioning anyone? API 101?)

      Erm, XHTML 1.0? And 1.1?

      You sound like you know what you're talking about, and then you forget about the fscking doctype.

      The faster we get rid of it, the better. Either by a proprietary spec (Flash may not be open source, but at least it freagin work

      Except when it doesn't.

      And since it is proprietary, there's little to no chance of third-party developers adding support for basic stuff, like, I don't know, 64-bit browsers, or video playback that doesn't suck.

      mostly cross platform if you don't care to use the latest version at all time...better than XHTML/CSS anyway...

      I think you'll find that if you stick to exactly one browser, and don't care about the latest version all the time, XHTML/CSS is at least as compatible as Flash.

      by a new standard body that doesn't suck at -everything- they do. XQuery, XHTML, CSS, SOAP, XSD, XML... can they do ANYTHING right?

      Any SPECIFIC complaints?

      For what it's worth, I don't use XQuery. I let jQuery worry about the browser quirks involved -- and I write my queries as CSS selectors, anyway, rarely XQuery-like.

      All things considered, it's actually not all that difficult to build a site that's standards-compliant, and works everywhere except IE. It's certainly easier to do so than to get Flash to perform well, or do anything Adobe didn't think of. (Can you imagine Greasemonkey for Flash? Neither can I.)

      --
      Don't thank God, thank a doctor!
    6. Re:It is not funny. by SanityInAnarchy · · Score: 3, Insightful

      Serious issue?

      Well, yes. Unless you think the Internet isn't important, or that it wouldn't make a difference if the web was controlled by a single person. I think that certainly puts it above "what costume will I wear" kind of serious.

      And your sig betrays you -- you seem to take yourself just as seriously as the rest of us take things that actually matter.

      I mean, when I go to the bank to cash a check, I don't worry they won't give me money unless I can prove I'm using Firefox at home.

      Well, when you go to cash a check, you shouldn't really have to prove anything, other than that you can sign for it.

      But I've seen banks that only work on IE. I haven't seen banks that only work on Firefox.

      --
      Don't thank God, thank a doctor!
    7. Re:It is not funny. by Shados · · Score: 2, Interesting

      However, the working subset that you can use is much larger, and the browser-specific hacks are almost nonexistent.

      Only because we're brainwashed in seeing the web as incredibly limited. The "standard" allows for a lot of things that even FF2 doesn't support (only FF3). Display:inline-block anyone? Oh, there are ways around it, either through hacks, or through workarounds... but when I was is a (&@&)(&#)(#@ block that is...I don't know...inline... it would make sense if I could use inline-block. But nope, not if I want to support FF2. Sure the subset you can use without IE is much larger, but you still need to test cross-browser, heavily, no matter what, which was my point. That your page validates is almost irrelevent.

      Erm, it's not the standard that moves slowly. It's adoption

      The standard moves slowly as hell. The W3C is a huge entity made of various special interest groups. That cannot go fast no matter what, AND its disconnected from reality (thus slowing down adoption). Even an -open source browser with Google as a sugar daddy pumping MILLIONS into it takes half a decade to get anywhere-. Same with everything the W3C piss out. It takes years to resolve real problems, because they're too busy with edge cases (XML namespaces mess!) to pump out specs that are useful.

      During that time something like Silverlight gets implemented by Miguel's team in a fraction of the time, and thats a freagin Microsoft product thats supposed to be crappily documented. If you ask the people who designed the specs, they'll tell you it was MADE to be easy to implement (thus its limitations, such as absolute positioning against the closest relative parent, or lack of vertical control aside with the table-* category of displays), but if you ask anyone who actually implements it, they have a different story.

      Ivory Tower, meet real world.

      Consider, again, how much better life is when you take IE out of the equation.

      Ironically, the only reason the standard picked up in the first place was that IE had the best support for it for the longest time :) A lot of the stuff in the specs made it in IE first, too, albeit differently (opacity, ajax, etc)

      Erm, XHTML 1.0? And 1.1?

      You sound like you know what you're talking about, and then you forget about the fscking doctype.

      The part in parenthesis was only about CSS. The part before applied to both XHTML and CSS. CSS versioning is so bad, that when its features get implemented (like by IE8), the community cries foul and say that in -THIS- case, IE8 should break the standard because its stupid. XHTML versionning -is- stupid too though. Its possible to get an XHTML 1.1 page that fully validates, yet its not even XHTML 1.1 (which is very different from 1.0)

      For what it's worth, I don't use XQuery. I let jQuery worry about the browser quirks involved -- and I write my queries as CSS selectors, anyway, rarely XQuery-like.

      XQuery has NOTHING to do with browsers. Its an XML API like DOM and XSLT :) Think SQL for XML. The specs are awful, and because of that, even though its much smaller to implement than XHTML/CSS, no one actually has a full implementation. Everyone is guessing. You'll see implementations on the market that claim being full, but if you talk with their developer, yes, its a perfect implementation of what was clear, with perfect guesses on the rest. I don't have a clue why you're comparing XQuery with JQuery though.

      Finally, its easy to make a site thats standard compliant if the person making the design is the same as the person coding it. Then you can stick to the subset of what XHTML/CSS is good for. The CSS Zen Garden is an example of that. They start from the structure, and then do the best layout they can from that. If they start from a photoshop made by a designer, then try to apply it, its going to be another story.

      There's a reason there's now a group for HTML 5.0... because even the experts thought the W3C's current specs are disconnected from reality.

    8. Re:It is not funny. by pbhj · · Score: 1

      I think he means serious in that IE has (by my reckoning on the effect it's had on sites I've dev-ed on) added about 35% to website costs for anyone that has paid to have a website designed in the last 8 years. Wasting countless hours of time and costing businesses vast amounts of money.

      Sure it's not as serious as the AIDS epidemic. But most people accept there are degrees of seriousness.

      The flip-side is it's probably improved revenue for web designers in a bizarre sort of way.

    9. Re:It is not funny. by SanityInAnarchy · · Score: 1

      The standard moves slowly as hell.

      Which is an entirely moot point when the browsers move even slower, and IE is pretty much stalled.

      It takes years to resolve real problems, because they're too busy with edge cases (XML namespaces mess!) to pump out specs that are useful.

      Which is actually useful, when you're that particular edge case.

      XQuery has NOTHING to do with browsers. Its an XML API like DOM and XSLT

      Which some browsers support natively -- or am I thinking of xpath?

      no one actually has a full implementation. Everyone is guessing.

      That is one case I think the w3c went wrong -- no reference implementation. (Oh, there's Amaya, but let's be serious.) And the Acid tests are a great idea, but always lagging behind.

      However, having exactly one implementation is not good, and should not be the basis for a standard -- unless that is an open source (probably public domain) and ridiculously well-tested, in the real world. The BSD network stack is a good example of that.

      The CSS Zen Garden is an example of that. They start from the structure, and then do the best layout they can from that. If they start from a photoshop made by a designer, then try to apply it, its going to be another story.

      That should tell you something about the usefulness of Photoshop as a web design tool.

      --
      Don't thank God, thank a doctor!
    10. Re:It is not funny. by Anonymous Coward · · Score: 0

      > During that time something like Silverlight gets implemented by Miguel's team in a fraction of the time

      You are delusional, even Mono 2.0 still can not handle table layouts generated by VisualStudio, it displays nothing at all (setting ColumnCount manually once more (to the same value as in the resource) fixes it).
      Making a web page that looks the same in IE6 and FF2 is easier than making a Gui app that is only _working_ in both Mono and .Net.

  10. Oh great by Spazztastic · · Score: 1

    This is pretty annoying. We already have to deal with grammar nazis, now we're dealing with standards nazis? When will it end!?

    --
    Posts not to be taken literally. Almost everything is sarcasm.
    1. Re:Oh great by Yvan256 · · Score: 2, Funny

      Have you tried getting some soup lately? That's even worst.

    2. Re:Oh great by Red+Flayer · · Score: 1

      We already have to deal with grammar nazis, now we're dealing with standards nazis? When will it end!?

      What do you think a grammar nazi is. They are trying to enforce language usage standards.

      I'm actually now very curious as to whether your typical website-standard-nazi uses correct grammar. And whether the average grammar nazi is also a web standards Nazi.

      I guess the only reason for a theoretical difference between the two is that the human brain is more capable of interpreting non-standard usage than a web-browser is.

      Oh well. Another of life's trivial unanswered questions that will keep me up at night.

      --
      "Trolls they were, but filled with the evil will of their master: a fell race..." -- J.R.R. Tolkien on Olog-hai
  11. Sad. Even sadder is the yet-another-feature creep. by bboxman · · Score: 3, Insightful

    This is sad. The situation is even worse in some non-English web domains.

    Why can't the web stick to something simple? 95% of the sites I use, would be fine with just plain simple HTML 2.0. Instead, we've got javascript, CSS, XHTML, and other buzzwords. Which in the end, take control of how a web page looks from the user's hand.

    I like to read text, on a monitor, green on black (or white on black). I would like to format a web page the way I want to see it.

    The vast majority of the web is simple formatted text. There is no reason for this to constantly evolve onwards and onwards.

  12. And Opera sayeth unto the Web: by rarel · · Score: 1

    "Come to MAMA!"

    1. Re:And Opera sayeth unto the Web: by fractalVisionz · · Score: 1

      When MAMA first was getting started with the internet, she talked with my grandmother--and her mom--GRAM, General Research and Analysis Miner for some help. Together they provided an online analysis tool, called MAMAGRAM, used to across the globe for enlightenment of geeks in mining single sided relationship data.

  13. and that's not a problem by circletimessquare · · Score: 3, Insightful

    1. the web is still evolving, the standards keep changing. no pressing need to lock things in
    2. it is superior design to have a browser that gracefully degrades rather than being and brittle and refusing to render everytime someone forgets to close a <p> element. not simply because of nonstandard pages, but for a whole host of other reasons, including handling partial transmissions
    3. the strength of the web is open participation, low barrier to entry. hobbyists should publish, and this is a good sign. hobbyists should not expected to be anal retentive standards zealots

    complete standards compliance should always be low on the web because this is a sign of a HEALTHY internet, because it means nonprofessionals are contributing content. this is always a good thing, this what made the internet a powerful nw form of media in the first place. if ever there were some sort of gatekeeper organization or rigorous technical specification that enforced standards compliance, you would raise the barrier to entry onto the web by regular joes. you would reduce the variety of the web, make it more monoclonal, and hurt a vibrant ocmmunity

    low standards compliance is not only a complete nonissue and not a problem, its a good sign. the lower standards compliance is, the better for us all

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:and that's not a problem by Anonymous Coward · · Score: 0

      3. the strength of the web is open participation, low barrier to entry. hobbyists should publish, and this is a good sign. hobbyists should not expected to be anal retentive standards zealots

      I agree. It should be the same as making a JPEG. If people want to crop and touch up a photo, they are not expected to read the JPEG standard, open the JPEG in a hex editor, and hand-code it. They use tools, like GIMP or Photoshop, which implement the standard.

      Why does this work? Because a malformed JPEG will not display. Because people can't bend the rules, they don't try and they don't complain that the JPEG standard is "too strict".

      It should be the same way with HTML. Unfortunately, we don't have the proper tools for this. There should be editors which work like text editors, except that they only allow the creation of valid code. There would be commands for adding elements and attributes. The software would generate a valid serialization of the DOM.

      As well, people should be able rely on CMSs to produce valid code, just like they rely on Photoshop to produce valid JPEGs or PNGs.

    2. Re:and that's not a problem by Anonymous Coward · · Score: 1, Insightful

      "low standards compliance is not only a complete nonissue and not a problem, its a good sign. the lower standards compliance is, the better for us all"

      That's asinine. As a developer, I shouldn't have to code something five different ways for five different browsers because they all decided to implement a rule different from one another. I prefer spending my time being productive, not having to try to account for other programmers' screw-ups. To the browser-makers: GET ON THE SAME F'N PAGE ALREADY!!!!

    3. Re:and that's not a problem by Anonymous Coward · · Score: 0

      So for the high school class that I teach where I drill making valid xhtml files into my students is a sign I'm breaking the internet? I teach them to always make their pages standard, and then 'pretty'. They can lose quite a lot of points if they add in special tags for IE that do something with loud annoying music... Anywho, that's my $0.02

    4. Re:and that's not a problem by Anonymous Coward · · Score: 0

      complete standards compliance should always be low on the web because this is a sign of a HEALTHY internet, because it means nonprofessionals are contributing content.

      Uh, no. Hobbyists simply need a gui web designer that conforms to standards. In case you didn't notice, nearly all hobbyists use gui web design tools, so you can't exactly blame THEM for forgetting to close the paragraph tag. You can, however, blame the web design tools, and certainly the browser makers for encouraging it.

      the lower standards compliance is, the better for us all

      Are you on crack? If suddenly all hobbyists were given web design tools that conform to standards, and the rate of standards compliance went up, would you actually complain that it's "worse for us all"? Perhaps you need a hobby yourself.

      As for an organization "forcing" standards compliance, I think the state of the web today proves that it's obviously impossible.

    5. Re:and that's not a problem by BenoitRen · · Score: 1

      The HTML and CSS standards haven't changed in about decade, and the next versions only add to the standard instead of changing it.

      While I agree that a low barrier to entry is a good thing, low standards compliance is not. You're advocating chaos. Web standards ensure that everyone works together and that your content renders how you wanted it.

      It's not like the web standards are hard to learn. Text? Use the p element. Image? Use the img element. Navigation? Use a list. There, most people are satisfied with their web page by now. Only need to use some CSS to give it some style, which is one of the simplest languages to learn.

      By the way, your p element example was a bad one, as you don't need to close it at all.

    6. Re:and that's not a problem by jonaskoelker · · Score: 1

      2. it is superior design to have a browser that gracefully degrades rather than being and brittle and refusing to render everytime someone forgets to close a

      element. not simply because of nonstandard pages, but for a whole host of other reasons, including handling partial transmissions

      If all browsers implemented the standard correctly and was anal retentive about compliance (just like your average compiler/interpreter is), people would learn to write compliant pages (just like hobbyists learn to write syntactically correct C programs). The problem of nonstandard pages would not have occured, and it will disappear over time when people realise their web page is not getting out there.

      Partial transmissions of valid pages is still an issue; parse what you have and render it, then add to the parse tree and re-render until the page is all the way there.

      hobbyists should not expected to be anal retentive standards zealots

      Hobbyists can write valid C/python/java programmers even though the compiler is anal-retentive about it. The only thing won by browsers not being strict is that we don't have to do the work required to climb out of the hole we've dug ourselves into.

      if ever there were some sort of gatekeeper organization or rigorous technical specification that enforced standards compliance,

      Like the C specification enforced by your compiler?

      you would raise the barrier to entry onto the web by regular joes. you would reduce the variety of the web, make it more monoclonal, and hurt a vibrant ocmmunity

      You'd get rid of some of the crap. Some of the crap would remain crap but for fewer reasons. Some of the crap would cease to be crap.

      low standards compliance is not only a complete nonissue and not a problem, its a good sign. the lower standards compliance is, the better for us all

      You can only access your bank over the web if you not only switch browser but also switch operating system because the browser your banks compels you to use doesn't run on the operating system you like.

      If you actually do that, it also means your favorite IDE is going to look, feel and act like crap, you'd have to change versioning system, and you'd have to spend time making LaTeX use Computer Modern so your output is going to remain looking pretty, you'd have shitty window management, and... [your favorite reason to stick with your current OS].

      Low standards compliance is probably not a big problem for my previous bank; I wasn't that big of a customer. In a sense, I shouldn't have to switch banks to get a functioning web banking service. No, I don't feel entitled. But I do think every developer should at some point in their training develop an application target to a 64-bit big-endian multi-CPU box running Amiga-OS and lynx, just to be forcefully yanked out of the "all the world's a PC/Mac/IE/*nix."

    7. Re:and that's not a problem by pbhj · · Score: 1

      complete standards compliance should always be low on the web because this is a sign of a HEALTHY internet, because it means nonprofessionals are contributing content.

      Presumably you think that the number of car crashes should be high because that's a sign that non-professional drivers are using the roads. Or the level of food poisoning should be high to show that people are cooking at home.

      Just because you're not a professional doesn't mean you can't do it properly.

      For those that don't want to learn to code/markup properly there are plenty of ways to contribute to the internet that don't require you to directly code your website. How many CMSs are there? Bloggin' apps, wikis? How many fora? There are plenty of point and click interfaces, designed by professionals, that you can use (often free with web space). These sorts of apps should produce standards compliant output.

  14. Re:Sad. Even sadder is the yet-another-feature cre by Spazztastic · · Score: 1

    You're telling me the DHTML clock that follows your cursor isn't entertaining?

    --
    Posts not to be taken literally. Almost everything is sarcasm.
  15. Re:Sad. Even sadder is the yet-another-feature cre by Daimanta · · Score: 1

    But what about the porn?

    I think the step from ASCII-girls was a big improvement.

    Yay for vid pron!!1!

    --
    Knowledge is power. Knowledge shared is power lost.
  16. So what?? by rodrigoandrade · · Score: 1

    Only about 4% of web sites are HTML-standard compliant. So what?? Will the world come to an end??

    This standards-nazi attitude is what, IMHO, will always keep Opera from becoming a major browser. When Joe Sixpack finally learns about Opera, decides to give it a go, and realizes a few sites don't look as good in Opera as they do in IE, he'll simply go back.

    The W3C is kind of like the UN, it dictates the rules, but has no firepower to enforce them (that's where Microsoft comes in).

    As much as I love Opera I find myself going back to IE (rather, FF with IE Tab ext.) about 20% of the time. Not to mention my work intranet which is totally designed for IE.

    1. Re:So what?? by bertilow · · Score: 1

      nly about 4% of web sites are HTML-standard compliant. So what?? Will the world come to an end??

      No. Actually those figures indicate that the world has improved a lot. It used to be something like 0.001% valid pages. So 4% is a huge step forward.

    2. Re:So what?? by Bogtha · · Score: 1

      Indeed. If you read the full report, you'll see that a similar study in 2001 yielded 0.71% valid pages, and a similar study in 2006 yielded 2.58% pages, so 4.13%, while still very low, is a decent improvement in the right direction and it seems to be accelerating.

      --
      Bogtha Bogtha Bogtha
    3. Re:So what?? by Hatta · · Score: 1

      This standards-nazi attitude is what, IMHO, will always keep Opera from becoming a major browser. When Joe Sixpack finally learns about Opera, decides to give it a go, and realizes a few sites don't look as good in Opera as they do in IE, he'll simply go back.

      Exactly wrong. The more sites that are standards compliant, the more sites will look good in Opera. The sites that don't look good in Opera, are only broken because of some non-standards compliant feature of IE.

      --
      Give me Classic Slashdot or give me death!
    4. Re:So what?? by Anonymous Coward · · Score: 0

      Wow, what a flamebait. You sir suck bigtime. I won't even try to spend my time dealing with stupid people like you.

    5. Re:So what?? by BenoitRen · · Score: 1

      Substitue Opera with Firefox, and you get the same picture. All the web browser developers are rallying behind the web standards. Yes, even IE, but they have a lot of catching up to do.

  17. Re:Sad. Even sadder is the yet-another-feature cre by bboxman · · Score: 1

    No Really.

    Come to think of it, the main use of all of these "junk standards" is to drive commercials on various sites.

  18. Everybody's High On Acid by Bananatree3 · · Score: 1

    All the major browsers are vying for top dog in creating a smiley face where there was once colorful blurs...And now is colorful flashy rainbows!

  19. I know the problem... by Anonymous Coward · · Score: 0

    The problem is html is so non restrictive that you can be high and create a "good" website. It also doesn't help that a lot of web developers are "high" school kids/drop outs and community college grads :P What I'm saying is that as long as companies hire cheap labor (those mentioned) companies will get cheap results.. simple as that.

    SUMMARY:
    You get what you paid for. Nothing more.

  20. strict vs transitional DTDs by tepples · · Score: 1, Informative

    Are there degrees of strictness?

    Yes. HTML 4.01 and XHTML 1.0 each have two DTDs: a "transitional" DTD that allows presentational elements and a "strict" one that disallows them. The trouble is that a couple structural elements and attributes got removed by mistake in the strict DTDs along with the presentational ones, most notably the value attribute of the li element. For this and other reasons, most valid HTML that I've found has used a transitional DTD.

    1. Re:strict vs transitional DTDs by Bogtha · · Score: 4, Informative

      Yes. HTML 4.01 and XHTML 1.0 each have two DTDs: a "transitional" DTD that allows presentational elements and a "strict" one that disallows them.

      No, that's something different. There aren't degrees of strictness when it comes to validity. If a document claims to be a Strict document, and makes a single mistake, then it is invalid. If a document claims to be a Transitional document, and makes a single mistake, then it is invalid. In both cases, it's an absolute rule with no laxity.

      --
      Bogtha Bogtha Bogtha
  21. not people but "webmasters/developers". by John+Hasler · · Score: 1

    So Webmasters are not human? I've often suspected that.

    --
    Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
  22. Re:Sad. Even sadder is the yet-another-feature cre by coopaq · · Score: 4, Interesting

    ./ is mostly text, but how did you post this comment? Any Page refreshes?

    Actually it uses some pretty sweet AJAX calls.

    Progress usually comes from ignoring standards.

  23. so what does this tell us about the standard? by thermian · · Score: 4, Insightful

    Does it mean that 94% of websites did not find the standard useful?

    Or perhaps that the standard is poorly presented, causing fewer people to be aware of it?

    My personal leaning is that the standards body lost control of their 'standards' a long time ago, but they haven't realised yet. The only real thing most web devs care about is 'does my site/application run as required in the browsers I need it to?' If the answer is 'yes, if you don't follow the standard', then the standard is ignored.

    --
    A learning experience is one of those things that say, 'You know that thing you just did? Don't do that.' - D. Adams
    1. Re:so what does this tell us about the standard? by cowscows · · Score: 1

      The web is a moving target in almost whatever direction you want to look at it from. Standards are constantly in development. There are multiple significant browsers all being developed at different rates and with different priorities. The technologies that are available are continually evolving. And the needs of clients are forever becoming more complex. The job of a web designer/developer is to pick the best compromises from all of those competing interests and to make a product.

      The point is, 100% standards compliance is not a realistic goal for most websites. And that's ok. It's just another one of those pieces that is nice and helpful to a degree, but there is a point of diminishing returns, and a few compromises here and there is not some sort of crime against humanity.

      I like to draw comparisons to the building design/construction industry because that's the career that I'm currently involved in. When designing a building, we have about a bazillion life safety/fire protection/accessibility/etc. codes that are legally enforced. We have to balance the demands of those codes with the needs of the client, our own "architectural vision", issues with energy useage, issues with budget, issues with gravity, and others.

      But the thing is, even though those codes are very important and have serious liability issues involved in them, they're still administered with some flexibility and compromise in them. Since the stakes are so high, there's all sorts of review processes that you have to go through, but it's possible to ask for and receive waviers for various issues, although they almost always require you to make a compromise of your own somewhere else.

      It's just the nature of the beast when you're designing complex systems. And whether that complex system is an office building, or the online store of the company that works in the office building, you can't realistically expect to get 100% of what you ideally want. And that's ok.

      --

      One time I threw a brick at a duck.

    2. Re:so what does this tell us about the standard? by pbhj · · Score: 1

      The only real thing most web devs care about is 'does my site/application run as required in the browsers I need it to?' If the answer is 'yes, if you don't follow the standard', then the standard is ignored.

      Personally I code for standards compliance. That means that most of the time I only need to check in FF, Op, Konq, Saf, Opera Mobile emulator. But then I need to work my way down IE8, IE7, IE6 making whatever fixes to ensure that IE doesn't barf all over the website. If I designed it to IE then it would most likely fail in other browsers - eg on handhelds.

      The point of standards is that of the thousands of browsers available in many versions on thousands of systems you can only test a few but if the browser devs and the website devs code to the same markup standards giving a useful presentation then the web works.

    3. Re:so what does this tell us about the standard? by Don+Sample · · Score: 1

      Does it mean that 94% of websites did not find the standard useful?

      Or perhaps that the standard is poorly presented, causing fewer people to be aware of it?

      No. It means that most HTML coders are too lazy to do it right. Sure there are errors that don't really make much difference, like not giving all your IMG tags an ALT string. 'ALT=" "' is perfectly legal, but doesn't do anything useful.

      But if you look at the actual errors reported, you're going to see a lot of things like unbalanced, or improperly nested tags. Something with an unmatched </TABLE> is going to display just fine, in pretty much any browser, until you go back in and edit the table to add some more rows, but you put them after that unmatched tag, and now they don't display right, and you waste ten minutes trying to track down what you did wrong.

    4. Re:so what does this tell us about the standard? by BenoitRen · · Score: 1

      HTML4 and CSS2 are standards that were done about a decade ago. This whole "the web is still evolving" doesn't apply.

      A comparison to building design is not appropriate, as we're dealing with computers here. It is perfectly possible to be 100% standards compliant, or at least very close to it, without too much effort.

    5. Re:so what does this tell us about the standard? by cowscows · · Score: 1

      You're right. The web hasn't changed at all in the last decade. Thanks for clearing this up.

      --

      One time I threw a brick at a duck.

    6. Re:so what does this tell us about the standard? by BenoitRen · · Score: 1

      I didn't say that the web as a whole hasn't evolved. I said that the HTML and CSS specifications haven't, so the argument that we shouldn't use them because the web is still evolving is irrelevant.

    7. Re:so what does this tell us about the standard? by Anonymous Coward · · Score: 0

      The only real thing most web devs care about is 'does my site/application run as required in the browsers I need it to?'

      I agree, but that's the sign of a bad web developer. Most web developers are bad developers. What they should care about is, "does my site/application run as required in any browser that the user has chosen? Obviously, that's impossible to check, but if the website is compliant and fails, it's the fault of the browser. If the website is not compliant and fails, it's the fault of the developer.

      The procedure a good developer will follow is to create a standard compliant website. Test that website in the major browsers such as IE and firefox. Create workarounds as needed for these browsers flaws while keeping the website compliant. This way, it will look good in the browsers most people use, and has the best chance of working in the browsers you can't anticipate the users will pick.

      Does it mean that 94% of websites did not find the standard useful?

      A standard isn't made to be "useful" in the sense of accomplishing a task. It's made to be useful in assuring cross-compatibility, and it can only do that if people (both web developers and browsers) follow it.

      Or perhaps that the standard is poorly presented, causing fewer people to be aware of it?

      It's the responsibility of every developer to find out whether standards exist to accomplish what he wants to do. If I type 'html standard' on google, I get the correct pages, which means that if someone "isn't aware of it" it's their own damn fault.

    8. Re:so what does this tell us about the standard? by Draek · · Score: 1

      Does it mean that 94% of websites did not find the standard useful?

      Or perhaps that the standard is poorly presented, causing fewer people to be aware of it?

      Or perhaps that a large percentage of people behind that 94% of websites are inept. Or do you think that Joe Average checks for standards-compliance before uploading his Donut-loving webpage to Geocities?

      Plus there's the fact that almost all free hosts put ads on your webpage, never in ways that comply with any standard.

      The only real thing most web devs care about is 'does my site/application run as required in the browsers I need it to?'

      The thing is, with so many different browsers using so many different engines, and the popularity of phone/PDA web browsers, the only way devs can have *any* expectation for their pages to work as required in all of them is by following the standards. And thankfully, more and more devs seem to be realizing that, because the number of idiot-coded websites I've seen has decreased dramatically in the last 3 years.

      So yeah, it's only 4.1%, but I imagine that if they had ignored relatively minor errors (like forgetting to close a bold tag, or not putting the / in br tags), and compensated in some way for advertiser's shit code, the percentage would be *much* higher than that.

      --
      No problem is insoluble in all conceivable circumstances.
  24. Slashdot by FlyingBishop · · Score: 2, Interesting

    http://validator.w3.org/check?uri=http%3A%2F%2Ftech.slashdot.org%2Farticle.pl%3Fsid%3D08%2F10%2F16%2F1325215&charset=(detect+automatically)&doctype=Inline&group=0

    If Slashdot shows up with 28 errors, would you really expect anything at all out of the non-technical media?

    1. Re:Slashdot by dword · · Score: 1

      Have you tried validating Google's pages? It's like "Oh, My Gawd, It's Full Of Errors!"
      They have plenty of resources to make their pages standards compliant but they don't and I think their company is doing pretty well. There must be a reason for this and I think it's the fact that their pages work in all the popular browsers; maybe the cost of validating them is just too high or it simply doesn't justify any cost! Really, I don't understand, why on Earth would I try to make my pages 100% standards compliant when nobody really cares about that. I don't think Average Joe gives a shit if www.myemailproviderhostnamehere.com validates correctly as long as it works in his web browser. This "our products are w3c valid" is only for marketing and has absolutely no other practical purpose.

  25. 4.13% compliance doesn't really surprise me. by NoNeeeed · · Score: 5, Insightful

    You only need to make one mistake in your markup to be non-compliant. I would be interested to see what the degree of failure is for the other 95.87% of sites. My website, Wii Fit Forum currently fails on six counts, all just simple errors in the code which I plan to fix. But currently, the site displays just fine, so I have more important things to worry about. I think this is the same for many publishers.

    Unfortunately for the novice, the ignorant, the lazy or the just plain error-prone (the last two are me), the W3C and the browser industry do not make it that easy to be compliant.

    HTML standards are the current prime example of the old joke "the great thing about standards is that there are so many of them". The W3C really needs to stop pissing around with all this semantic web crap, and concentrate on making what is already there work better.

    We need a single standard which embodies all the best elements of the existing ones in a coherent form, and then the browers manufacturers need to get their arses in gear and implement it properly. The novice developer is currently confronted with a mish-mash of alternative doc-types, each of which has different pros and cons, and which may or may not work properly depending on your browser. It needs to be done soon, not over a ten year timescale.

    When you can stop worrying about whether your site will work in various browsers, then people will spend more time on compliance. Until then, people will worry about the important things, such as their readers being able to see their site properly.

    I know I should treat standards with more importance, but while the current mess persists it is hard to care.

    1. Re:4.13% compliance doesn't really surprise me. by NoNeeeed · · Score: 3, Insightful

      As I said, I will, but it is low down my priority list because there are other things that will actually make a difference to my site's users that I need to do first. HTML standards compliance is, for most people, irrelevant. It's like using perfect grammar, it's a good thing to have, but failing doesn't make you unintelligible. Only when your grammar is really bad, or your standards compliance is utterly terrible, do you become unintelligible (to man and browser), at which point it becomes a problem.

    2. Re:4.13% compliance doesn't really surprise me. by BenoitRen · · Score: 1

      What the hell are you whining about? There are only two standards for mark-up: HTML and XHTML. The DOCTYPEs are clear on which you should use for what. The best option is Strict.

      Semantics aren't crap. They're meaningful and powerful. They make styling and maintenance much easier, and describes your document to a machine better than a dozen font tags ever could.

      You talk as if all web browsers break the standard, while there's only one that does which gives web developers over the world grief. And we all know which one that is.

    3. Re:4.13% compliance doesn't really surprise me. by pbhj · · Score: 1

      You're clearly not selling the design for your forum: if I asked my designer why the website had errors and they said "they're minor and easy to fix" I'd be kinda curious as to what the hell he thought he was being paid for. It's not a finished design. That's fine for yourself.

      You say it doesn't affect the users, you test all browsers on all platforms? No. What you mean is it doesn't AFAICT affect users or it only affects a few and I can live with losing their custom.

  26. What good are "standards" by PortHaven · · Score: 3, Insightful

    When they don't work with the tools (various browsers).

    Better to build a website that works, than one that meets standards but display poorly in the browsers of your users.

    Ask yourself this simple question. If it does not look good in the browser, is your client going to accept "Well it's coded to standards!". Heck no...

    1. Re:What good are "standards" by shish · · Score: 1

      When they don't work with the tools (various browsers).

      Who said they don't?

      If the choice was code for one browser, or code for none, then one would be better; but you seem to be missing the option of "code to standards and look right everywhere"

      --
      I mod down anyone who says "I will be modded down for this", regardless of the rest of their comment
    2. Re:What good are "standards" by ParanoiaBOTS · · Score: 1

      If the choice was code for one browser, or code for none, then one would be better; but you seem to be missing the option of "code to standards and look right everywhere"

      Are you actually a web developer? Have you tried creating and maintaining anything beyond a three page site that actually meets standards AND displays well in all browsers? It is a pain just to get a site to look / work the same in different browsers.

    3. Re:What good are "standards" by nottoogeeky · · Score: 1

      You can make a website look good and still stick to standards. You just need to know how to do it correctly. I'm building a website right now for a client http://bikingdirect.cogocreative.co.uk./ I have 1 css error that i'll fix and it passes the accessibility test. In an older browser it will simply show the text. It works in all modern browsers apart from ie6 (which i will fix with an ie only stylesheet).

    4. Re:What good are "standards" by BenoitRen · · Score: 1

      Yes, I'm a web developer, and yes, I maintain such sites. They're standards compliant and render well in all web browsers.

      Seriously, it's not an arcane art. It's perfectly possible. I wonder why people always claim the opposite when I know it's possible because I actually do this.

    5. Re:What good are "standards" by shish · · Score: 1

      Yes, and yes. Admittedly I design for standards and look fine everywhere except IE, then spend an extra 10% of my time on IE specific hacks, but its not *that* hard~

      --
      I mod down anyone who says "I will be modded down for this", regardless of the rest of their comment
    6. Re:What good are "standards" by PortHaven · · Score: 1

      Probably because this seldom is the case...

      Hence, we actually add many conditions and evaluations to determine browser, version, etc.

      ***

      That said, if it looks right and is standard - that's the best of both worlds.

    7. Re:What good are "standards" by PortHaven · · Score: 1

      Render well...

      That works for some sights, where as certain clients want "render" exactly.

      I do wonder whether you utilize any pre-written libraries that take into account variations in web browsers, DOM, etc.

      If so, then you're not coding to standards, you're coding to handle differences and process your code to display to a standard.

    8. Re:What good are "standards" by BenoitRen · · Score: 1

      Pixel perfect is not possible. There are many variables at play. But you can get a very consistent rendering.

      No, I don't use any pre-written libraries.

  27. End 6 by tepples · · Score: 1

    I wish we could somehow get rid of IE6 very quick.

    Install End 6 on sites that you maintain, and the first time an IE 6 user visits your site, a pop-up will suggest Opera, Safari, Firefox, Flock, or IE 7.

  28. Re:Sad. Even sadder is the yet-another-feature cre by I.M.O.G. · · Score: 3, Interesting

    The best thing for you to do is to provide your own CSS file and tell firefox to use it rather than anything provided by the website you are visiting.

    This will style all sites similarly, and will work great for sites that atleast have well-structured HTML. Sites that at least have properly structured HTML are much more common than sites which are standards compliant.

  29. Errors found while checking this document as HTML by Anonymous Coward · · Score: 0

    Errors found while checking this document as HTML 4.01 Strict! Result: 23 Errors, 1 warning(s) Address: http://tech.slashdot.org/article.pl?sid=08/10/16/1325215 Encoding: iso-8859-1 Doctype: HTML 4.01 Strict Root Element: HTML

  30. It's not standard by Anonymous Coward · · Score: 0

    ...if the majority of authors don't abide by it. Silly propeller-heads.

  31. _Already_ 4.13% of the web is standards-compliant by Anonymous Coward · · Score: 1, Informative

    If you go to the source of the research, you will for example notice that the last time a similar study was done (in June 2006), only 2.58% of the tested pages validated completely. A 1.5% increase might not seem to be all that much, but it's definitely indicative that we're on the right way. (And of course, perfect validation is never the final goal in itself, but merely an easy first step for people en route to writing better, semantically-meaningful, universally accessible websites.)

  32. <blink>really?</blink> by Anonymous Coward · · Score: 1, Funny

    Inconceivable!

  33. Re:Sad. Even sadder is the yet-another-feature cre by foniksonik · · Score: 1

    unfortunately the vast majority of the web would not exist if it had to meet your standards. People don't create content for free... well the majority of them don't.

    Copywriters cost $100/hour + and nobody wants to pay that much if the copy being written is going to go online into a format that amounts to a high school term paper.

    Also nobody wants you to have the power to view their content the way YOU want to. They pay hundreds of thousands of dollars for a web site that communicates their content the way THEY want it communicated.

    --
    A fool throws a stone into a well and a thousand sages can not remove it.
  34. Now if only they could⦠by joeharrison · · Score: 1

    Now if only they could get MAMA to automatically scold the people that aren't compliant

  35. New Window !== evil by jDeepbeep · · Score: 1

    Annoying behaviour by web developers who think no one could possible want to, god forbid, leave their site in favor of another site.

    There are times when it can be appropriate. When it's absolutely needed however (read: the boss wants it that way) I'll use a mini icon to give a visual cue that it opens in a new window.

    --
    Reply to That ||
  36. The dirty secret of web development... by Anonymous Coward · · Score: 0

    I use Noscript and I don't even bother to explore sites that are totally borked without their Javascript crutch

    ...Is nobody cares about you.

  37. Re:Sad. Even sadder is the yet-another-feature cre by Firehed · · Score: 2, Interesting

    So override with a stylesheet that looks roughly like:
    * {
    color: #0F0 !important;
    background-color: #000 !important;
    }
    div {
    display: block !important;
    float: none !important;
    }

    and you'll be all set. The rest of us tend to like looking at something that doesn't resemble a terminal window all day long. There's a reason that browsers provide the ability to override stylesheets and disable javascript. CSS, JS, and all of that other stuff don't take the presentation layer away from you (in fact, they make it a hundred times easier to override rather than the inline styles of old), they just provide defaults.

    --
    How are sites slashdotted when nobody reads TFAs?
  38. Re:Only 4.13% of the Web Is Standards-compliant .. by Anonymous Coward · · Score: 0

    ...the rest just renders perfectly in IE.

    ...and then IE crashes, that's why it is not compliant;)

  39. Re:Only 4.13% of the Web Is Standards-compliant .. by rgo · · Score: 1

    ...the rest just renders perfectly in IE. (i would prefer if there wasn't any truth in it.)

    To be honest, most of the rest also renders perfectly on Firefox.
    The sites that don't are mostly Microsoft and online banking sites. But who cares about them? *sigh*

  40. I am probably just repeating here but... by ParanoiaBOTS · · Score: 1

    1.) When the majority of browsers start supporting standards, so too will developers. Now that is not to say there aren't browsers that support the standards. But I have found that I can write a site that meets standards 100% (fairly difficult to do) but to get it to work in IE I have to hack. When I am done hacking it to work in IE, I am probably down to somewhere in the 50-65% compliance range. So your options are typically: be standards compliant and screw IE users. OR you can support IE users and screw standards. IE6 just makes this 10X worse too...lets retire IE6

    1. Re:I am probably just repeating here but... by bunratty · · Score: 1

      If developers stop getting pages to work in IE6, users will stop using IE6 because pages don't work. If developers keep making pages work in IE6, users will keep using it.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    2. Re:I am probably just repeating here but... by Rendoggle · · Score: 1

      That only works if every webpage in the world decides to say 'FUCK YOU!' to IE6. And that would require every web developer to say 'FUCK YOU!' to 25% of the web population. That will not happen.

      The ordinary user does not care about what browser they're using. They care about the accessing content. If one site says 'sorry, please upgrade your browser.' then users will simply migrate to another site. And that site'll have more visitors.

      Take Facebook, for example. They had a whole fancy Ajax-y redesign. They also didn't support it in IE6, and told people to upgrade or use Flock, Firefox or Safari. Fantastic news - but the point here is that IE6 users were not excluded outright, because it made best sense for them [Facebook] as a business.

      As someone who's hacked about with CSS and javascript a bit, I would rejoice if I heard IE6 had just died a long, drawn-out and tortuous death. Firefox has considerably helped with this, but non-technical people do not care. And since lots of non-technical people use IE6, developers cannot stop supporting it; it's a chicken and egg problem.

      Unfortunately, short of a Windows Update that upgrades IE6 to 7 or 8, IE6 is not going anywhere soon.

    3. Re:I am probably just repeating here but... by BenoitRen · · Score: 1

      The majority already supports web standards. It's just IE, as you said. You don't need to reduce standards compliance to make your page work in IE. Either use some CSS hacks, or, even better, use IE's conditional comments to serve a stylesheet to IE only to fix whatever's wrong.

    4. Re:I am probably just repeating here but... by Shados · · Score: 1

      Windows Update -did- push IE7.

      However, people still stick to versions of Windows that don't support it (there's still tons of people on Win98/ME, and of course Win2k, though those really should use another browser if they can help it), and it was "OMG EVIL MS PUSHING THEIR BROWSER", so there was an opt out method, as well as a confirmation that you could refuse.

      Because of that, IE6 still lives.

    5. Re:I am probably just repeating here but... by bunratty · · Score: 1

      Exactly. That's why asking for IE6 to retire is stupid and pointless. This is what developers do. They make sites work in IE6, then lament that users still use it. Well, of course they do, stupidheads!

      --
      What a fool believes, he sees, no wise man has the power to reason away.
  41. Hey Joe by Slash.Poop · · Score: 0

    Does it matter even to Joe the Plumper or Joe Six Pack?

    No, for real that was a serious question.
    If Joe Newb goes to his favorite website (using his default browser) do you actually think he even knows that it might not look like it is suppose to?

    This whole compliance war makes little or absolutely no difference to Joe Average. You can argue that he should care about it but within 2 seconds you would have talked circles around him and he will just tell you "but this website looks fine to me and that is all I care about."

  42. invalid allegory by circletimessquare · · Score: 1

    1. jpeg is a old cold hard standard. its not evolving. additionally, its a very limited spec: it involves static images. no more. the web is anything goes, anything you can write up in an sgml flavor, encode, and stuff into http, standards constantly evolving. comparing jpeg to the web is like comparing a carrot to the entire vegetable kingdom. orders of magnitude of difference in dimensions of description

    2. lots of the coolest stuff you can do with webpages involve things that are far outside any standards. like ajax. or howabout youtube: enocding videos as flash. these are things that evolved on their own, outside of any standards committee. in fact, they used proprietary technology from microsoft and adobe at first. not only that, they used proprietary technology in innovative ways that the technology wasn't meant for. microsoft's early ajax-like code was meant to be an outlook extension. adobe's flash was meant to describe simple animations, not video encoding. but if one appreciated the power of the idea of ajax or video encoding in flash early, and wanted to play with it, as a hobbyist, you could. and why shouldn't they? a hobbyist is supposed to wait for standards to keep up? a hobbyist is supposed to wait until someone writes a brain dead point and click interface before tinkering? you think the web is better without youtube or google maps? of course you don't. but that's what your jpeg allegory is trying to tell us about standards and the still evolving web

    what innovation means, and how its fits into the picture, and how innovation works, has nothing to do with standards. on the contrary, its the thematic opposite of standards compliance. innovation comes first, and then a long time later, standards comes along and consolidated the best practices that were discovered as innovative technologies move from the cutting edge into mainstream mundane use

    what you don't do is get in front of innovation, and write standards for it before people innovate. that's insane. no one is so omniscient as to know what the next great leap forward on the web will be, and when it will happen, and what format it will first manifest itself in. no one says "i'm going to write the spec for encoding video on a webpage before it happens, and everyone is going to fall in line behind me, and everyone is going to use brain dead point and click interfaces to make that happen." actually, some people did try to do that. look up vrml (virtual reality markup language) from the mid90s, amongst many other examples, of standards trying to come before innovation. it doesn't work. its not how technology evolves

    but this is what you expect us to appreciate if your jpeg allegory is supposed to be instructive to us about the relationship between the jpeg spec and webpage specs

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:invalid allegory by Anonymous Coward · · Score: 0

      2. lots of the coolest stuff you can do with webpages involve things that are far outside any standards. like ajax. or howabout youtube: enocding videos as flash.

      None of the things you mentioned depend on having invalid HTML code. What does invalid code allow that valid code does not?

  43. The problem is not syntax by coryking · · Score: 1

    The problem is the W3C and "standards advocates" are chasing the wrong problem. They view the problem like this:

      - Standards = Proper structure. Correct use of syntax. Cross your t's, dot your i's and leave it to the browser to decide how a page is rendered.

    Worse, this "who cares how it is displayed on the browser as long as you get the syntax right" is considered to be a feature by these types! The rest of the world, all 95.87% of them, don't think of "Standards" that way. For the majority, standards means only one thing:

      - Standards = Looks and Behaves the same on all browsers.

    The longer the W3C denies the majority definition and continues to dismiss the importance of a standard way of browser behavior, the longer they remain in the wilderness. The W3C will be the minority until they define how web browsers should *render* a page so that HTML *looks* the same regardless of browser.

    And before you shoot back to me and carry the W3C talking point "it is up to the browser to determine how to render and dammit, it is a feature not a bug", remember that this very article asserts you are the minority.

    Either accept that the majority of us want browsers to display a page the same way, or continue to be dismayed when nobody cares about your standard.

  44. Re:Sad. Even sadder is the yet-another-feature cre by SanityInAnarchy · · Score: 1

    Instead, we've got javascript, CSS, XHTML, and other buzzwords. Which in the end, take control of how a web page looks from the user's hand.... I would like to format a web page the way I want to see it.

    You should love CSS, XHTML, and Javascript, then.

    With CSS, you can change the entire look of a webpage without changing the markup. Most browsers will let you load your own custom CSS. Without CSS, people would be using FONT tags, which you have significantly less control over.

    And Javascript allows for things like bookmarklets, or better, GreaseMonkey. You can write or download a script which does, well, whatever you want to a given page, as you view it. One I've been playing with recently adds a "download MP4" link right into the middle of every YouTube page. Off the top of my head, if you really hate my post, and don't want to see any more comments from me -- I'm not sure if Slashdot itself allows this, but you could write a Greasemonkey script to do it.

    The vast majority of the web is simple formatted text. There is no reason for this to constantly evolve onwards and onwards.

    Simple formatted text can look better.

    And, like it or not, the Web is an application platform now. What you're saying is kind of like wishing computers never evolved beyond calculators.

    --
    Don't thank God, thank a doctor!
  45. How to do your bit for standards compliance by Ed+Avis · · Score: 2, Interesting

    Nowadays making sure your site is valid HTML is easy. Just install the excellent HTML validator plugin for Firefox. It gives you a tick or cross icon on each page; double-click the cross to view the page source with a list of errors. It does the validation locally on your machine, not sending the content off to some server, so it's fast.

    If you're writing dynamically generated pages it is a great way to find bugs in your code, and it's unobtrusive enough to leave it turned on all the time.

    --
    -- Ed Avis ed@membled.com
    1. Re:How to do your bit for standards compliance by Cope57 · · Score: 2, Informative

      There is also a Web Developer plug-in available at the FireFox Add-ons site.

      --
      http://www.accountkiller.com/removal-requested
    2. Re:How to do your bit for standards compliance by Quietust · · Score: 1

      The problem with Web Developer is that using it validate a page requires it to submit it to validator.w3.org over unencrypted HTTP, which may be a breach of security if your page is displaying any sensitive information. The aforementioned HTML Validator add-on has the advantage of running entirely locally and not transmitting any data across the network.

      --
      * Q
      P.S. If you don't get this note, let me know and I'll write you another.
  46. Re:Sad. Even sadder is the yet-another-feature cre by SanityInAnarchy · · Score: 4, Insightful

    I'm really not sure what your comment about AJAX calls has to do with "ignoring standards" -- especially given that:

      - XMLHttpRequest is a standard
      - It was always possible with a hidden iframe anyway, which is also a standard

    --
    Don't thank God, thank a doctor!
  47. What about Google? by Anonymous Coward · · Score: 0

    Google.com isn't even standards compliant

  48. Re:Sad. Even sadder is the yet-another-feature cre by DorkRawk · · Score: 2, Insightful

    Why can't the web stick to something simple? 95% of the sites I use, would be fine with just plain simple HTML 2.0. Instead, we've got javascript, CSS, XHTML, and other buzzwords. Which in the end, take control of how a web page looks from the user's hand.

    I like to read text, on a monitor, green on black (or white on black). I would like to format a web page the way I want to see it.

    The vast majority of the web (that this user likes to view) is simple formatted text. There is no reason for this to constantly evolve onwards and onwards.

    Face it, you are the minority. Hell, most people here on Slashdot are the minority. First off, CSS, XHTML, and Javascript aren't buzzwords. They are technologies (AJAX is a buzzword... but it's still pretty cool). If a web page doesn't control how it looks who is? The user? Listen closely... MOST PEOPLE LIKE THINGS THAT LOOK NICE AND DO COOL THINGS. THE NUMBER OF PEOPLE WHO WANT TO READ MONO-COLOR TEXT FOR ALL INFORMATION OUT THERE IS VERY MINIMAL. If you don't need any of it, browse without stylesheets, images, and javascript turned on.

    The Amish get by just fine without electricity and things like that, but they don't try to fool themselves into thinking that nobody should have it, just because they don't want it.

  49. The flaw goes deeper then that by coryking · · Score: 1

    The real flaw is the underlying philosophy that the standards, HTML/CSS, should never get to make assumptions on how a page is rendered by a client. This philosphy, a core value of the W3C, says that as long as you the website author do not get to dictate how a page is rendered.

    Unfortunately, this core value is at odds with what the industry is demanding. The industry is demanding there be a *standard* for how a page is rendered. The attitude is now "screw the 'standards' as long as it works in all the browsers". And clearly this attitude is the majority, or more people would be following the W3C standards. Worse for the W3C, people are now routing around their standards by using Flash and Silverlight, both of which render content in the same manner regardless of browser.

    I hold that until the W3C rethinks their long held value that it is up to the browser to decide how a page is rendered, they will be unable to meet the needs of a rapidly changing industry.

  50. No... by tragedy+in+chaos · · Score: 1

    Every one is interpreting this wrong. I'm sure they were talking about political, not web standards. And it looks as though the porn industry just got a lot larger.

    --
    Microsoft - The best ad campaign Apple ever had.
  51. Re:_Already_ 4.13% of the web is standards-complia by AndrewNeo · · Score: 1

    Another thing you have to compare between back then and now is the total number of websites there are entirely. A 1.5% increase to the same number of total websites may not seem like all that much, but if you consider how many new webpages have likely appeared in the past two years, that's a significantly larger number.

  52. Don't BLINK or you'll miss it. by Smivs · · Score: 2, Interesting

    BLINK will validate. To my eternal shame I've used it on my Home site's humour page and it passes w3c validation (just checked it to make sure). P.S. please don't slashdot me!

    1. Re:Don't BLINK or you'll miss it. by Lachlan+Hunt · · Score: 1

      Your page only uses <span class="blink">NEW!</span>, which is styled using text-decoration:blink;. That's different from the <blink> element that was actually being discussed.

      --
      By reading this signature, you hereby agree with the content of the above comment.
  53. Try this. by Smivs · · Score: 0, Flamebait

    Save the developers! have a nifty bit of script which generates a drop-down when it detects I.E.6 being used, which urges the user to upgrade. It's subtle and inoffensive. I add it to all my sites.

    1. Re:Try this. by billcopc · · Score: 1, Troll

      There's nothing subtle and inoffensive about telling someone to change their browser.

      What if everytime you stopped at a gas station, the attendant said "Your Ford sucks, why don't you go visit the Toyota dealership down the road, where my brother Ackbar works"... I would choke that little he-bitch!

      People who use IE are often quite happy with it. They don't need to be beaten over the head with Firefox ads.

      --
      -Billco, Fnarg.com
    2. Re:Try this. by Jane_Dozey · · Score: 1

      Subtle and inoffensive like someone berating your choice of clothes before they say anything else every time you go to speak to them.

      Respect other peoples choices. If standard code breaks their web browser on your site and they complain *then* give them advice.

      --
      Silly rabbit
    3. Re:Try this. by pizzach · · Score: 2, Insightful

      It looks like the page is more about upgrading browsers rather than changing browsers (at least for now). The message is more akin to the gas attendant saying "Fix your muffle because it's a nuisance to other people on the road," and not "Get a new car!" The original poster said nothing about changing browsers either.

      --
      Once you start despising the jerks, you become one.
    4. Re:Try this. by spinkham · · Score: 1


      Lets say I'm a road builder, and I know your 2001 Microsoft Road Explorer sucks and would cause me many hours of work to work around it's bugs.

      Lets say I decide I'm not planning on doing that extra work in my future roads, and I put up a sign telling you that your car is faulty and you should go to your dealer for a FREE safety and functionality upgrade.

      It's hard to argue that that is a bad thing to do.
      </car analogy>

      There's no excuse for using a web browser from 7 years ago. As long as you are using XP or later, IE 7 is easy to aquire and install, and is a much better browser for both the user and developer.
      Now, telling them IE sucks and they should go to firefox might be considered rude(if still good advice), but urging them to upgrade to the latest free version of the software they're using is not bad form. It's nothing but good for them to upgrade.

      --
      Blessed are the pessimists, for they have made backups.
    5. Re:Try this. by Smivs · · Score: 1

      That's why I don't have a problem using it. I have seen some scripts used which are well over the top and even some which refuse to display the site on IE6...what's the point in that? Save the developers seems to be slashdotted at the moment so if you can't see what I refered to, it's a tiny drop-down explaining to IE6 users that their browser is out of date. It then offers a download of IE7 and also the option of converting to Firefox, Opera or Safari. It's not specifically critical of people's choice of browser and primarily suggests the IE7 upgrade.

    6. Re:Try this. by riceboy50 · · Score: 1

      Good thing motor vehicles all adhere to some standards that make them interoperable on the road such as lights/signals, license plates, wheels/tires, etc. Do we really need to get the government involved to force interoperability on the Web?

      --
      ~ I am logged on, therefore I am.
    7. Re:Try this. by blofeld9999 · · Score: 1

      What if everytime you stopped at a gas station, the attendant said "Your Ford sucks, why don't you go visit the Toyota dealership down the road, where my brother Ackbar works"...

      Ackbar? It's a trap!

  54. Opera's article by Anonymous Coward · · Score: 2, Informative

    Here's Opera's article, with actual numbers:
    http://dev.opera.com/articles/view/mama-markup-validation-report/

  55. The real world goes beyond IE and Firefox by Smivs · · Score: 1

    What an arrogant approach! Based on recent figures I calculated that 1/4 million people are using Opera (I'm one of them) in the U.K alone, and many countries have a higher percentage than this. And Safari users are probably even more numerous. Your clients are asking you to design sites that will piss-off millions of people world-wide. Good plan!

    1. Re:The real world goes beyond IE and Firefox by elrous0 · · Score: 2, Insightful

      If it looks and works the same in both IE and Firefox, the odds are pretty high it's going to work just fine in Opera and Safari too. If that weren't the case, trying to use Opera or Safari (with so many designers designing for and testing on IE only) would be a huge hassle.

      --
      SJW: Someone who has run out of real oppression, and has to fake it.
    2. Re:The real world goes beyond IE and Firefox by Smivs · · Score: 1

      That's not necesarily true. I just wrote a little on-board homepage for my wifes computer. She uses firefox, so I designed it with that in mind. It's standards compliant and the HTML and CSS both validate. Out of interest I checked it on Opera and IE7 and it's fine but on Safari it's a mess! I've found it's wise to check on all browsers, and if you're using a liquid layout check on 'square' and 'wide' monitors.

  56. if all browsers rendered the same by circletimessquare · · Score: 1

    you wouldn't have a job. you would be fired and replaced by a point and click interface your clueless boss would use

    do not belittle browser incompatibility, it keeps you employed. it means you have special rare expensive expertise, rather than common cheap expertise

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:if all browsers rendered the same by Anonymous Coward · · Score: 0

      Um, speaking for myself, my "expertise" extends far beyond accounting for browser standards-compliance errors. In addition to having to know x/html, there's CSS, XML/RSS, C# (and VB), ASP.NET, image manipulation (PhotoShop, GIMP, etc), accessibility issues (ADA/section 508) and any RIA stuff we decide we want, a la Flash or SilverLight. Honestly, there's so much more to Web design and development that I'd rather be focusing on that trying to make stuff appear the same in "x" number of browsers because they all insist on rendering things differently than what the W3C has mandated. The fact that not everyone out there has made "point-and-click" their Web management paradigm, a la Wikis and whatnot, and not then fired their Webmasters, speaks to the complexity that such systems can't yet handle, and may never handle.

      No, all that standards-noncompliance achieves is to slow us all down.

    2. Re:if all browsers rendered the same by Anonymous Coward · · Score: 0

      do not belittle browser incompatibility, it keeps you employed. it means you have special rare expensive expertise, rather than common cheap expertise

      Please see the Parable of the broken window. We're all worse off when we're forced to waste effort.

  57. Opera's Hidden Agenda -- Making Excuses by Anonymous Coward · · Score: 0

    1) If 95% of the world doesn't follow a spec, then it's not a standard, it's a guideline at best.

    2) Who's actually used Opera? It's so unstable as to be completely unusable. If you start with something as simple as Google News' home page, and just start clicking stories, you'll find that it crashes on about every third web page for one reason or another. This is my most recent experience with Opera 9.6 on Vista, YMMV.

    This study is a not-so-subtle way of "explaining" why their browser only works 5% of the time, not a critique of any adherence to so-called standards.

  58. compliant or conformant? by bugi · · Score: 1

    Do you mean "compliant" or "conformant"? There is a difference.

  59. Re:Sad. Even sadder is the yet-another-feature cre by Rendoggle · · Score: 1

    I like to read text, on a monitor, green on black (or white on black). I would like to format a web page the way I want to see it.

    This is what user style sheets are for. By using !important (in particular), the user can override the styling (see also the spec). Something like this might do the trick:

    * {
    background: white none !important;
    color: black !important;
    }
    As far as making a user stylesheet is concerned, this might help you with that.

  60. What is "standard" by bitsiphon · · Score: 1

    Does the fact that 95.87% of the web is not "standards compliant" make being not compliant the Standard?

    1. Re:What is "standard" by Shados · · Score: 1

      Thats actually a very important thing to consider: W3C doesn't make "standards", it makes standard propositions, specs.

      If it becomes the standard is if its accepted or not. Amusingly enough, the only reason its even semi-accepted is because people pushed it as "THE STANDARD!" way before it ever was, and now it kindda is. A standard thats not accepted is not a standard.

  61. Browsers to blame by frisket · · Score: 1

    Of course, if the browsers had been standards-compliant, perhaps it might have encouraged the siteowners...

  62. Re:Sad. Even sadder is the yet-another-feature cre by Anonymous Coward · · Score: 0

    No tags needed here. Just plain old text.

    At a fundamental level, the issue is one of literacy. People who are functionally illiterate -- a sad state within a supposedly advanced civilization -- require devices and techniques that go well beyond the ordinary printed word. The illiterate need pictures to convey even the simplest of ideas and this is the major reason why the Web has proliferated to its current state of inane animations and flashy visual thrills. Such presentations are very costly in terms of bandwidth and storage, but, as with the passion plays of the Middle Ages, pandering to the illiterate masses is an unfortunate necessity.

    It is therefore inaccurate to state that "MOST PEOPLE LIKE THINGS THAT LOOK NICE AND DO COOL THINGS." The preference for such methods is directly related to the level of literacy. The correct expression would be: "MOST PEOPLE, BECAUSE THEY ARE SADLY ILLITERATE, *REQUIRE* THESE EXORBITANT VISUAL DEVICES TO BE ABLE TO GRASP EVEN SIMPLE MEANINGS."

    Rejection of the current state of the Internet is not a rejection of progress or technology. It is only the outrage of the refined and sophisticated to the unschooled methods of functional barbarians.

  63. the standards-noncompliance you speak of by circletimessquare · · Score: 1

    is more commonly known as innovation

    you're like a guy complaining that the different railroad companies all use a different track gauge so you have to keep retrofitting the rail cars you build

    i'm sorry progress is messy. but there are no standards, because the web is still evolving. standards cannot get in front of innovation. standards must naturally follow behind innovation, and consolidate

    in 30 years, maybe it will be all the same, and then your complaints would have some validity. but right now, your complaints are hollow, because you simply don't understand the historical context in which your job exists. you work in an evolving, fluid specialty. you're not a plumber, working in a field that has existed since the romans, and all the pipe sizes are standardized

    so stop complaining. what you complain about is completely unavoidable, and is the flip negative side of a much greater positive that makes your job even possible: technological innovation and creation

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  64. if it were 1994 by circletimessquare · · Score: 1

    and some guy told you tables were frustrating to work with, and instead why not put everything in nested divs, and describe the different classes of styles of the different divs in an external file, so as to effect easy modification of rendering in one change rather than going into every td element and changing the test alignment to left rather than center, for example, would you have deducted points for not following the standard way to render tables?

    if not, you understand my point about the proper relationship between messiness, innovation, and standards

    in 30 years you would be dead on. but the web and its standards are still evolving. as such, messiness reigns, and is a sign of creative ferment, which is a good thing

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  65. Re:Sad. Even sadder is the yet-another-feature cre by Dlugar · · Score: 1

    ./ is mostly text, but how did you post this comment? Any Page refreshes?

    Actually, yes, I have the crappy /. AJAXy stuff turned off, so it properly POSTs my form and does a "page refresh".

    Tell me again why this is A Bad Thing[tm]?

    Dlugar

    --
    Computer Go: Writing Software to Play the Ancient Game of Go
  66. so what would you say by circletimessquare · · Score: 1

    about the hobbyist tinkerers who used a microsoft outlook component to do partial page refreshes, eventually creating what we now know as ajax?

    hobbyists are not brain dead morons following the pack. they lead the pack

    in fact, those overly obsessed with standards compliance represent a sort of brittle, uncreative mind that is in fact the brain dead morons who trail at the bottom of the pack. everything must be in a straightjacket, or they can't deal

    creativity trumps all of your observations. standards follow innovation, not the other way around

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  67. Appeal to the DC court... by omuls+are+tasty · · Score: 1

    Basically, once the appeals court overturned the antitrust decision, it was pretty much game over. Microsoft has had virtually no need to improve on IE, because most users are not technical, they just understand that they click on the "Internet" icon and they're "on the Internet", for whatever that means. More than once I've had people panic because "their Internet has changed" - i.e. after they somehow click the "upgrade" button and got IE7 instead. The comforting Microsoft messages upon IE7 installation did little to help, considering I live in a non-English speaking country.

    Until something finally kills off Windows, or the new generation who's grown up with computers comes up, I don't see how it's going to change.

    On that day I will download a photo of Gates, print it out on photo paper, burn it and celebrate. In the meantime I just try to make my pages W3C compliant and display their banner.

  68. Standards by BhaKi · · Score: 2, Insightful

    The very purpose of standards is to make "Working" a property of a website. It is a shame that the world let M$ kill standards.

    --
    The largest prime factor of my UID is 263267.
  69. Re:Only 4.13% of the Web Is Standards-compliant .. by pbhj · · Score: 1

    You're obviously not a web designer .. IE which version.

    Pages that render perfectly in any one version are by no means guaranteed to render properly (or even usably) in any other version. Possibly with the exception of IE7 and IE8 when in IE7 rendering mode; but not fully tested that assumption yet.

  70. 2 things by circletimessquare · · Score: 1

    1. a webpage is not a c program. a c program HAS to be anal retentive to work. out of millions of lines, one misplaced ascii character and the whole thing is mud. a webpage meanwhile is just a bit of aesthetic markup, it can degrade, it can degrade heavily, and it is still worth something

    2. you're complaining about different track gauges in the dawn of the age of railroads. i would expect that engineers who had to build rail cars a century and a half ago would complain about customizing every car for 5 different gauges. however, that's the way innovation works, its messy. standards do not get in front of innovation, innovation leads and standards trails behind, consolidating. now, today, all track gauges are standardized. and, in a decade or two or more, all webpage markup will be standardized. but not while we're still innovating in that area in the time we exist in: its still the dawn of the internet in 2008. so your complaints and your perspective are perfunctory and premature, outside of an understanding of proper historical context. they would be true uttered in 30 years time, but your words are not true today

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  71. Re:Sad. Even sadder is the yet-another-feature cre by pbhj · · Score: 1

    Why can't the web stick to something simple? 95% of the sites I use, would be fine with just plain simple HTML 2.0. Instead, we've got javascript, CSS, XHTML, and other buzzwords. Which in the end, take control of how a web page looks from the user's hand.

    Why can't actors stick with something simple - 95% of films I see could be performed in the round without sets or ornate costumes. Instead we have special effects and costumes and makeup, specialist lighting, post production colouring, fancy-smancy cameras, stuntmen and other needless hollywood stuff. These in the end take control of imagination out of the user's hands.

    ---

    In the end it's both an informational, entertainment and advertising medium and anything used in other media gets it's version in this one.

  72. i am not advocating chaos by circletimessquare · · Score: 1

    i am recognizing chaos is undeniably part of the mix. we are still innovating in markup. what do you think ajax is doing to how webpages are customarily handled, in a fundamental way? you think we've figured out html and css and that's it, end of story, no further changes?

    this is what i know about chaos, and what you must learn: standards do not lead, and then innovation follows. no, messy innovation leads, and standards follow behind, consolidating

    the chaos you perceive is the creative ferment that makes the entire internet as we know it possible. its not some junk and noise, its the process of creation. it is more important than standards

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:i am not advocating chaos by BenoitRen · · Score: 1

      You can innovate messily without creating a web page that doesn't even follow the basic HTML4 standard. I also find that you put too much faith into the people at large. Most of the people don't know what they're doing, and they're certainly not innovating.

  73. Only 4.13% of the Web Is Standards-Compliant... by no1home · · Score: 1, Funny

    The rest are designed to work with MS IE.

    --
    I hope this comment is well received... I could have moderated instead!

    Persecutors will be violated!
  74. poor analogy by circletimessquare · · Score: 1

    better analogy: in the early days of the railroad, there were many different track gauges. this made life hell for railroad car engineers who had to retrofit all of their designs. eventually, one gauge won out and standardization took place

    and there WERE a lot of car crashes in the early days of automobiles due to reasons that would be stupid today. and there WERE a lot of cases of botulism in the early days of canning

    the point is, in the early days of technology, there is no standardization. innovation leads, standardizaiton follows, consolidating. not the other way around

    the chaos you see me advocating is rather the chaos i see as simply an inevitable part of the process of innovation and technological creation. its unavoidable, and you don't standardize it up front, you standardize it later. your entire perspective on the issue is wrong and backwards

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:poor analogy by pbhj · · Score: 1

      better analogy: in the early days of the railroad, there were many different track gauges. this made life hell for railroad car engineers who had to retrofit all of their designs. eventually, one gauge won out and standardization took place

      What I'm saying is that it would be better if all the railroads had fit a standard gauge. Every passenger doesn't need to make their own railroad car - they can ride on one made for them, or if they want they can just build the car on a pre-made railroad truck (just the platform).

  75. xhtml + application/xhtml+xml = no errors by WebmasterNeal · · Score: 0

    Why not serve your content as application/xhtml+xml and use xhtml. Your browser will choke if it incurs any validation errors.

    And yes IE will properly render xhtml with a little work - http://www.nealgrosskopf.com/tech/thread.asp?pid=1

    --
    "During My Service In The United States Congress, I Took The Initiative In Creating The Internet." -Al Gore
  76. Search and composition forms on one page by tepples · · Score: 1

    I presume you mean submit the form and have the form page stay open and the submission complete page show in a separate tab/window. Not sure how useful that is (you can page back to view a forms submitted content in FF)

    Imagine a web page with two forms: one for search and one for composing a long text. I want to display the search results while keeping the text area open. This has happened to me dozens of times while editing Wikipedia articles.

    1. Re:Search and composition forms on one page by pbhj · · Score: 1

      OK, gotcha, thanks for explaining - still sounds like a feature request but I see the utility. Sometimes an extra click is one too many.

  77. Uh.. question.. by Markimedes · · Score: 1

    What percentage of the web is even frequently visited? I'd say that the average user uses 1% of the internet (or less), the question is how much of that 1% coincides among people; then you might see that a much much larger percentage of websites that are actually relevant will be standards compliant.

  78. Reason? by QuietLagoon · · Score: 0, Redundant

    Probably because 95.87% of the web is Internet Explorer compliant.

    1. Re:Reason? by QuietLagoon · · Score: 1

      Yeah, I wasn't sure if it was redundant or not. I didn't have the time to wade through all of the other similar comments before posting mine.

  79. you've just described evolution by circletimessquare · · Score: 1

    a bunch of random crap being flung on the wall, having no idea what will stick. and out of the mess comes... us, homo sapiens

    do you think that the guy who took an obscure ms outlook component and used it to do partial refreshes of webpages knew he was creating ajax? could you, in the late 1990s, have looked at what that guy was doing and you would have perceived with absolute omniscient clarity such a groundbreaking innovation? could he even?

    there is no purposeful effort, its blind fumbling. progress is nothing more than a mistake at first, that is recognized eventually to be better than the "right" way to do things. its like asking if fleming knew what he was doing when he screwed up a bacterial culture and discovered penicillin

    simply put: your understanding of what innovation is is flawed. innovation very much is a process of people having no idea what they are doing. those messy fools you perceive are like that guy working for cern 20 years ago spending WAY too much time with markup (aka, tim berners-lee). you think he knew what he was doing? you think he woke up and said "i'm going to pave today the way for perhaps the most earthshattering form of media mankind has yet invented"? no, he was just trying to share research. nothing purposeful about what his work did.

    "Most of the people don't know what they're doing, and they're certainly not innovating."

    the invention of the internet was EXACTLY that: a bunch of people, in small steps, having no idea what they were doing, and innovating. innovation is the exact opposite of how you perceive it

    as for what i put faith in, yes, absolutely, i put faith in people at large to innovate, as a group. on an individual basis, 99% of them are idiots. but there is absolutely no way you, me, or anyone else can differentiate between insane ramblings of an idiot, and the next great technological innovation. because neither of us, nor anyone, is omniscient

    so you respect the mess, because you have some humility about where you really are in the process. you don't have control over it. no one does. or at least, you should learn that humility

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:you've just described evolution by BenoitRen · · Score: 1

      You don't get it. The mark-up has already been messed with, and consolidated with standards. But we still have most people writing crappy HTML.

      You don't need to ignore all the standards to experiment with standards that you think still need messing with, like JavaScript. You take a solid base, and build on that.

      The mess you create still has to show properly in my web browser in the end!

  80. Re:Sad. Even sadder is the yet-another-feature cre by Anonymous Coward · · Score: 0

    Iframes are invalid in xhtml strict.

  81. No surprises by speedingant · · Score: 1

    The rest is FaceBook and Myspace pages.

  82. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  83. Re:Sad. Even sadder is the yet-another-feature cre by DorkRawk · · Score: 1

    Are you really arguing that plain text is the most efficient way of expressing all ideas? Are you really saying there is no communication value to sound and images?

    Sure there are a lot of people misusing multimedia, but does that make it an invalid form of communication? Try to show some knowledge of usability outside your own personal preference.

  84. Comment removed by account_deleted · · Score: 2, Insightful

    Comment removed based on user account deletion

  85. heroin by Anonymous Coward · · Score: 0

    People who use IE are often quite happy with it. They don't need to be beaten over the head with Firefox ads.

    So are heroin addicts as they shoot up. Being advised to use Firefox is an intervention.

    1. Re:heroin by billcopc · · Score: 1

      And that is why we come from different attitudes... I think heroin addicts can do whatever the hell they want to themselves, as long as they do no harm to others.

      The way I see it, if someone's happy with IE6 and they put up with its quirks, they have the same rights as anyone else.

      --
      -Billco, Fnarg.com
  86. Re:Sad. Even sadder is the yet-another-feature cre by coopaq · · Score: 3, Informative

    XMLHttpRequest is now a standard since everyone decided to "ignore standards" and use it anyway.

    http://en.wikipedia.org/wiki/XMLHttpRequest

    "The World Wide Web Consortium published a Working Draft specification for the XMLHttpRequest object's API on 15 April 2008."

  87. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  88. Re:Sad. Even sadder is the yet-another-feature cre by coopaq · · Score: 1

    Page refreshes:
    1) cause more data to be transmitted which is slower
    2) cause more cpu cycles by re-rendering the whole page on your client
    3) all of this probably uses more electricity
    4) wastes time
    5) kills baby seals
    6) causes markets to crash
    7) makes you lose bids on ebay

  89. of course by circletimessquare · · Score: 1

    it would be better if i could fly by flapping my arms. it would be better if i had a billion dollars. none of which describe reality, nor have you. innovation does not proceed in the way you describe. its messy. wouldn't it be neat if innovation were clean and standardized? yeah, of course. except it never will be, so what you say is pointless

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:of course by pbhj · · Score: 1

      But the reason the web is largely non-standards compliant is little to do with innovation. How many non-standards compliant sites are that way because they include HTML5 or CSS3 code that hasn't been ratified as standard yet? Or because they're doing some funky DOM manipulation or whatever? No the sites are broken because people can't be arsed to fix them on the whole.

      Innovation, as you say is messy, organic and almost by definition doesn't adhere to standards frameworks .. but I'd be prepared to bet that less than 1% of websites could really be classed as innovative.

      Take Adobe's Kuler site for example, it's innovative but only in regard to the flash site embedded in the website - the website is just a simple frame to hold the flash site, does it validate? No. Why not? I'd have thought a company like Adobe would be embarrassed by such laxness.

      Compare with colourlovers.com, which I think was the forerunner in this area, which implements it's site with XHTML. Does it validate, no, but it's doing a million more things with it's code.

      One of these sites can claim the excuse that it's innovative, the other not. But neither seems a million miles away (most errors seem to be URL entity issues).

  90. ok, and? by circletimessquare · · Score: 1

    of course new stuff is built on what comes before. but that observation of yours doesn't banish messiness. in fact it neatly describes the nature of the mess: weird random accretions on what works fine and is standard

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:ok, and? by BenoitRen · · Score: 1

      Except that is not what actually happens today. As I said, people still spit out invalid web pages, whether they want to experiment or not.

  91. 4.13%? by clone53421 · · Score: 1

    I wonder... if the answer had been 3.14% would the crawler have become trapped in an infinite loop?

    --
    Alexander Peter Kristopeit bought his basement from his mommy for one dollar.
  92. Fuck Compliance. by Anonymous Coward · · Score: 0

    If it looks alright in major browsers, who cares?

  93. wrong parable by circletimessquare · · Score: 1

    its early in the age of the locomotive, and there are 5 different track gauges. the engineers who have to retrofit 5 different track gauges onto their railcar design are obviously perturbed by this. it will 30 more years before one track gauge is standard. thats the flipside to innovation

    you can prevent little boys from breaking windows. but there is nothing you will ever do that will make technological innovation a clean and orderly and standardized process

    in 20 years, all browsers will render the same. until then, stop looking a gift horse in the mouth. you are mistaking the irreducibly messy process of innovation with common vandalism. you fail at choosing the right parable

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  94. Make that 4.129... by droptone · · Score: 1

    Interestingly, the site that posted the news fails validation (the story, the frontpage).

    --
    Every post I make begins with the assumption P=~P.
  95. and what is the great crime in that? by circletimessquare · · Score: 1

    do you honestly expect raising the barrier of entry to webpage publication will result in a better web? no, it will result in a smaller web, of dreary sameness. i applaud the hobbyist who knows nothing and starts churning out what you perceive as crap design. he's creating

    the value of the web is in its noisy cacophony of creation, not its fascist adherence to some page standard

    life is messy. deal with it, or go grow a small little moustache

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:and what is the great crime in that? by BenoitRen · · Score: 1

      I already explained that it isn't hard. Or do you really think no one has to make even the slightest of efforts before they actually have a web page in front of them? If the bare minimum isn't met, there will be no page.

      You're using circular logic. I think I'll abstain from further replies.

  96. its the early 1990s by circletimessquare · · Score: 1

    your html teacher is explaining how to make tables

    you tell your teacher its a straightjacket, that you'd rather work with nested divs, and describe the divs' styles in external files, for easy changeups

    "but that's not standard" the teacher replies

    yes, positive, useful, helpful creation is not standard

    an emphasis on adherence to standards is the path to technological stagnation

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  97. The validator sucks by Alari · · Score: 1

    I tried their STUPID validator a while back on some HTML code I wrote by hand, and it wouldn't stop complaining about invalid markup. First about some doctype COMMENT (which of course it didn't provide a valid template for) and then it went on to nitpick every single line pretty much. Fuck that. I'm sorry <P> isn't good enough, but the HTML code in question works on everything, including Lynx.

    You want some valid HTML? Here you go:

    <HTML>
    <HEAD>
    <TITLE>Title</TITLE>
    </HEAD>
    <BODY>
    <P>Some text</P>
    </BODY>
    </HTML>

    Guess what web browsers that code is compatible with? ALL OF THEM. =D

    --
    I use Windows... like a two dollar wh.. why don't I just go ahead and not finish that sentence.
    1. Re:The validator sucks by _2Karl · · Score: 1

      That's invalid as there's no Doc Type Definition.

      Add this:

      <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">

      to the top of the document. That line's not a comment, it's the DTD.

  98. there's no circular logic by circletimessquare · · Score: 1

    if someone makes an unreadable page, no one will read it

    that's all the consequences that are needed

    there is no need for a standards body to stand there poopooing them. in short, compulsory adherence to standards is some sort of game that has no real value in increasing the quality of the internet, but merely an exclusionary principle that serves to reduce webpage quantity, and some kinds of quality that fall outside of a narrow standard

    its useless and pointless, to emphasize standards, when they are still evolving. until they stop evolving, let the mess be, in spite of your psychological compulsion to order things. it gets in the way of innovation

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  99. Oblig. by Anonymous Coward · · Score: 0

    "yo MAMA so fat she took 3.5 million pages up the a$$!" – wait, that IS what "analysis" means, right?

  100. If only Google would award valid sites a bit by Anonymous Coward · · Score: 0

    Then suddenly many managers would go "i need this standards thing, NOW !!"

  101. My internet crawler had different results. by dontmakemethink · · Score: 1

    To conduct this research project, Opera created the Metadata Analysis and Mining Application (MAMA), a tool that crawls the web and indexes the markup and scripting data from approximately 3.5 million pages.

    After a thorough examination of over 6.2 websites worldwide, my Mama determined that 7.31% of all statistics are merely improvised and presented using unnecessarily sophisticated syntax.

    --

    War as we knew it was obsolete
    Nothing could beat complete denial
    - Emily Haines
  102. Standard? by Anonymous Coward · · Score: 0

    How can something be "standard" if only 4.13% of the net complies with it?

  103. Evan by Anonymous Coward · · Score: 0

    First off, I'm surprised it took 15 bad/ignorant comments before someone mentioned W3C.

    I know how hard it is to stay standards compliant while maintaining a site that is constantly evolving. Not to mention the hacks that need to be put in place to make a site cross-browser friendly. IE came a long way toward standards compliant when it hit version 7 (6 was a nightmare), but they still haven't made it.

    I would say, if in this study standards compliant refers to a 100% compliant page (transitional not strict) then almost all mine are but they neglect to recognize that the majority of the internet domains are kited my marketing firms that throw auto-generated pages up to get click-revenues. I doubt any of these are standards compliant, since the quality of a kiting portal is insignificant as long as it generates $.

    I would say that this study falls under the guidelines of all studies, it has a value to 100-value range of error (ie 95.87%). First, because they didn't specify the level of compliance (strict, transitional, etc...). Second, because they only tested an insignificant sample of the internet. Predictive math will always me just that, predictive. Algebraic formulas don't make it so unless you're talking about environmental ohms law.

  104. It's not that hard... by splorp! · · Score: 1

    http://validator.w3.org/check?uri=http%3A%2F%2Fwww.splorp.org%2Findex.php&charset=(detect+automatically)&doctype=Inline&group=0

    Although the Tidy function of the HTML Validator program is a bit too picky about empty tags. It's still valid, dammit.

    --
    Please don't humanize the morons around me. It makes me very uncomfortable.
  105. Hypothetical situation... by PortHaven · · Score: 1

    I is "Client"...

    Simply showing the text is not acceptable. We want it to display the same in all browsers, and in the past few versions too.

    It "all" depends on the task, the client, etc.

    Not saying don't strive for standards when possible, and coding to be accessible, etc. But I am not sure there is any browser that currently exists and renders "perfectly" to ALL standards.

    Hence, we compensate...

    ***

    Note definition of standards vary, and we all may be talking about differing aspect of standards. ;-)