From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] the siblings patch
Date: Wed, 28 Dec 2016 19:31:39 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1612281926460.4769@carhart.net> (raw)
I just sent a suggested patch which will implement the DOM manipulations
nextSibling and previousSibling. Karl, you pointed out a while ago that
the siblings are computed in the course of our native insertBefore code.
But I did it in javascript so that I would have a deeper understanding
and not just be modifying your insertBefore code in more of a brittle way.
And also, nextSibling and previousSibling are merely discerning
something and there is no side effect to worry about. It doesn't change
the tree, just discerns information about it.
Kevin
reply other threads:[~2016-12-29 3:31 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.1612281926460.4769@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).