From: Kevin Carhart <kevin@carhart.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] document.head.querySelector (fwd)
Date: Fri, 22 Dec 2017 21:39:25 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1712222123220.18658@carhart.net> (raw)
Karl sez:
Well for starters, a.href = a.href; makes no sense to me.
What's the point of that?
--
It definitely appears redundant so I'm assuming that the side effects idea
is the only sensible reason for it to be there. The side effects would be
the answer to why it isn't pointless to set that.
Side note to Chuck, I'm glad you got it!
reply other threads:[~2017-12-23 5:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.LRH.2.03.1712222123220.18658@carhart.net \
--to=kevin@carhart.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).