From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] $ object in javascript
Date: Mon, 26 Dec 2016 20:17:00 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1612262007380.1948@carhart.net> (raw)
In-Reply-To: <20161126224954.eklhad@comcast.net>
Hi Karl
Okay, sounds good. Pretty much like we have done. When I find out if
Adam is around, I will offer to stay up so that we overlap. I never go to
bed before around 1 Pacific anyhow.
Do you remember at the beginning of the jquery development when we were
working with a series of tests at the top of their "supports" function?
In writing out that long message, it makes me think that I wish there was
something similar, a grand test suite for DOM implementations. Maybe
there is. I have these two poles - I
can go to W3 and read the spec but it's very detached from scenarios. So
then I can go
work on find and fix, but this is just scenarios and doesn't let you know
what's ahead or how close you are to finishing. We need a series of
anecdotal exercises designed by people, similar to our jsrt only published
by the W3 consortium or something, so that you have a definitive way of
knowing when you've passed your tests or which ones failed. Maybe this
exists. I'm sure at Firefox and Chrome they run their browser through a
suite like that.
On Mon, 26 Dec 2016, Karl Dahlke wrote:
>> How do you think we ought to work?
>
> Well you could just send email to me, and Chris, and anyone else interested,
> that's mostly how we have trudged forward in the past.
> Or there's a speakup IM channel that we chat on but we would all have to be awake and online at the same time.
> Sometimes that has worked well for me and Chris, or me and Tyler, but that's just cause we don't sleep much, or regular, I guess.
> So I don't know, whatever you like.
>
> Karl Dahlke
>
--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists
next prev parent reply other threads:[~2016-12-27 4:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 16:03 Karl Dahlke
2016-11-29 16:24 ` Chris Brannon
2016-11-30 0:47 ` Kevin Carhart
2016-11-30 7:30 ` Karl Dahlke
2016-11-30 7:43 ` Tyler Spivey
2016-11-30 7:54 ` Karl Dahlke
2016-12-01 0:04 ` Kevin Carhart
2016-12-01 1:17 ` Karl Dahlke
2016-12-25 13:06 ` Adam Thompson
2016-12-26 14:52 ` Karl Dahlke
2016-12-27 3:04 ` Kevin Carhart
2016-12-27 3:49 ` Karl Dahlke
2016-12-27 4:17 ` Kevin Carhart [this message]
2016-12-27 4:38 ` Karl Dahlke
2016-12-27 18:37 ` Adam Thompson
2016-12-27 4:59 ` Chris Brannon
2016-12-27 6:53 ` Kevin Carhart
2016-12-27 15:21 ` Chris Brannon
2016-12-27 20:13 ` Kevin Carhart
2016-12-27 13:26 ` Karl Dahlke
2016-12-27 15:47 ` Chris Brannon
2016-12-27 18:48 ` Adam Thompson
2016-12-27 20:23 ` Chris Brannon
2016-12-28 11:42 ` [Edbrowse-dev] Edbrowse in NetBSD Adam Thompson
2016-12-28 11:50 ` Chris Brannon
2016-12-28 12:15 ` Adam Thompson
2016-12-27 19:11 ` [Edbrowse-dev] $ object in javascript Adam Thompson
2016-12-27 19:47 ` Kevin Carhart
2016-12-27 20:11 ` Karl Dahlke
2016-12-27 20:45 ` [Edbrowse-dev] nextSibling and previousSibling Kevin Carhart
2016-12-27 21:14 ` Chris Brannon
2016-12-28 11:38 ` [Edbrowse-dev] $ object in javascript Adam Thompson
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.1612262007380.1948@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).