From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: edbrowse-dev@lists.the-brannons.com
Subject: Re: [edbrowse-dev] window.location.search and String.search
Date: Sun, 2 Jun 2019 00:10:33 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1906012354210.172820@carhart.net> (raw)
In-Reply-To: <20190502024317.eklhad@comcast.net>
Oops, you're right, I should have given a file and line number!
If you
load https://www.baseball-reference.com/players/, it's in one of the
advertising js files, pubads_impl_2019052302.js at line 1854 after demin.
I don't know if it's responsible for inhibiting content from loading such
as Players, but it's the first runtime that occurs. Hooray, first piece
of find & fix that would probably not have been coherent to isolate and
work on without the breakpoint!
On Sun, 2 Jun 2019, Karl Dahlke wrote:
> I guess you would have to show me where the location.search(stuff) as a function is, because I find it as a string all over, even in the baseball site.
> cloud.js lines 42, 589, 1551, 6062, etc.
> If you stretch your mind to the limit you could imagine the getter returning a function that is string.match but it has a toString() function that is the string you want,
> so if the code coerces it to a string it will be right, but that's the only way,
> and most of the time the code doesn't coerce it to a string so it will be an object and blow up.
> So no you can't have your cake and eat it too.
> More likely there's something wrong with the parameters being passed in,
> like maybe the location object should have been coererced to string before it was passed.
> Anyways I'd have to look at it for real.
>
> Karl Dahlke
>
next prev parent reply other threads:[~2019-06-02 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-02 0:42 Kevin Carhart
2019-06-02 6:43 ` Karl Dahlke
2019-06-02 7:10 ` Kevin Carhart [this message]
2019-06-02 12:50 ` Karl Dahlke
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.DEB.2.21.1906012354210.172820@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).