edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] jquery v2 and an interesting seg fault
Date: Fri, 04 Dec 2015 17:11:23 -0500	[thread overview]
Message-ID: <20151104171123.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1512041248370.26352@carhart.net>

> document.nodeType = 9;
> document.implementation = {};
> document.location = {};

The first two are fine and (theoretically) harmless.
The third is not a good idea, as document.location is set at run time
and is a URL object equal to the url of the page you are browsing.
My latest push adds the first two lines.

The seg fault I cannot reproduce, even with these lines added,
at least not on the fanfiction home page.
Perhaps you traveled down the path a ways and read a book or some such.
Still I get a glimpse of the problem from your backtrace.
Somehow and for some reason js is trying to remove a node
from beneath another node that has no children.
Obviously this should never happen, but it does, or does for you,
so my push allows for that.

Karl Dahlke

  reply	other threads:[~2015-12-04 22:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 18:11 [Edbrowse-dev] 3.6.0? Chris Brannon
2015-12-02 20:01 ` Karl Dahlke
2015-12-03  1:59   ` Kevin Carhart
2015-12-03  2:42     ` Chris Brannon
2015-12-03  3:13       ` Kevin Carhart
2015-12-03  4:52         ` Karl Dahlke
2015-12-04  1:05           ` Kevin Carhart
2015-12-04 14:24             ` Karl Dahlke
2015-12-04 21:10               ` [Edbrowse-dev] jquery v2 and an interesting seg fault Kevin Carhart
2015-12-04 22:11                 ` Karl Dahlke [this message]
2015-12-04 22:28                   ` Kevin Carhart
2015-12-05  9:12                     ` [Edbrowse-dev] javascript() in timer side effects Kevin Carhart
2015-12-05 14:39                       ` Karl Dahlke
2015-12-06  0:19                         ` Kevin Carhart
2015-12-06  0:26                           ` Karl Dahlke
2015-12-06  2:48                             ` Kevin Carhart
2015-12-06 11:38                               ` 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=20151104171123.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --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).