From: Karl Dahlke <eklhad@comcast.net>
To: ubuntu@geoffair.info, Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] nested anchors
Date: Thu, 01 Oct 2015 06:40:09 -0400 [thread overview]
Message-ID: <20150901064009.eklhad@comcast.net> (raw)
Here is a behavior of tidy that is not terrible,
but a bit confusing.
I ran into html like this today.
<body>
<a href=www.edbrowse.org>link1
<a href=www.edbrowse.org>link2
<a href=www.edbrowse.org>link3
</body>
Edbrowse renders this as nested hyperlinks
{link1 {link2 {link3}}}
This works, as long as you remember that a link is marked by open brace,
not close brace or the text in between.
but it really should render as
{link1} {link2} {link3}
The reason is that the second <A> tag does not close off the first.
They are all closed off at the end.
If an early anchor happens to miss its </a> tag,
then the entire document, the entire web page, could be enclosed in the hyperlink.
Karl Dahlke
next reply other threads:[~2015-10-01 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 10:40 Karl Dahlke [this message]
[not found] ` <CA+Pgot+mTy_4efnhF77Q=-XESyvHLHto3FtdEycQB_Dq2F26Dw@mail.gmail.com>
2015-10-01 16:56 ` Karl Dahlke
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=20150901064009.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=ubuntu@geoffair.info \
/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).