Hello Scott.
I did get a major difference in Firefox vs. MSIE.
It appears that you may need to modify your HTML for compatibility. IK usually check all HTML output against a set of standards. This can be done at
http://validator.w3.org/When I ran your page, it reported that there were 33 errors. The detaled report identifies the lines that have the problems, the nature of the problem, and the solution to the problem.
I suspect that if you fix all 33 problems, you will have acceptable output in Firefox. And since you are using this page as a form vs. just text for reading, that the compliance needs may be more strict. Different web page developer programs use different, sometimes proprietary techniques for "forms". If you conform to these standards, you have a much better chance of always providing the user with a usable web page.
Here is an except from their site:
Quote: The Markup Validator is a free service by W3C that helps check the validity of Web documents.
Most Web documents are written using markup languages, such as HTML or XHTML. These languages are defined by technical specifications, which usually include a machine-readable formal grammar (and vocabulary). The act of checking a document against these constraints is called validation, and this is what the Markup Validator does.
Validating Web documents is an important step which can dramatically help improving and ensuring their quality, and it can save a lot of time and money (read more on why validating matters). Validation is, however, neither a full quality check, nor is it strictly equivalent to checking for conformance to the specification.
This validator can process documents written in most markup languages. Supported document types include the HTML (through HTML 4.01) and XHTML (1.0 and 1.1) family, MathML, SMIL and SVG (1.0 and 1.1, including the mobile profiles). The Markup Validator can also validate Web documents written with an SGML or XML DTD, provided they use a proper document type declaration.
Why should I validate my HTML pages?
One of the important maxims of computer programming is: Be conservative in what you produce; be liberal in what you accept.
Browsers follow the second half of this maxim by accepting Web pages and trying to display them even if they're not legal HTML. Usually this means that the browser will try to make educated guesses about what you probably meant. The problem is that different browsers (or even different versions of the same browser) will make different guesses about the same illegal construct; worse, if your HTML is really pathological, the browser could get hopelessly confused and produce a mangled mess, or even crash.
That's why you want to follow the first half of the maxim by making sure your pages are legal HTML. The best way to do that is by running your documents through one or more HTML validators.
This service does not mean you have a "valid" web page, but it does check for compliance with correct HTML syntax.
So you may need to create your HTML file, correct it using the validator tools, then modify the source that generates your html file.
I also ran your page through another validator at
http://www.htmlhelp.com/tools/validator/. ; This also listed multiple errors, but does not provide as much information for correction.
The end result of this begs the question: When Sesame "prints a form" are they using a technique that uses proper HTML syntax for web page standards? It is disturbing to see that two independant validators show so many errors. Is this because output was intended as a report only, and not for web page publishing, so a lower standard is used?
Pages: 
F000 Oh brother! (Read 4149 times)
