From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] $ object in javascript
Date: Mon, 26 Dec 2016 20:59:17 -0800 [thread overview]
Message-ID: <87y3z2x90a.fsf@the-brannons.com> (raw)
In-Reply-To: <alpine.LRH.2.03.1612262007380.1948@carhart.net> (Kevin Carhart's message of "Mon, 26 Dec 2016 20:17:00 -0800 (PST)")
Kevin Carhart <kevin@carhart.net> writes:
> 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.
The Acid3 test is a web test page from the Web Standards Project that checks
a web browser's compliance with elements of various web standards,
particularly the Document Object Model (DOM) and JavaScript.
https://en.wikipedia.org/Acid3
http://acid3.acidtests.org
I think someone may have been trying to run edbrowse against this at one
time, and it's how we got support for data: URIs.
I'll be honest, I am starting to find this project very
overwhelming on an intellectual level.
I don't know how long I can keep up.
And the security implications of AJAX scare the crap out of me.
We're making web requests at the behest of code sent to us by total
strangers, using our credentials?
Sounds like a real Pandora's Box.
But I'll keep up as much as I can.
And what are the implications of doing that XHR stuff in startwindow.js,
rather than native C? If you need it ported from JS to C, I can
certainly do that, as I have enough familiarity with both languages.
-- Chris
next prev parent reply other threads:[~2016-12-27 4:59 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 [this message]
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=87y3z2x90a.fsf@the-brannons.com \
--to=chris@the-brannons.com \
--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).