From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] html parser and whitespace in tag names
Date: Wed, 28 Jan 2015 07:16:54 -0500 [thread overview]
Message-ID: <20150028071654.eklhad@comcast.net> (raw)
Actually those tags are all recognized, even with the extra newlines.
I guess I had seen this syntax somewhere, and wrote the parser accordingly.
However, the <script> tag is different,
and a newline in that tag seems to derail things.
In your example,
http://hub.darcs.net
in the source html, delete lines 8 and 9, the script and /script tags,
and browse, and all the links appear.
I will have a look at the <script> tag parsing
and see if I can find the whitespace problem.
Karl Dahlke
next reply other threads:[~2015-01-28 12:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 12:16 Karl Dahlke [this message]
2015-01-28 13:08 ` Adam Thompson
-- strict thread matches above, loose matches on Subject: below --
2015-02-01 20:05 Karl Dahlke
2015-02-01 20:29 ` Chris Brannon
2015-01-29 13:24 Karl Dahlke
2015-02-01 19:56 ` Chris Brannon
2015-01-28 20:55 Karl Dahlke
2015-01-29 8:22 ` Adam Thompson
2015-01-28 15:02 Karl Dahlke
2015-01-28 17:33 ` Adam Thompson
2015-01-28 11:49 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=20150028071654.eklhad@comcast.net \
--to=eklhad@comcast.net \
--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).