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] Amazon can of worms
Date: Tue, 22 Apr 2014 15:17:44 +0100	[thread overview]
Message-ID: <20140422141744.GD23557@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20140321085354.eklhad@comcast.net>

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

On Mon, Apr 21, 2014 at 08:53:54AM +0000, Karl Dahlke wrote:
> Adam writes:
> > I think in this case it is expected that the script element is placed (and thus
> > executed) in the DOM just as it would be if it was done in the html.
> 
> Perhaps, but in this case, Amazon.com, the script element is added
> to the head section, which is about 1000 lines in the past.
> It is not placed in some tag in the future.
> Since we don't have time travle,
> the best we can do is to execute the script right now.
> I guess, it's all rather merky.

Yeah, that's seriously weird. I fail to see how this is expected to work,
since even if the DOM is created first then script elements executed in the
order they appear, the addition of an extra script element in the head section
after that part of the DOM has had all its script elements executed would be a bit pointless.
The only way this could possibly work without invoking the script out of place
would be to re-check the DOM on each update executing new script elements.
This just sounds like a bit of a recipe for disaster.

Before doing anything with this I'd be tempted to look at how other browsers
handle this case, assuming it's not just a bug in amazon's page which no one
has noticed yet.

Cheers,
Adam.

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

  reply	other threads:[~2014-04-22 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-21  8:53 Karl Dahlke
2014-04-22 14:17 ` Adam Thompson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-04-21  0:48 Karl Dahlke
2014-04-21 11:17 ` 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=20140422141744.GD23557@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).