NoScript login/form issue?

[malonso]

You know, I kept thinking about mentioning that but decided it probably was not important; stupid. However, the thing is that that ticker has been on the page for several months now and was never an issue. Also, if this problem persisted across all versions of NoScript I would be much more willing to dismiss it but it seems odd that this issue just happens to crop up in 1.9.5.x. Were there some changes in the most recent version that make it more susceptible to high CPU usage than it was previously?

On an unrelated note, I realize the ticker kicks the crap out of the CPU when viewed in FF but has next to 0 impact when viewed in IE. Obviously this has to do w/the way the browsers render the scrolling but it was just unexpected.

[malonso]

Ok so I swear the problem was still there after upgrading to ff3.5 this AM but when I just went back to check, I am no longer seeing it. I removed a significant portion of the ticker text and so the size difference may be why it went away. I will do some more tests to see what I can find but I just wanted to make a note about it so if someone goes to the site now and doesn't get the issue they think I am craz(y/ier).

[malonso]

Annnnd I'm back. Ok so with all add-ons disabled, going from the homepage to any other page is fine. However, after enabling only NoScript I would say that trying to navigate from the home page to another page (e.g. FAQ via the link at the top or by attempting to login w/the form at the top) seems excessively slow about half the time. While the page is performing sluggishly in FF3.5, I can still login and logout quite quickly in IE6-8.

I know this is a rather isolated incident - especially given the amount of CPU the ticker takes up - but as I mentioned previously this issue does not occur when NoScript is disabled or when using NoScript v1.9.3.x and lower. Maybe this is a bug in FF and the NoScript thing is just a red herring; I dunno.

[therube]

I don't seem to be running into a problem, this time.

CPU usage is still high with the ticker, but is FAR less invasive compared to what it was in its earlier incarnation.
The animated gif, doesn't seem to be any trouble, nor does the Flash element.

From the home page, I can readily load the FAQ.

(On the first right-click on the Flash element, there is some kind of "pop" of the page? You will notice a border come & go.)

[therube]

No problem logging in either.
(The characters in the log in boxes kind of bounce, but I guess thats cause of the ticker.)

Anyhow log in just fine & then the Daily Max Temp chart loads.
Back to home, then to FAQ, without problems.

The above (& post above too) were with SeaMonkey 1.1.17.


SeaMonkey 2 (akin to FF35) was affected more then SeaMonkey 1.1.17.
There was a bit (but not too much, perhaps three to four seconds) of a delay in loading FAQ.
Logging in didn't seem hampered (& that "bounce" was not apparent). (I guess you can't really distinguish what might be a slowdown because of the login process, & what might be some slowdown because of goings on with the site.)

[therube]

SeaMonkey 2 is affect to a much larger degree then SeaMonkey 1.1.17.

Even refreshing the home page can take some 20+ seconds before it begins to respond.
(It may depend partially on what part of the page has focus & where the element of the page physically are - as in are the visible or not.)

In all cases, I have only allowed myskeye.com. Did not allow yahooapis.com nor goggle*.

With SeaMonkey 2, I was running NoScript 1.9.5.
With SeaMonkey 1.1.17, I was running NoScript 1.9.5.73.

Disabling NoScript ...

Load myskeye.
Refresh. The page "refreshed", but then took an extremely long to as it was still loading parts from myskeye (the progress bar took a long time to finally finish).
Refresh again, & better.
Refresh sometimes will fire right through, other times somewhat of a delay (also caught a delay once with google* loading).

In any case, definitely better with NoScript disabled, but still seems to be some issues even without.

(Once you log in, then return to /home/ the 3-day forecast image boxes fail to display. Intentional?)

[therube]

With NoScript (& now 1.9.5.73) enabled & myskeye NOT Allowed, i.e. no ticker, but with the Flash, the site runs MUCH better. Reloads fly right through. (But then again no ticker & no loading of yahoo* & google*.)

Even now after Allowing myskeye, 1.9.5.73 looks to be doing markedly better. Give that a try & see how that works for you. Refreshes are much better, loading FAQ much quicker. There can still be delays, but definite improvement with .73.

[malonso]

Fan-freaking-tastic. That is massively better. You guys rock.