Page 1 of 1

continuous page reloading in FF2 + 1.9.3.6

Posted: Wed Jun 03, 2009 12:28 pm
by al_9x

Re: continuous page reloading in FF2 + 1.9.3.6

Posted: Wed Jun 03, 2009 3:40 pm
by therube
Confirmed.
If you remove NoScript, the page loads once as expected.

Looks to be a Gecko 1.8.1 issue as SeaMonkey 2 (Gecko 1.9.1) is not affected this way.

Re: continuous page reloading in FF2 + 1.9.3.6

Posted: Thu Jun 04, 2009 7:07 am
by Tom T.
Error: no element found
Source File: http://support.dlink.com/emulators/dgl4 ... status.xml
Line: 1, Column: 1
Source Code:
^
*********************
[NoScript XSS] xss.reason.[Exception... "Component does not have requested interface arg 0 [nsIHttpChannel.notificationCallbacks]" nsresult: "0x80004002 (NS_NOINTERFACE)" location: "JS frame :: chrome://noscript/content/ChanUtil.js :: anonymous :: line 108" data: no] --- undefined

Warning: Selector expected. Ruleset ignored due to bad selector.
Source File: http://support.dlink.com/emulators/dgl4 ... _table.css
Line: 1262

Warning: Error in parsing value for property 'marker-offset'. Declaration dropped.
Source File: http://support.dlink.com/emulators/dgl4 ... _Info.html
Line: 0

these errors keep repeating

Re: continuous page reloading in FF2 + 1.9.3.6

Posted: Sat Jun 06, 2009 8:21 pm
by al_9x
Giorgio, please acknowledge.

Re: continuous page reloading in FF2 + 1.9.3.6

Posted: Sun Jun 07, 2009 5:07 am
by Tom T.
al_9x wrote:Giorgio, please acknowledge.
I'll PM him. Thanks for your patience.

Re: continuous page reloading in FF2 + 1.9.3.6

Posted: Sun Jun 07, 2009 8:36 am
by Giorgio Maone
Can you confirm it on latest development build (1.9.3.9)?

Re: continuous page reloading in FF2 + 1.9.3.6

Posted: Sun Jun 07, 2009 4:24 pm
by al_9x
Giorgio Maone wrote:Can you confirm it on latest development build (1.9.3.9)?

fixed in latest (1.9.3.91) (small aside: just curious, why not go to 1.9.3.10 from 1.9.3.9)

could you also look at this

Re: continuous page reloading in FF2 + 1.9.3.6

Posted: Sun Jun 07, 2009 7:28 pm
by therube
(Actually this looks to have been resolved at least by 1.9.3.8.)

Perhaps because nothing was added, only a fix for some bustage?