Colin,

Here is the html of the form, before I press the update button:

<h1>Editing orf</h1>
<form action="/orves/1705" class="edit_orf" id="edit_orf_1705"
method="post"><div style="margin:0;padding:0"><input name="_method"
type="hidden" value="put" /></div>

  Gura_0317
  <input id="orf_current_annotation" name="orf[current_annotation]"
size="50" type="text" value="hypothetical protein" />
        <input id="orf_submit" name="commit" type="submit" value="Update" />
</form>


When I paste it into the html validator (on their web page), I get:


Validation Output: 2 Errors

   1. Error Line 1, Column 1: no document type declaration; will parse
without validation

      <h1>Editing orf</h1>

      ✉

      The document type could not be determined, because the document
had no correct DOCTYPE declaration. The document does not look like
HTML, therefore automatic fallback could not be performed, and the
document was only checked against basic markup syntax.

      Learn how to add a doctype to your document from our FAQ, or use
the validator's Document Type option to validate your document against
a specific Document Type.
   2. Error Line 2, Column 77: document type does not allow element
"FORM" here

      …_orf" id="edit_orf_1705" method="post"><div style="margin:
0;padding:0"><input …

      ✉

      The element named above was found in a context where it is not
allowed. This could mean that you have incorrectly nested elements --
such as a "style" element in the "body" section instead of inside
"head" -- or two elements that overlap (which is not allowed).

      One common cause for this error is the use of XHTML syntax in
HTML documents. Due to HTML's rules of implicitly closed elements,
this error can create cascading effects. For instance, using XHTML's
"self-closing" tags for "meta" and "link" in the "head" section of a
HTML document may cause the parser to infer the end of the "head"
section and the beginning of the "body" section (where "link" and
"meta" are not allowed; hence the reported error).
   3. Warning Line 2, Column 158: NET-enabling start-tag requires
SHORTTAG YES

      …e="margin:0;padding:0"><input name="_method" type="hidden"
value="put" /></div>

      ✉

      The sequence <FOO /> can be interpreted in at least two
different ways, depending on the DOCTYPE of the document. For HTML
4.01 Strict, the '/' terminates the tag <FOO (with an implied '>').
However, since many browsers don't interpret it this way, even in the
presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it
completely in pure HTML documents and reserve its use solely for those
written in XHTML.
   4. Warning Line 5, Column 120: NET-enabling start-tag requires
SHORTTAG YES

      …orf[current_annotation]" size="50" type="text"
value="hypothetical protein" />

      ✉

      The sequence <FOO /> can be interpreted in at least two
different ways, depending on the DOCTYPE of the document. For HTML
4.01 Strict, the '/' terminates the tag <FOO (with an implied '>').
However, since many browsers don't interpret it this way, even in the
presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it
completely in pure HTML documents and reserve its use solely for those
written in XHTML.
   5. Warning Line 6, Column 68: NET-enabling start-tag requires
SHORTTAG YES

        <input id="orf_submit" name="commit" type="submit"
value="Update" />

      ✉

      The sequence <FOO /> can be interpreted in at least two
different ways, depending on the DOCTYPE of the document. For HTML
4.01 Strict, the '/' terminates the tag <FOO (with an implied '>').
However, since many browsers don't interpret it this way, even in the
presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it
completely in pure HTML documents and reserve its use solely for those
written in XHTML.


-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to rubyonrails-t...@googlegroups.com.
To unsubscribe from this group, send email to 
rubyonrails-talk+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en.

Reply via email to