Further correctionGuest wrote: With noscript_security_suite-2.6.8.27 (offered on May 21, 2014)

noscript_security_suite-2.6.8.27 (offered on June 3, 2014)
Further correctionGuest wrote: With noscript_security_suite-2.6.8.27 (offered on May 21, 2014)
Answer to question one:barbaz wrote:Now someone please check those rc versions and post the last working rc? (I'm thinking that 2.6.8.27rc1 will work, but not 100% sure. The big question is whether the issue is introduced in rc2 or rc3.)
Also can someone please run a traffic monitor (such as HTTPFox) on OneDrive both with a working NoScript and a non-working NoScript, and if the two logs are different please post them here?
Answer to question two:https://addons.mozilla.org/de/firefox/a ... .6.8.27rc2
Veröffentlicht am May 31, 2014 533.4 kB Funktioniert mit Firefox 3.0.9 und neuer, Mobile 1.0 - 2.0a1pre, SeaMonkey 2.0 und neuer
v 2.6.8.27rc2
=========================================================================
+ [Surrogate] External script surrogates are now triggered whenever a matching script fails to load, no matter the reason, e.g. NoScript permissions, ABE, ABP or RequestPolicy ...
I can understand that, feel free to dummy out any parts of the URLs you're afraid of posting.Guest wrote:Answer to question two:
Sorry, I'm afraid of posting a HTTPFox-log - I saw HTTPFox logging my live.com-identity and I don't know if it logs my password too in any way (maybe encrypted, I'm doubtful) - feeling too risky![]()
barbaz wrote:Giorgio is the only developer of NoScript and I have no idea when he can get to this. atm he's pretty busy trying to design & implement WebExtensions API...
You're welcome.JLJ wrote:GOLD, JERRY, GOLD! Whoever you are, sir or madam, or the cat, I thank you again.![]()
This. Almost every NoScript rc fixes at least one bug, and many have compatibility fixes for Gecko updates... your life will be a lot easier keeping track of just one workaround, than dealing with myriad old bugs with no support.JLJ wrote:So what's best if you're lazy like me: leave that pref set to false until a fix is implemented to NS
Hopefully, a fix is comingHello,
I am able to repro this issue. I've filed a bug against our web devs to look into this.
Thanks for bringing this issue to our attention!
Carl Hirschman
and this:barbaz wrote:Thanks for confirming.
I can understand that, feel free to dummy out any parts of the URLs you're afraid of posting.Guest wrote:Answer to question two:
Sorry, I'm afraid of posting a HTTPFox-log - I saw HTTPFox logging my live.com-identity and I don't know if it logs my password too in any way (maybe encrypted, I'm doubtful) - feeling too risky![]()
Or one of the registered users here can PM the logs to Giorgio and/or a Mod (me, GµårÐïåñ, therube, or Thrawn).
I decided to register for an account on InformAction Forums (former guest mutated to Zitrus nowbarbaz wrote:@sandrock: Thank you for bringing this to Microsoft's attention! I like that reply![]()
Although it is still a NoScript bug, so if they get to this before Giorgio, explanations as to what about the site revealed this bug in NoScript - and how they work around it - would be very helpful and much appreciated.
Yep. Something changed in OneDrive's code at some point. Using the date of first report of this bug, I'm sure thay can find the commits that did it. Maybe they are using a JS "hack" that NoScript does not like. Removing/fixing this hack on their side will fix the bug AND help debug NoScript.barbaz wrote:Although it is still a NoScript bug, so if they get to this before Giorgio, explanations as to what about the site revealed this bug in NoScript - and how they work around it - would be very helpful and much appreciated.
People at MS are humans too. If you write a nice email, with constructive info plus debug info then stuff happens (hopefully).victor50 wrote:@sandrock. How extraordinary! I have never succeeded in getting M$ to admit that some of the many "anomalies" is their fault and they should do something about it.