Errors(?) in FP code reported by NetMechanic

[Peter Judd]

Hello all,
Created with FP 2002 SP-2, my pages are reported to have a ton of
errors by NetMechanic's HTML Toolbox at
http://www.netmechanic.com/toolbox/html-code.htm

Errors found:

----:[1]^Warning: unescaped & which should be written as
&.
----:[1]^Hint: this & character does not begin a named entity.


----:[20]^Warning: tag <script> missing required attribute "type".
----:[20]^Hint: use "type" attribute with "language" attribute.


----:[25]^Error: missing </font> end tag before <center> tag.
----:[25]^Hint: <center> element NOT allowed in <font>...</font>
element.


----:[115]^Warning: <nobr> is NOT approved by W3C.
----:[115]^Note: <nobr> is NOT supported by HTML 4.0 standard..

and many more.
These are coding concerns that should not be any business of a Wysiwyg
editor user like myself.

Is FP incompetant?
Should I be using it?
Is HTML Toolbox off the rails?

Thank you for helping,
Peter

 

[Jim Buyens]

-----Original Message-----

Hello all,
Howdy.


Created with FP 2002 SP-2, my pages are reported to have
a ton of errors by NetMechanic's HTML Toolbox at
http://www.netmechanic.com/toolbox/html-code.htm

Errors found:

----:[1]^Warning: unescaped & which should be written as
&amp;.
----:[1]^Hint: this & character does not begin a named
entity.

If the browser displays "&" OK, why code "&amp;"?

----:[20]^Warning: tag <script> missing required
attribute "type".
----:[20]^Hint: use "type" attribute with "language"
attribute.

Every browser known to man defaults to JavaScript. What's
wrong with taking the default?

----:[25]^Error: missing </font> end tag before <center> tag.
----:[25]^Hint: <center> element NOT allowed in
<font>...</font> element.

I'd have to see the context.

----:[115]^Warning: <nobr> is NOT approved by W3C.
----:[115]^Note: <nobr> is NOT supported by HTML 4.0
standard..

This is a "note" that FP writes for itself. Browsers
ignore it. So?

and many more. These are coding concerns that should not
be any business of a Wysiwyg editor user like myself.

Then why are you concerning yourself?

Is FP incompetant?
No.

Should I be using it?

Yes. (What did you expect on this newsgroup?)

Is HTML Toolbox off the rails?

Maybe. The question is, would your site be any better if
this tool gave it a clean bill of health?

Excruciating compliance with W3C standards is no
guarantee of browser compatibility. The browsers aren't
W3C-compliant.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*========----------
|\=========------------
|| Microsoft Office FrontPage 2003 Inside Out
|| Microsoft FrontPage Version 2002 Inside Out
|| Web Database Development Step by Step .NET Edition
|| Troubleshooting Microsoft FrontPage 2002
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/=========------------
*========----------