Prox affecting code of GM script on installing

[leecovuk]

Hello Sidki,

I'm sure you know, but just in case you don't and to give you a little background, Greasemonkey is a Firefox addon which inserts user javascripts into web pages. The script installation typically takes place by clicking on 'Install' on the relevant userscripts.org script page (if you are finding the script on that site) which 'fetches' the script. You are then offered an install prompt in Firefox to install the script into Greasemonkey. You then simply browse to the affected pages/site and the script should be impacting.
(Sorry if you are more than aware of all that; it may appear patronising, but I just wanted to be 100% clear seeing as you hinted not being highly familiar with Greasemonkey)


What I am getting at is, is it expected that having Prox in circuit when installing a Greasemonkey script as described above should actually impact on and change the script's code? I can understand potential conflicts once installed and acting on a web page together with Prox, but not on the installation side ... ?
Do you see what I mean? Maybe you do and I haven't seen what you're saying back (I think I do too many smile emoticons ... it appears insincere .... hmmm ...)
Yes, I can of course put Prox into bypass to install the script which avoids the problem, but I'm wondering why it is happening and if it should be.

From what I can tell, this is the only script and only line of code where I currently have/have ever had this happening, so it doesn't appear to be a big issue. I don't know if other people also have this experience, but I assume they would with this script and same FF version etc

Lee