From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [edbrowse-dev] window.location.search and String.search
Date: Sun, 02 Jun 2019 08:50:56 -0400 [thread overview]
Message-ID: <20190502085056.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1906012354210.172820@carhart.net>
Ok this is fun, isn't it?
It took me a while even to replicate your situation.
The js you refer to comes from a domain doubleclick.net, which I supressed long ago.
It's adds, so I don't care about it.
nojs = doubleclick.net
I commented out the whole nojs block so I could run all the javascript.
I still didn't get your file, at all.
I realized I routinely spoof the internet by pretending I am internet explorere.
(If I don't do this there are no h3 headins on google search)
The website doesn't even go down this path for IE.
So I set ua0 so I'm back to edbrowse.
Now, finally, I fetch the same scripts as you and see the same error.
snapshot()
Now I can replicated here on my machine and put in breakpoints etc.
eval($bp) as you suggest.
Yes I'm calling search on a url object. Oops.
It's not window location as you thought.
a === window.location
false
Not document.location either.
It's document.URL.
A little more internet research, and document.URL is suppose to be a string, not a URL, its name notwithstanding.
So I was right to think we were barking up the wrong tree, don't mess with overlaid search functions,
what is passed in shouldn't be a URL at all.
It's a one line fix in ebjs.c line 795.
Now the error goes away.
But no worries, I'm sure you'll find plenty more.
Karl Dahlke
prev parent reply other threads:[~2019-06-02 12:50 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
2019-06-02 12:50 ` Karl Dahlke [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:
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=20190502085056.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).