Talk:GM.openInTab: Difference between revisions

From GreaseSpot Wiki
Jump to navigationJump to search
← Older edit
No edit summary
m Arantius moved page Talk:GM openInTab to Talk:GM.openInTab: Greasemonkey 4.0
 
(6 intermediate revisions by 4 users not shown)
Line 1: Line 1:
[http://www.articlesbase.com/supplements-and-vitamins-articles/my-weight-loss-experience-with-the-acai-berry-diet-1726693.html Acai Berry], [http://ezinearticles.com/?Acai-Berry---How-I-Lost-30-Pounds-in-Under-30-Days-Using-The-Acai-Berry&id=1998407 Acai Berry Detox] dietary supplement and a good source of fiber is higher than the property make this detoxification process effectively. Fibers are popular with the toxin binding, detaching the accumulation of toxic your colon and intestinal walls are easier to them out of the water body as part of fecal waste. Furthermore, detoxification is very effective, and its effect is almost completely eliminate all toxins from accumulating in your system, while helping you reduce the pressure because of the efficient use of toxic waste, weighing approximately nine fifty-five pounds, depending on the regular use of unhealthy foods.
'''@Aavindraa'''


Another great thing about [http://www.buzzle.com/articles/the-facts-and-half-truths-about-the-acai-berry-diet.html Acai Berry] is that it is a good source of amino acids that make it useful for people who want to accumulation of muscle mass and regular exercise in the gym. [http://www.acaiberryinformations.com/ Acai Berry Supplements] detox diet can help to increase metabolism and burn calories faster during exercise, in place since the incredible amount of extra pounds on your body on the road.
Shouldn't your note section example be <code>unsafeWindow.open(url)</code> instead of <code>window.open(url)</code>?
 
[[User:Marti|Marti]] 14:54, 30 December 2008 (EST)
 
Also <code>GM_openInTab</code> calls the root function of tabBrowser.addTab... so if it is truly not handling the referer, this is a Mozilla "by design" feature... not a Greasemonkey shortcoming.  I've already confirmed the tab focus issue.  Perhaps you should submit a feature enhancement [http://greasemonkey.devjavu.com/newticket ticket] to have a return value of the tab, to be able to call the <code>.focus()</code> method.
 
[[User:Marti|Marti]] 15:03, 30 December 2008 (EST)
 
 
 
@Marti:
I've tested, and <code>window.open(url)</code> works perfectly fine (with the referrer as I mentioned in the article).
About GM_openInTab: I like the background feature, but the referrer has been an issue on some sites, so I'll add a ticket.--[[User:Aavindraa|Aavindraa]] 15:12, 30 December 2008 (EST)
 
 
'''@Aavindraa'''
 
Hrmmm... just ran a test here and that's not the results I'm getting with the window object. (see http request below).  The window object is also part of the XPCNativeWrapper and the last thing I would recommend is letting a website know that GM itself is actively redirecting to another site.  Perhaps unsafeWindow is the answer you are looking for... I'll give it a shot momentarily and get back here.
 
GET / HTTP/1.1<br>
Host: www.yahoo.com<br>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.0.5) Gecko/2008120121 Firefox/3.0.5<br>
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8<br>
Accept-Language: en-us,en;q=0.5<br>
Accept-Encoding: gzip,deflate<br>
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7<br>
Keep-Alive: 300<br>
Proxy-Connection: keep-alive<br>
Cookie: *clipped*<br>
 
[[User:Marti|Marti]] 16:03, 30 December 2008 (EST)
 
Tried <code>unsafeWindow.open("http://www.yahoo.com")</code> and it produces the same results... no referer atom.
 
This appears to be a natural function of Mozilla Firefox on this platform.
 
[[User:Marti|Marti]] 16:11, 30 December 2008 (EST)
 
Results from WinXP platform...
 
GET / HTTP/1.1<br>
Host: www.yahoo.com<br>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5<br>
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8<br>
Accept-Language: en-us,en;q=0.5<br>
Accept-Encoding: gzip,deflate<br>
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7<br>
Keep-Alive: 300<br>
Connection: keep-alive<br>
Cookie: *clipped*<br>
 
Again... no referer via window or unsafeWindow... this would strongly suggest that the browser is responsible.  '''What platform are you running on?'''
 
[[User:Marti|Marti]] 16:29, 30 December 2008 (EST)
 
@Marti:
 
It's working for me on:
*Windows Vista Ultimate SP1 32-bit
*Firefox 3.0.5
 
This is my user-agent string: "Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 (.NET CLR 3.5.30729)"

Latest revision as of 15:05, 3 November 2017

@Aavindraa

Shouldn't your note section example be unsafeWindow.open(url) instead of window.open(url)?

Marti 14:54, 30 December 2008 (EST)

Also GM_openInTab calls the root function of tabBrowser.addTab... so if it is truly not handling the referer, this is a Mozilla "by design" feature... not a Greasemonkey shortcoming. I've already confirmed the tab focus issue. Perhaps you should submit a feature enhancement ticket to have a return value of the tab, to be able to call the .focus() method.

Marti 15:03, 30 December 2008 (EST)


@Marti: I've tested, and window.open(url) works perfectly fine (with the referrer as I mentioned in the article). About GM_openInTab: I like the background feature, but the referrer has been an issue on some sites, so I'll add a ticket.--Aavindraa 15:12, 30 December 2008 (EST)


@Aavindraa

Hrmmm... just ran a test here and that's not the results I'm getting with the window object. (see http request below). The window object is also part of the XPCNativeWrapper and the last thing I would recommend is letting a website know that GM itself is actively redirecting to another site. Perhaps unsafeWindow is the answer you are looking for... I'll give it a shot momentarily and get back here.

GET / HTTP/1.1
Host: www.yahoo.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.0.5) Gecko/2008120121 Firefox/3.0.5
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Proxy-Connection: keep-alive
Cookie: *clipped*

Marti 16:03, 30 December 2008 (EST)

Tried unsafeWindow.open("http://www.yahoo.com") and it produces the same results... no referer atom.

This appears to be a natural function of Mozilla Firefox on this platform.

Marti 16:11, 30 December 2008 (EST)

Results from WinXP platform...

GET / HTTP/1.1
Host: www.yahoo.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cookie: *clipped*

Again... no referer via window or unsafeWindow... this would strongly suggest that the browser is responsible. What platform are you running on?

Marti 16:29, 30 December 2008 (EST)

@Marti:

It's working for me on:

  • Windows Vista Ultimate SP1 32-bit
  • Firefox 3.0.5

This is my user-agent string: "Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 (.NET CLR 3.5.30729)"

Retrieved from "https://wiki.greasespot.net/index.php?title=Talk:GM.openInTab&oldid=7525"