From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] suggested additions
Date: Mon, 4 Sep 2017 18:32:15 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1709041816420.28685@carhart.net> (raw)
In-Reply-To: <20170804110647.eklhad@comcast.net>
Good question. I think it's both. It's because of the acid tests that we
got into CSS, but at the same time, getting drescher and nasa has been
based on find & fix. I think both things amount to a large catalog of
scenario-like puzzles that can be picked up when we have time to work, and
which have all been vetted or ratified that they will help our coverage.
It's all the same DOM. I would consider toggling back and forth. If we
are stuck with the one, go implement something raised by the other.
On Mon, 4 Sep 2017, Karl Dahlke wrote:
> Curious. Would the acid tests uncover these 7 things?
> The jury is still out on whether we should follow the acid tests, or find&fix, or both.
>
> Karl Dahlke
> _______________________________________________
next prev parent reply other threads:[~2017-09-05 1:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 2:38 Kevin Carhart
2017-09-04 14:12 ` Karl Dahlke
2017-09-05 1:16 ` Kevin Carhart
2017-09-05 2:27 ` Karl Dahlke
2017-09-04 15:06 ` Karl Dahlke
2017-09-05 1:32 ` Kevin Carhart [this message]
2017-09-04 17:10 ` Karl Dahlke
2017-09-05 2:15 ` [Edbrowse-dev] contentWindow Kevin Carhart
[not found] ` <20170804223729.eklhad@comcast.net>
2017-09-05 2:58 ` Kevin Carhart
[not found] ` <20170804232757.eklhad@comcast.net>
2017-09-05 3:57 ` Kevin Carhart
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.1709041816420.28685@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).