From: Kevin Carhart <kevin@carhart.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] var elem = document.querySelector('script[nonce]');
Date: Mon, 25 Sep 2017 23:18:14 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1709252302480.16707@carhart.net> (raw)
I found out a little more about freecarrierlookup.com. Sorry to send a
part one and part two.
It seems that freecarrierlookup wants some variations on our
querySelectorAll.. also, or maybe this discovery is actually the main
issue, and I'm mistaken about the <image onclick> question.
Because I actually noticed that when you fire i1* on the
freecarrierlookup submit, does it do nothing and not parse? It actually
does not do nothing. I think in the old days, it would just not
understand the element and give you a question mark. That is no longer
the case. It runs quite a bit, just not to complete success, to xhr and
back.
So here's what I found using demin, showscripts and ^>
It wants a document.querySelector which works like querySelectorAll but
returns just the first hit. I've known about this for a while.. there are
both.
It's complaining about line 15 of the following.
(function () {
if (!window['___grecaptcha_cfg']) {
window['___grecaptcha_cfg'] = {};
}
;
if (!window['___grecaptcha_cfg']['render']) {
window['___grecaptcha_cfg']['render'] = 'onload';
}
;
window['__google_recaptcha_client'] = true;
var po = document.createElement('script');
po.type = 'text/javascript';
po.async = true;
po.src = 'https://www.gstatic.com/recaptcha/api2/r20170919161736/recaptcha__en.js';
var elem = document.querySelector('script[nonce]');
var nonce = elem && (elem['nonce'] || elem.getAttribute('nonce'));
if (nonce) {
po.setAttribute('nonce', nonce);
}
var s = document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(po, s);
}());
next reply other threads:[~2017-09-26 6:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 6:18 Kevin Carhart [this message]
[not found] ` <20170826081450.eklhad@comcast.net>
2017-09-26 23:48 ` Kevin Carhart
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.1709252302480.16707@carhart.net \
--to=kevin@carhart.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).