edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] DOM
Date: Wed, 26 Feb 2014 17:22:48 +0000	[thread overview]
Message-ID: <20140226172248.GF6911@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20140126080634.eklhad@comcast.net>

[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]

On Wed, Feb 26, 2014 at 08:06:34AM -0500, Karl Dahlke wrote:
> It is a bit intimidating how much dom work there is yet to do,
> perhaps not just from the basic model but also from all the plugins.
> Audio and video objects with properties etc.
> When we move forward on this we'll probably have to
> simulate somebody's dom in particular.
> I see so much javascript that looks ad your navigator to figure out
> who you are, then makes calls based on those objects.
> So far everything I've done is universal and vanilla,
> but as we move forward we have to make a conscious decision to look like
> chrome or explorer or firefox or whatever.
> It's going to be a lot of tedious work.
> Of course there is also some universal stuff yet to implement as well.
> Like the createElement appendchild etc, which are pivotal
> for the future designs that I describe at the bottom of the README file.

Yeah. As we're currently using spidermonkey it makes sense to me to implement 
our version of the firefox DOM since this'll also mean we get
engine-appropriate js if there are any spidermonkey-specific work-arounds or
optimisations used by websites independant of the DOM.

As you say though, it'll be a *lot* of work to get right.

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

      reply	other threads:[~2014-02-26 17:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 13:06 Karl Dahlke
2014-02-26 17:22 ` 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=20140226172248.GF6911@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --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).