From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Using xhtml strict or html5 for the web gui ?
Date: Wed, 12 Feb 2014 20:14:24 +0100 [thread overview]
Message-ID: <1392232464.5657.7.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <52FA6B4E.2080003@i100.no>
[-- Attachment #1: Type: text/plain, Size: 1701 bytes --]
Hi Alf,
indeed the quality of the generated HTML of the CGI scripts is a mess.
That is one of the main reasons, why we decided to ditch the webUI as it
is now and rewrite it from scratch in IPFire 3 in Python.
The new theme that comes with IPFire 2.15 (next branch) comes with the
HTML5 doctype and a lot of code has been improved, but I think we are
still far away from valid output.
I would welcome any patches that fix the generated HTML, but I don't
think that someone should put too much effort in it and rewrite bigger
chunks of code.
-Michael
On Tue, 2014-02-11 at 19:26 +0100, Alf Høgemark wrote:
> Hi
>
> I was trying to validate the html pages of the web GUI of Ipfire.
> Although having pages that passes a validator is not absolutely
> requried, I think it makes styling easier, and it makes
> good sense to make sure table cells and rows are properly closed etc
> etc. It is a kind of indicator of code quality.
>
> I then noticed that the ipfire web GUI is using the doctype for xhtml
> strict.
>
> But the actual html itself seems to be a bit old style, with lots of
> align, valign attributes on tags, which will not validate
> as xhtml, even if all the tags are properly closed.
>
> Have you considered going for "html5" doctype ?
> Using html5, I think it would require a lot less cleanup to make the
> pages validate.
>
> And when a page validates, it makes it easier to test the page using a
> validator after you make code changes, to make sure it still validates.
>
>
> Regards
> Alf Høgemark
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
prev parent reply other threads:[~2014-02-12 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 18:26 Alf Høgemark
2014-02-12 19:14 ` Michael Tremer [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1392232464.5657.7.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox