edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Chris Brannon <chris@the-brannons.com>
Cc: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Issues with creating mailing lists on freelists.org
Date: Sun, 3 Jul 2016 09:59:53 +0000	[thread overview]
Message-ID: <20160703095952.GB19967@odin> (raw)
In-Reply-To: <87zipz7ttq.fsf@mushroom.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]

On Sat, Jul 02, 2016 at 11:56:01AM -0700, Chris Brannon wrote:
> 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>

Ouch! Missed that one... I did however notice some exciting script src attributes without url schemas, e.g.
<script src="//cdnjs.cloudflare.com/ajax/libs/jquery/2.1.3/jquery.min.js"></script>

That's at the bottom of the page source and doesn't even have a type or language!  I guess the expectation is that these are sourced then... ran... without a
type?  Or perhaps this never works right and the functionality is never used?

Cheers,
Adam.

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2016-07-03 10:00 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
2016-07-03  9:59   ` Adam Thompson [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=20160703095952.GB19967@odin \
    --to=arthompson1990@gmail.com \
    --cc=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).