edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Kevin Carhart <kevin@carhart.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] what is dispatchEvent and is it needed?
Date: Sun, 10 Dec 2017 00:28:55 -0800 (PST)	[thread overview]
Message-ID: <alpine.LRH.2.03.1712100021550.16897@carhart.net> (raw)
In-Reply-To: <20171110014820.eklhad@comcast.net>

On Sun, 10 Dec 2017, Karl Dahlke wrote:

>> dispatchEvent(button,"click")
>
> At first glance this seems silly, as one can call button.onclick() to run that function,

Yes.. there must be some reason.  Well, it's parameterized, right?
Maybe easier to use with something like

for each element in (a b c d)
for each event in (click blah blah2 blah3)

I dunno.


  reply	other threads:[~2017-12-10  8:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 15:48 [Edbrowse-dev] Problem installing git version on debian sid Chuck Hallenbeck
2017-12-04 18:19 ` Geoff McLane
2017-12-04 19:48   ` Chuck Hallenbeck
2017-12-04 20:23     ` Geoff McLane
2017-12-04 23:42       ` Kevin Carhart
2017-12-05  0:47         ` Chuck Hallenbeck
2017-12-05 14:58           ` Chris Brannon
2017-12-05 16:36             ` Chuck Hallenbeck
2017-12-05 16:54               ` Karl Dahlke
2017-12-05 17:26                 ` Chuck Hallenbeck
2017-12-05 18:57                   ` Geoff McLane
2017-12-05 20:03                     ` Chuck Hallenbeck
2017-12-10  6:39                 ` [Edbrowse-dev] what is dispatchEvent and is it needed? Kevin Carhart
2017-12-10  6:48                   ` Karl Dahlke
2017-12-10  8:28                     ` Kevin Carhart [this message]
2017-12-05  1:01         ` [Edbrowse-dev] Problem installing git version on debian sid Chuck Hallenbeck
2017-12-04 20:12   ` Chuck Hallenbeck
2017-12-04 20:36     ` 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=alpine.LRH.2.03.1712100021550.16897@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).