Differences between version 10 and predecessor to the previous major change of RealWorldWebCompliance.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 10 | Last edited on Tuesday, November 16, 2004 12:29:17 am | by AristotlePagaltzis | Revert |
| Older page: | version 4 | Last edited on Monday, September 6, 2004 5:00:32 pm | by PerryLorier | Revert |
@@ -1,26 +1,27 @@
This page is designed to tell commercial web developers why they should develop StandardsCompliant web pages.
-!!Why should I make my web site compliant?
+!! Why should I make my web site compliant?
-
-?tid=103&tid=113&tid=126&tid=172&tid=95&tid=99
] from InternetExplorer in droves. Windows users tend towards MozillaFirefox or [Opera], Mac users may be using MozillaCamino or [Safari]. Linux users have probably been using [Mozilla] forever.
+Because the IT department of your biggest clients are [changing|http://www.theregister.co.uk/2004/06/28/cert_ditch_explorer/] [away|http://slashdot.org/articles/04/07/02/1441242.shtml] from InternetExplorer in droves. [
Windows]
users tend towards MozillaFirefox or [Opera], Mac users may be using MozillaCamino or [Safari]. Linux users have probably been using [Mozilla] forever.
The percentage of people using a non-IE browser is estimated to be between 5% and 15%, depending on who you ask. You wouldn't tolerate a phone system or secretary that turned away 10% of potential customers who ring you...
+!! Dos and don'ts
-
-!!Do
's and don
'ts
-
-* Don't use "document.all"
in your JavaScript
+* __Don't__ create browser detection pages that lock out browsers you think won't work, or browsers you don't recognise. New browsers and versions come out all the time, and you never know when one of them will be fixed.
+* Don't use markup purely because its default display suits what you want. Use markup that
's suitable to the content, then style it using [CSS], instead.
+* Don
't test your [CSS] padding/margin/width settings by only testing in IE.
+* Do test your [HTML] pages against http://validator.w3.org/ (or the free [sgmlnorm | http://openjade.sourceforge.net/doc-1.5.1/sgmlnorm.htm] program).
+* Don't put stuff in a table without <tt><td></tt> tags around it (IE displays it, Moz might not).
+* Don't put tooltips in the <tt>alt</tt> attribute. They belong in <tt>title</tt>.
+* Be careful with your comments:
+
* Don't use <tt><!--</tt> and <tt>--></tt> in <tt><script></tt> tags without making sure they are matched. InternetExplorer won't care, but [Mozilla] will consider the rest of your page commented out.
+ * The popular <tt><!----------></tt> style
"separators" are dangerous. With an odd numbers of dashes, the comment does not close, so the rest of your page will be commented out. Best to avoid any more than single dashes altogether inside comments.
+* Don't use <tt>
document.all</tt>
in your JavaScript
* Don't use MSXMLDOC
-* Don't develop your CSS padding/margin/box model by only testing in IE
-
-* Do test your HTML pages against http://validator.w3.org/ (or the free "[sgmlnorm|http://openjade.sourceforge.net/doc-1.5.1/sgmlnorm.htm]" program)
-
-* Don't put stuff in a table without <td> tags around it (IE displays it, Moz might not)
-There's
a great guide on the specifics at
http://nexgenmedia.net/evang/iemozguide/.
+See
a [
great guide on the specifics |
http://nexgenmedia.net/evang/iemozguide/] and the [Mozilla Web Author FAQ | http://www.mozilla.org/docs/web-developer/faq.html]
.
-!!Should I support Netscape any more?
+!! Should I support Netscape any more?
If you support [Mozilla], you're supporting Netscape 7 and up. These days it's realistic to drop support for any version of Netscape 4 or below.
