From: Chris Brannon <chris@the-brannons.com>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Issues with creating mailing lists on freelists.org
Date: Sat, 02 Jul 2016 11:56:01 -0700 [thread overview]
Message-ID: <87zipz7ttq.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20160702172650.GB13590@odin> (Adam Thompson's message of "Sat, 2 Jul 2016 17:26:50 +0000")
Adam Thompson <arthompson1990@gmail.com> writes:
> sure enough tidy's complaining about a missing </form> on line 61
> (although I can't see another form earlier in the source) and the node
> representation shows
> that the form ends at the checkbox to agree to the terms (which is
> before the fields to create the list).
I think it may have something to do with divs not being closed in the
right order, but I'm not completely sure.
Unrelated, after groveling around in the HTML source, I found a couple
gems like this:
<h3>Create a New Mailing List: Step 1</h2>
-- Chris
next prev parent reply other threads:[~2016-07-02 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-02 17:26 Adam Thompson
2016-07-02 18:56 ` Chris Brannon [this message]
2016-07-03 9:59 ` Adam Thompson
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=87zipz7ttq.fsf@mushroom.localdomain \
--to=chris@the-brannons.com \
--cc=edbrowse-dev@lists.the-brannons.com \
/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;
as well as URLs for NNTP newsgroup(s).