From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] return value from removeChild
Date: Thu, 22 Feb 2018 22:17:59 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1802222217290.18804@carhart.net> (raw)
In-Reply-To: <20180123010546.eklhad@comcast.net>
rad!
thank you!
On Fri, 23 Feb 2018, Karl Dahlke wrote:
>> our removeChild function should return the removed node to javascript,
>
> No need for wrappers etc, just a 2 line change in the native method.
> I use to specifically pop the argument and return 0, so don't pop it and return 1.
>
> Karl Dahlke
> _______________________________________________
> Edbrowse-dev mailing list
> Edbrowse-dev@lists.the-brannons.com
> http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
>
---
prev parent reply other threads:[~2018-02-23 6:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 18:54 [Edbrowse-dev] hover Karl Dahlke
2018-02-23 5:47 ` [Edbrowse-dev] return value from removeChild Kevin Carhart
2018-02-23 6:05 ` Karl Dahlke
2018-02-23 6:17 ` Kevin Carhart [this message]
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.1802222217290.18804@carhart.net \
--to=kevin@carhart.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/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).