edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] questions about new finds
Date: Sun, 26 Jun 2016 23:39:49 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LRH.2.03.1606262311350.11865@carhart.net> (raw)
In-Reply-To: <20160523124137.eklhad@comcast.net>



Thanks for the notes on my new finds.  I checked up on a couple of these.

> (1) Do you mean <modernizer> in the html text or createElement("modernizer")?
> Those are radically different issues.
> The first is up to tidy, and out of our hands.

Aha,so it actually is createElement.  The Amazon homepage says things 
like:
...r.createElement("video")....
and
...r.createElement("canvas")...
and then from tagFromJavaVar2, edbrowse can't find those strings in 
availableTags, and then reports:
cannot create tag node video
cannot create tag node canvas

And on item 3, about the setTimeout and badarg:

> Hint: jseng_moz.cpp line 2030, the 2 forces exactly 2 args.
> I think. You might have to change it to 0 for vararg then check
> arg counts down the line.

Aha, I wonder if that was the missing link when I was getting crashes. 
Because it now didn't adhere to the spec.  That could be it!

Kevin

  reply	other threads:[~2016-06-27  6:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23 11:22 Kevin Carhart
2016-06-23 16:41 ` Karl Dahlke
2016-06-27  6:39   ` Kevin Carhart [this message]
2016-07-02 16:48     ` Adam Thompson
2016-07-02 17:29       ` Karl Dahlke
2016-07-03  9:54         ` Adam Thompson
2016-07-02 22:11       ` Kevin Carhart
2016-07-03 11:12         ` 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=alpine.LRH.2.03.1606262311350.11865@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).