9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9front@googlegroups.com
Subject: Re: mothra ignores <br>, funky text entry
Date: Sat, 07 Jul 2012 12:12:58 +0100	[thread overview]
Message-ID: <1341659578.30781.140661098969033.19203867@webmail.messagingengine.com> (raw)
In-Reply-To: <2f037c006419e1d8bd59b7c496b85524@sp.inri.net>

On Fri, Jul 6, 2012, at 08:36 PM, sl@9front.org wrote:
> Have you verified that the forums in question are actually
> presenting a <br> and not something else?

Right. What it's not parsing correctly is <br/>. It also doesn't parse
<hr/> although it parses <hr> correctly. Both errors can be seen at
http://ethan.uk.to/static/brtest.html

We must deal correctly with these trailing slashes because as any fine
upstanding Web 2.0 shithead will tell you, any tag which does not have a
corresponding closing tag must have a / at the end because otherwise
html is simply too hard to parse.

Ehh, regardless of what bollocks they use to justify it, the trailing
slash seems to be required if you want to be taken seriously as a web
designer, everybody uses it.
There are some ideas so wrong that only a very intelligent person could believe in them.
-- George Orwell


  reply	other threads:[~2012-07-07 11:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-07  1:31 Ethan Grammatikidis
2012-07-07  1:36 ` sl
2012-07-07 11:12   ` Ethan Grammatikidis [this message]
2012-07-07 13:13     ` cinap_lenrek
2012-07-07 16:03       ` Ethan Grammatikidis
2012-07-07 18:08     ` sl
2012-07-08  4:15       ` Ethan Grammatikidis
2012-07-07 12:22   ` cinap_lenrek
2012-07-07 13:39 ` cinap_lenrek
2012-07-07 15:46   ` Ethan Grammatikidis
2012-07-07 17:11     ` cinap_lenrek
2012-07-07 18:09       ` sl
2012-07-07 18:10         ` sl
2012-07-07 23:31       ` Ethan Grammatikidis
2012-07-08  0:07         ` cinap_lenrek
2012-07-08  5:34           ` Ethan Grammatikidis
2012-07-08 21:00             ` Matthew Veety
2012-07-09  4:16               ` Ethan Grammatikidis
2012-07-09 15:01                 ` Julius Schmidt
2012-07-07 17:31     ` cinap_lenrek

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=1341659578.30781.140661098969033.19203867@webmail.messagingengine.com \
    --to=eekee57@fastmail.fm \
    --cc=9front@googlegroups.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).