From: ludo@gnu.org (Ludovic Courtès)
To: "Luis Felipe López Acevedo" <felipe.lopez@openmailbox.org>
Cc: 24981@debbugs.gnu.org, David Thompson <davet@gnu.org>
Subject: bug#24981: [Website] All pages fail the HTML validation test
Date: Wed, 23 Nov 2016 22:45:45 +0100 [thread overview]
Message-ID: <8760nd6fau.fsf@gnu.org> (raw)
In-Reply-To: <39c35b21c4edc31b948f5b29c6f321a1@openmailbox.org> ("Luis Felipe López Acevedo"'s message of "Mon, 21 Nov 2016 14:29:51 -0500")
Hello!
Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
> Steps to reproduce
> ==================
>
> 1. Go to https://validator.w3.org/
> 2. For each page in the website: validate by URI
>
>
> Unexpected behavior
> ===================
>
> All pages are marked as [Invalid]
Oops.
> Most of the errors happen because of a missing Doctype declaration. It
> seems all pages built with Haunt have this problem, while the
> packages[1] and packages issues[2] pages, generated with a different
> mechanism, do include the document type.
I see you already fixed this one the same way I’d have done it. :-)
> There are other errors not related to the document type declaration in
> the packages-related pages.[1][2] Mostly, obsolete elements or
> attributes, and missing closing tags.
This is underway too, right?
Ludo’, who likes self-fixing bugs. :-)
next prev parent reply other threads:[~2016-11-23 21:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 19:29 bug#24981: [Website] All pages fail the HTML validation test Luis Felipe López Acevedo
2016-11-23 21:45 ` Ludovic Courtès [this message]
2016-11-24 0:25 ` Luis Felipe López Acevedo
2016-11-24 9:17 ` Ludovic Courtès
2017-12-06 19:06 ` sirgazil
2017-12-07 12:21 ` Ludovic Courtès
2017-12-07 13:33 ` sirgazil
2017-12-09 15:17 ` sirgazil
2017-12-09 21:15 ` Ludovic Courtès
2019-02-06 17:08 ` sirgazil
2019-02-08 22:00 ` Ludovic Courtès
2019-02-08 14:14 ` sirgazil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760nd6fau.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=24981@debbugs.gnu.org \
--cc=davet@gnu.org \
--cc=felipe.lopez@openmailbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).