Code: Select all
Illegal AddressMatcher: [xpconnect wrapped nsIPrefBranch] -- TypeError: s.split is not a function
Illegal AddressMatcher: [xpconnect wrapped nsIPrefBranch] -- TypeError: s.split is not a function
Code: Select all
Illegal AddressMatcher: [xpconnect wrapped nsIPrefBranch] -- TypeError: s.split is not a function
Illegal AddressMatcher: [xpconnect wrapped nsIPrefBranch] -- TypeError: s.split is not a function
Code: Select all
s.split is not a function AddressMatcher.js:73
AddressMatcher.prototype.parse chrome://noscript/content/AddressMatcher.js:73:22
AddressMatcher chrome://noscript/content/AddressMatcher.js:3:13
AddressMatcher.create chrome://noscript/content/AddressMatcher.js:6:15
DoNotTrack.observe chrome://noscript/content/DoNotTrack.js:21:22
DoNotTrack.init chrome://noscript/content/DoNotTrack.js:9:7
ABE.init chrome://noscript/content/ABE.js:30:5
<anonymous> chrome://noscript/content/Main.js:105:3
ns.onBeforeLoad chrome://noscript/content/Main.js:3540:11
ns._onWindowCreatedReal chrome://noscript/content/Main.js:3831:5
ns.observe chrome://noscript/content/Main.js:132:9
bumpbarbaz wrote:Is it significant?
Sorry for the late answer.barbaz wrote:Giorgio, do you need any further information from me to assess this?
They are set to default.Giorgio Maone wrote:Are they initialized and, if they do, what do they look like in your profile?
Originally reported on SeaMonkey '2.49.2pre', but I now use Waterfox 56.0.1 and still see these messages. I can confirm this still happens in SeaMonkey with NoScript 5.1.8.3rc1.Giorgio Maone wrote:What browser version are we talking about?
Next version is now out, and this is still happening.Giorgio Maone wrote:I'm putting a work-around in place for next version, but I believe is not worth issuing a coordinated update until there's some beefier change (i.e. security-related) affecting 5.x.
off-topic: I think the culprit might have been a non-default value of about:config > browser.cache.use_new_backend . Reset it to default, started with -purgecaches again, and the problem seems to have subsided. Hopefully.barbaz wrote:(And again, I needed to restart the browser with -purgecaches to get the fix to apply. I will have to investigate this more.)