edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] update on dyndns
Date: Sun, 18 Feb 2018 19:58:28 -0800 (PST)	[thread overview]
Message-ID: <alpine.LRH.2.03.1802181946300.29347@carhart.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1802181640190.29347@carhart.net>

Actually, the rectangles error happens later on, so I don't think it is 
related to this particular unresponsive button.  Though it is still 
probably useful overall to supply the rectangles thing later.
But there is a bad JSON error in mmapi.js which happens adjacent to the 
request for "notice", which brings back and processes the div that contains these 
buttons.  I bet that the code that is supposed to imbue these buttons does 
not complete because of the JSON problem.  I'm in mmapi a little, and I 
think it has to do with getting and setting cookies.  "Storage" is 
mentioned, but it does not appear to be hitting our localStorage.  The 
functions are "get" and "set", which is not what localStorage uses.

The bad JSON seems to be a name with no value, like {"v":}

  On Sun, 18 Feb 2018, Kevin Carhart wrote:

> Thank you for working on them!  I noticed that you wrote a searchscripts(). 
> That's useful.  I was doing the same thing recently, crudely with 
> blah.split("mystring").length
> But that is an example of where long expressions in jdb, with a varying bit 
> in the middle of a long static bit, is annoying to continually assemble over 
> and over, so searchscripts is easier, and easy to memorize.
> And static analysis is one way of tackling errors in event code, where we 
> don't have a filename or line number reported, right?
> I'm also replying here to Chuck's report about dyndns.  Thanks for raising 
> this, Chuck.
> Well, I noticed this when I run dyndns.com with db3:
> TypeError: undefined not callable (property 'getClientRects' of [object 
> Object])
> failure on 0xf63938.onload()
> execution complete
> I'm going to investigate if we can satisfy this with some stubs.  Maybe it 
> will be similar to our set of stubs for Canvas.  There's a related function, 
> getBoundingClientRect.  Both of these things had runtime errors in quite a 
> few sites in my top sites experiment yesterday. So by fixing it for dyndns we 
> should also fix it for some other situations at the same time.
> https://developer.mozilla.org/en-US/docs/Web/API/Element/getClientRects
> https://developer.mozilla.org/en-US/docs/Web/API/Element/getBoundingClientRect
> Kevin
> _______________________________________________
> Edbrowse-dev mailing list
> Edbrowse-dev@lists.the-brannons.com
> http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev

Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists

      reply	other threads:[~2018-02-19  3:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-15 11:56 [Edbrowse-dev] version Karl Dahlke
2018-02-15 18:48 ` Adam Thompson
2018-02-15 21:04   ` Karl Dahlke
2018-02-16 19:11     ` Adam Thompson
2018-02-18  2:19   ` Karl Dahlke
2018-02-18  2:42     ` Kevin Carhart
2018-02-18  3:03       ` Karl Dahlke
2018-02-18  3:39         ` Kevin Carhart
2018-02-18  7:43           ` Karl Dahlke
2018-02-18  8:17             ` Dominique Martinet
2018-02-18  8:47               ` Dominique Martinet
2018-02-18  8:30             ` Kevin Carhart
2018-02-18  7:45         ` Kevin Carhart
2018-02-18  8:55           ` Karl Dahlke
2018-02-18 11:29           ` Karl Dahlke
2018-02-18 14:08           ` Karl Dahlke
2018-02-19  1:07             ` [Edbrowse-dev] version / dyndns Kevin Carhart
2018-02-19  3:58               ` Kevin Carhart [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:

* 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.1802181946300.29347@carhart.net \
    --to=kevin@carhart.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \


* 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).