[Resolved] 2.5.3rc4 affecting Refresh on Unfocused Tab

[therube]

Not certain but looks like 2.5.3rc4 is affecting Refresh on Unfocused Tab?
(IOW it does not refresh once it gains focus.)

Code: Select all

Error: NS_ERROR_XPC_NOT_ENOUGH_ARGS: Not enough arguments [nsIRefreshURI.setupRefreshURIFromHeader]
Source file: jar:file:///C:/Mozilla/therube/extensions/%7B73a6fe31-595d-460b-a920-fcc0f8843232%7D.xpi!/components/noscriptService.js
Line: 6206

Code: Select all

          docShell.setupRefreshURIFromHeader(docShell.currentURI,  toGo + ";" + uri.spec);

Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Firefox/17.0 SeaMonkey/2.14a2

[therube]

Looks like this happened starting with SeaMonkey 2.14 aka FF 17.0 (so the current Aurora, Gecko/17.0).

[therube]

Resolved (at least by) 2.5.4rc3.

[therube]

Did this break again?
(Due to another Mozilla change?)

I'm still on 2.5.1rc1, Aurora.
Haven't had time yet to diagnose ... will look more later.

Mozilla/5.0 (Windows NT 5.1; rv:18.0) Gecko/18.0 Firefox/18.0 SeaMonkey/2.15a2
Build identifier: 20121018013005

[NoScript] Blocking refresh on unfocused tab, http://forums.informaction.com/posting. ... 994#p43994

Thu Oct 18 2012 12:39:47
Error: NS_ERROR_XPC_NOT_ENOUGH_ARGS: Not enough arguments [nsIRefreshURI.setupRefreshURIFromHeader]
Source file: jar:file:///C:/Mozilla/therube/extensions/%7B73a6fe31-595d-460b-a920-fcc0f8843232%7D.xpi!/components/noscriptService.js
Line: 6204

docShell.setupRefreshURIFromHeader(docShell.currentURI, toGo + ";" + uri.spec);

[therube]

A fluke, perhaps?
Because with doing nothing further on my end, except for checking in other browsers & profiles, it is back working again.

testing123

Hey, how do you like that, *I* was testing incorrectly in my testing, so maybe it is still a problem.

Or maybe it is just a Profile issue?
Cause I can still duplicate in my original Profile, but have not been able to duplicate in other Profiles or in FF?

[therube]

Whatever it was that I was running into yesterday, it is not here today, so Resolved, again.
(Nonetheless, perhaps the Error Console messages have some meaning?)

[Giorgio Maone]

(Nonetheless, perhaps the Error Console messages have some meaning?)

Yes, if you were using 2.5.1rc1 as you stated above, that's expected: a regression caused by relatively recent Firefox versions which had been fixed since then.