Having spent some more time observing the interaction between URO+ and WMETB, the source of the original problem has now been identified... If WMETB starts up after URO+, it calls the uroWazeBits() function (which URO+ has already called by this point as part of its own startup procedure) to reinitialise the layer indices used by URO+. Previous to 3.20, calling this function twice wasn't an issue.Twister-UK wrote:I describe it as an "attempt" only because I don't understand why having WMETB installed is causing the issue
As of 3.20 however, uroWazeBits() also initialises the window.confirm() interceptor code, required by the "inhibit pending questions prompt" option. The way this code was written in 3.20 worked just fine provided it was called once. The JS environment provided by Firefox also coped quite nicely with the code being called multiple times, however the JS environment provided by Chrome was somewhat less tolerant of multiple calls. And by somewhat less tolerant what I actually mean is completely and utterly intolerant, to the point of throwing a hissy fit as soon as the intercepted confirm() function was called for the first time...
The fix I put in to 3.21 was simply to rewrite the interceptor code in a style which seemed to meet the general Google consensus on how this sort of code ought to be written, which conveniently allows the code to be called multiple times without ill-effect. So I think it's safe to upgrade 3.21 from being an "attempt" at a fix to being an actual fix.
Re: [Script] UROverview Plus v3.21 (20140922)