Now that I've had enough time to cite references and document Greasemonkey a bit better (which is is important to the explanations I have here), I can get back for a while to u.s.o. <b>@gimmic</b> No prob and thanx... yes it is looking more like Mozilla is the culprit, but for reasons unknown. I still don't know whether to file a bug report with them or not... I'll search through their forums and docs soon to see if they have an official standing. What I didn't say in my response above is about YOUR NAMESPACE... any user script namespace is in what they call in the Sandbox, and of course it is not privileged enough either to send the Referer atom (at least on the machines I have tested). Currently the only way that I have successfully sent a Referer atom is to use the unsafeWindow object, which I'm not thrilled with... I usually block all Referer atoms period, but I know some sites are annoying enough to require them. In that case I usually forge them and apparently that's not possible in chrome or the sandbox using the XMLHttpRequest (XHR for short) method, which presents a very large problem. <b>@Yansky</b> That's more or less the solution that I've come to as well, but with <b>Descriptors</b> comment about the extra r shouldn't be in there and depending on what method of the native DOM XHR you want to call will determine which method you use. I make typos all the time, so no big deal... but I'm doing my best to be as accurate as I can here. Unfortunately a host site will see what you do when you utilize unsafeWindow *le sigh* <b>@Descriptor</b> Thankx for catching that... I've been WAY busy with GM docs <p>Now that I've had enough time to cite references and document Greasemonkey a bit better (which is is important to the explanations I have here), I can get back for a while to u.s.o.</p> <p><b>@gimmic</b> <br />No prob and thanx... yes it is looking more like Mozilla is the culprit, but for reasons unknown. I still don't know whether to file a bug report with them or not... I'll search through their forums and docs soon to see if they have an official standing.</p> <p>What I didn't say in my response above is about YOUR NAMESPACE... any user script namespace is in what they call in the Sandbox, and of course it is not privileged enough either to send the Referer atom (at least on the machines I have tested). Currently the only way that I have successfully sent a Referer atom is to use the unsafeWindow object, which I'm not thrilled with... I usually block all Referer atoms period, but I know some sites are annoying enough to require them. In that case I usually forge them and apparently that's not possible in chrome or the sandbox using the XMLHttpRequest (XHR for short) method, which presents a very large problem.</p> <p><b>@Yansky</b> <br />That's more or less the solution that I've come to as well, but with <b>Descriptors</b> comment about the extra r shouldn't be in there and depending on what method of the native DOM XHR you want to call will determine which method you use. I make typos all the time, so no big deal... but I'm doing my best to be as accurate as I can here. Unfortunately a host site will see what you do when you utilize unsafeWindow *le sigh*</p> <p><b>@Descriptor</b> <br />Thankx for catching that... I've been WAY busy with GM docs</p> 2007-12-11T10:20:01Z 1 Forum 5402 1302 2007-12-11T10:40:00Z 37004