The meta tag is harmless. If that’s the case, then so is the bold tag, since it can be styled in any way you like. Why is strong better? It has more meaning, and that serves the future of the web. But it doesn’t harm anyone, right? Correct. Still the idea of standards is not just to stick to standards for being pricks, but for helping the web to attain it’s full potential in the future.
It’s the best of all evils. How could this ‘solution’ possibly be the best if it means again the burden of complying is with the developers, instead of with Microsoft? I’d like to elaborate on this part:
Let’s make a comparison chart of possible solutions:
|Meta Tag||Server Config||Browser Setting||Branched Version|
|Burden on||Web Developers||Sys Admin||Sys Admin/End user||Vendor|
I have seen solutions being brought forward that would involve changes for the web developers or sysadmins of intranets. From experience I can tell that this is hardly feasible. The Meta Tag solution is similar, though it doesn’t actually require the change, it’s always optional.
I am in favor of the branched version for several reasons: not only is it a solution that is completely transparent to current internet developers (only intranet admins would download it), it’s also an easy to deploy solution. In the scenario of a browser setting, a user could accidentally have ‘IE6-mode’ switched on, giving support guys and girls all over the world a headache. The server config has to accomodate not just IIS, but any server software in the world. Hardly a good choice, however it’s possible when it’s just a header to be sent. Still, it’s a lot more fiddling then deploying software, something intranet sysadmins are very familiar with.To conclude, in my opinion we should leave the current standards aware environment as we have developed over the past years in it’s status quo: if you’re not a standards aware developer, and your publis internet site fails it’s rendering, it’s your own fault, and you should fix it! If you’re on a user limited intranet, there are more options, since you don’t have to render correctly in all browsers.