From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] acid3 log!
Date: Tue, 15 Aug 2017 16:04:35 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1708151551520.10375@carhart.net> (raw)
In-Reply-To: <20170715184401.eklhad@comcast.net>
Hi Karl
Are you kidding, we just got iframe support thanks to you and several
awesome people! We were batting 23 for 100 before, and now I think a good
10-20 of these tests are sure to be easy. Each one is a nugget - they
can be read and understood. Most are no longer than the code for test
zero that I emailed to the list. That's a lot easier to work with than a
brick of minified crud.
Also, check out how many of those diagnostic messages are phrased alike:
Test 54 failed: cannot read property 'getAttribute' of undefined
Test 55 failed: cannot read property 'appendChild' of undefined
Test 56 failed: cannot read property 'appendChild' of undefined
If that is not three instances of the same issue, I will eat my hat.
It's because of iframe support that I am back in the acid3 file in the
first place. I'm sorry if sending 100 status messages all at once is
overwhelming or got you down.
Call me optimistic but I think we're doing great!
On Tue, 15 Aug 2017, Karl Dahlke wrote:
> Looks like we're batting 0 for 100.
> If I wasn't horribly depressed about the rest of my life, then this would bother me.
>
> Karl Dahlke
> _______________________________________________
> Edbrowse-dev mailing list
> Edbrowse-dev@lists.the-brannons.com
> http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
>
--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists
next prev parent reply other threads:[~2017-08-15 23:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 19:46 Kevin Carhart
2017-08-15 22:44 ` Karl Dahlke
2017-08-15 23:04 ` Kevin Carhart [this message]
2017-08-15 23:38 ` Karl Dahlke
2017-08-16 0:18 ` [Edbrowse-dev] script in tree of document.written elements? Kevin Carhart
2017-08-16 2:53 ` Karl Dahlke
2017-08-16 3:29 ` Kevin Carhart
2017-08-16 3:32 ` 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.1708151551520.10375@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).