spamassassin-dev December 2011 archive
Main Archive Page > Month Archives  > spamassassin-dev archives
spamassassin-dev: [Bug 4710] SA Wiki "Valid HTML 4.01 "

[Bug 4710] SA Wiki "Valid HTML 4.01 " link fails validity check

From: <bugzilla-daemon_at_nospam>
Date: Sun Dec 04 2011 - 14:57:58 GMT
To: dev@spamassassin.apache.org

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=4710

Kevin A. McGrail <kmcgrail@pccc.com> changed:

           What |Removed |Added
----------------------------------------------------------------------------
             Status|NEW |RESOLVED
         Resolution| |WONTFIX

--- Comment #2 from Kevin A. McGrail <kmcgrail@pccc.com> 2011-12-04 14:57:58 UTC ---
Spot checking further, the validity issues appear to be one image border tag on
the header logo combined with lots of little moin-moin problems.

In short, Moin-moin itself doesn't pass valid 4.01.
http://moinmo.in/HelpOnThemes, for example, has the link as of Dec/4/2011 and
fails (see below)

I also don't believe we have the ability to edit the theme where the header and
footer reside without going through infra.

As a ticket is open with MoinMoin
(http://moinmo.in/MoinMoinBugs/Invalid%20HTML%204.01?highlight=%28html%29|%284.01%29)
and it is not causing any readability issues, I'm closing this as won't fix.

MoinMoin Failure:

   1. Error Line 147, Column 63: end tag for element "LI" which is not open

      …me">Make a new Theme</a></li></ol></li></ol></div> <span class="anchor"
id="li…

      ✉

      The Validator found an end tag for the above element, but that element is
not currently open. This is often caused by a leftover end tag from an element
that was removed during editing, or by an implicitly closed element (if you
have an error related to an element being used where it is not allowed, this is
almost certainly the case). In the latter case this error will disappear as
soon as you fix the original problem.

      If this error occurred in a script section of your document, you should
probably read this FAQ entry.
   2. Error Line 147, Column 68: end tag for element "OL" which is not open

      …ake a new Theme</a></li></ol></li></ol></div> <span class="anchor"
id="line-11…

      ✉

      The Validator found an end tag for the above element, but that element is
not currently open. This is often caused by a leftover end tag from an element
that was removed during editing, or by an implicitly closed element (if you
have an error related to an element being used where it is not allowed, this is
almost certainly the case). In the latter case this error will disappear as
soon as you fix the original problem.

      If this error occurred in a script section of your document, you should
probably read this FAQ entry.
   3. Error Line 149, Column 730: there is no attribute "TYPE"

      …"anchor" id="line-18"></span><ol type="1"><li>The directory where all
the stat…

      ✉

      You have used the attribute named above in your document, but the
document type you are using does not support that attribute for this element.
This error is often caused by incorrect use of the "Strict" document type with
a document that uses frames (e.g. you must use the "Transitional" document type
to get the "target" attribute), or by using vendor proprietary extensions such
as "marginheight" (this is usually fixed by using CSS to achieve the desired
effect instead).

      This error may also result if the element itself is not supported in the
document type you are using, as an undefined element will have no supported
attributes; in this case, see the element-undefined error message for further
information.

      How to fix: check the spelling and case of the element and attribute,
(Remember XHTML is all lower-case) and/or check that they are both allowed in
the chosen document type, and/or use CSS instead of this attribute. If you
received this error when using the <embed> element to incorporate flash media
in a Web page, see the FAQ item on valid flash.

-- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.