bug with frameset pages firefox 4

[trogs]

Hi,

I upgraded to firefox 4 and latest noscript, now the back button doesn't work properly when viewing frameset based pages, seems to be very erratic as to what happens. sometimes it goes back to the original page, sometimes back two pages..This seems to be a quite annoying bug, only surfaced when I upgraded to firefox 4, so initially thought it was a problem with firefox, but disabled noscript and things work fine.

demo URL http://jedi.school.nz/fftest/

Cheers,
Trogs

[udp8]

Hmm, I would have hoped to see a response on this thread, but I guess it's only been one day.

Anyhow, I also have this problem, and went through the same process the OP did - thinking "FF4 has a bug!" then realizing it was caused by a plugin, then going through a painful trial and error process to narrow down NoScript (which also seems to slow FF down somewhat, but I'm supposing that's just par for the course).

I consider NoScript absolutely essential, and I am very grateful to the author, but as I also use the back button in framed sites on a daily basis and cannot have this bug interrupting my work, I'm in a catch 22.....

[therube]

@udp8, URL where this happens to you?

[Giorgio Maone]

sometimes it goes back to the original page, sometimes back two pages.

"It goes back" when? If you hit the "Back" button? if you reload the frameset?

@udp8: and you?

BTW, I tried to navigate a bit back and fort at http://jedi.school.nz/fftest/, both on a clean profile and on one with NoScript, and didn't manage to see any difference.
Should I look at anything specific, or perform particular steps?

[trogs]

Ok, it doesn't seem to be an issue on latest firefox/noscript on windows, on a system that hasn't had noscript installed on before. On my osx and linux systems, it's definitely an issue. These have had firefox and noscript installed previously, so I don't know if it's a setting that's carried over from an old version of firefox or noscript which is screwing things up here.

What happens is I visit my test site, and click around a bit, and click the back button, and it takes me back to the original page, instead of cycling back through the pages I've just been clicking through. If I click reload instead of back, it also takes me back to the initial page.

[Guest]

Hi Giorgio, a place I see it happening consistently is on my webmail, so sorry I can't give you access to my email account.

Sometimes when I view the page info for one of the frames, it reports the page address as the wrong page, too. Maybe that's a clue. I definitely verified it's NoScript, cuz I turned it on and off a few times and tested it both ways.

Is there any other way I can help you find the problem?

[udp8]

@trogs I see it on windows here (sorry last post was mine too).

[Giorgio Maone]

o I don't know if it's a setting that's carried over from an old version of firefox or noscript which is screwing things up here.

You can easily check by using "Export" and "Reset" in NoScript Options.
Also, to be sure it's not an interaction with some other extension, you should disable them all and, if this cures the symptom, try Standard Diagnostic to spot the conflict.

[udp8]

1) Disabled all plugins & tested. My frame history works like it should with the back button

2) Enabled only NoScript. My frame history is ignored/corrupted by NoScript

[udp8]

Anything anyone? What else can one to do diagnose this?

[Alan Baxter]

Anything anyone? What else can one to do diagnose this?

This may be a tough one. I don't doubt that you're having problems, but no one else was able to duplicate it with trogs test page, and on Windows it isn't causing a problem for even trogs anymore. Here's some stuff you can try. Please let us know your results for any of them. Before you do any more testing, update to the most current NoScript development build. It's the latest and greatest, the one Giorgio and the rest of us use here. http://noscript.net/getit#devel
Be sure to tell us NoScript's version number in any report you post.

1) Can you tell us the name of the web mail you use? Perhaps one of us uses it too and can test the problem that way.
2) Can you duplicate the problem with trogs test site? If you can duplicate the problem, provide precise steps to reproduce it so Giorgio can reproduce it too.
3) Here's what I usually wind up doing on difficult problems like yours.
- Create a new test profile. Don't change any of its settings or install any extensions or themes.
http://kb.mozillazine.org/Profile_Manag ... ew_profile
- Disable all of the plugins with the Add-ons Manager
Tools > Add-ons > Plugins
- Verify that your web mail works properly.
- Install the current development version of NoScript. Don't change its whitelist or any of its other settings.
- Test your web mail again. Has the problem appeared when NoScript is installed with just its default settings?

[udp8]

sorry I have to find time to try some of your suggestions, but i'm getting super busy. i will try as soon as i can.

i have already disabled all plugins except NoScript and found that to be the cause.

it looks like my webmail is Squirrel Mail.

and, no, interestingly, i cannot reproduce the problem with trog's test site, but I swear I remember reproducing it the first time I tried. well, it's still a problem on my webmail for sure

currently i'm using v2.1.0.5