From: Adam Thompson <arthompson1990@gmail.com>
To: Kevin Carhart <kevin@carhart.net>
Cc: Karl Dahlke <eklhad@comcast.net>, Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] $ object in javascript
Date: Wed, 28 Dec 2016 11:38:05 +0000 [thread overview]
Message-ID: <20161228113805.GA12313@odin> (raw)
In-Reply-To: <alpine.LRH.2.03.1612271144060.15985@carhart.net>
[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]
On Tue, Dec 27, 2016 at 11:47:08AM -0800, Kevin Carhart wrote:
> >It depends on time zones etc, but I've certainly got time this week.
>
> Great - I am around also. Maybe let's get calibrated and this will
> supercede confusion over the time zones. Right now it's 11:30 AM in
> California.
Ok, according to the date header that's -0800 offset so it's now 11:30 (approx)
in utc, which should make it 03:30 in the morning for you?
Hmmm, any idea what time/how you'd be online to work? Any preference as to IM
clients etc?
> When I sit down to try to do something, I generally resort to fixing
> cases from the inside out. Do you think it would be good to take a set of
> tests like Acid3 and work off of that? It seems like we need an
> intermediate point which is both an implementation of the spec approach,
> but also gives you a series of specific things to say "this passed," "this
> failed." Find-and-fix has problems because it's just one thing after the
> next, forever, with no way of knowing if you have ten or a hundred
> remaining. Going to the W3 consortium and getting the spec document has
> problems because it is hard to know where to begin or how to translate what
> you're reading into an attainable task.
Agreed, I like the set of tests method personally, particularly seeing as how
many devs seem to take a "I'll use it like this because it works" approach to the spec which means that one could only end up implementing a partial "fix"
and miss some important use-cases.
I'm going to take a look at acid3 I think and see what I can find.
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-12-28 11:38 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
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 ` Adam Thompson [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=20161228113805.GA12313@odin \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
--cc=kevin@carhart.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).