[CLOSED] Problem on epi.org site

[Jojo999]

At http://www.epi.org. Running FF 3.6.23

If I ALLOW http://www.epi.org, the text around the top photo gets corrupted (like this: http://i.minus.com/iLtKTmXwlgw5.jpg)

But if I FORBID http://www.epi.org, the text around the photo displays fine.

How can I fix this problem?

[therube]

Opening the page right now, I'm not seeing the issue.

(I have seem similar issues before, & would have though, before looking, that it was either a page coding issue in general, or that the page was using features not supported in older browsers.)

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.23) Gecko/20110920 Firefox/3.6.23

As a test, create a new Profile, install only NoScript, leaving it at default settings, then allow epi.org & see if it repeats for you?

[Tom T.]

My profile is identical to OPs -- Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.23) Gecko/20110920 Firefox/3.6.23, except for the .NET, which I don't have. Probably not the issue, though.
3.6.23 is fully supported, even if older than the latest release, and I've not encountered similar problems anywhere else.

For the heck of it, I'll try it in a *really* old browser, Fx2.0.0.20, and report back in a minute.

Edit: Nope, can't reproduce on Fx 2.0.0.20. The layout isn't correct, but the issue is too much white space, not the overlapping depicted in your screenshot.
Could you please try Standard Diagnostic and see if there's an extension conflict?

[Jojo999]

Well, if I am the only one with the problem, then it is likely something to do with my browser set-up.

I don't go to that site too often, so i is not worth jumping through hoops to try and figure this out.

Thanks.

[Tom T.]

Confirming, this is the only site at which this happens? Every other site appears normally with scripting allowed?

If that is true, here are a couple of quick work-arounds:

1) Don't allow epi.org. Most things still seemed to work. Once you get past the home page, perhaps you can enable epi.org without problems.

2) In the NS menu, point to "Recently blocked sites". There is an entry for "Allow (or temporarily allow) all from hxxp//epi.org". Click one. Does this help?

3) If all else fails, in Firefox toolbar, View > Page Stye > No Style. The page will look very different, but all of the elements, links, images, etc. should still be there. This will very likely fix the issue. If this is the only site where it happens, and it *does* need the scripting, it solves your problem, while still leaving other sites "normal."

It's unfortunate that none of us were able to reproduce it, but one of the above may fix the issue at this one site, without a lot of hoop-jumping. Let us know. Thanks.

[Jojo999]

Since the problem ONLY occurs when I allow scripting through NS, the problem has to be some sort of conflict with whatever scripts run when allowed.

Or maybe NS is making a change to a script that is allowed to run that causes the conflict?

[Tom T.]

Since the problem ONLY occurs when I allow scripting through NS, the problem has to be some sort of conflict with whatever scripts run when allowed.

Then why would it not happen to me, using the same browser version? And same operating system? Even when I allowed the entire page -- third-party scripts and all.

Or maybe NS is making a change to a script that is allowed to run that causes the conflict?

NS doesn't change scripts that are allowed. It either allows them or blocks them. If it detects a cross-site scripting attack or a clickjacking attack, it stops the running until you decide what to do. Or it runs Surrogate Script if applicable. None of which would cause this problem.

And again, if you're correct, why wouldn't it do the same to me?

Simplify the hoop-jumping:
Save the following steps to a text document (any kind), and do this only after closing all browsers and tabs.

Click Start.
Click Run.
In the Run box, type this:
firefox.exe -profilemanager (or just firefox.exe -p)
Profile Manager opens.
Click "Create Profile".
Profile Wizard starts. Click Next.
Type a name for your new profile. It must be different from your present profile. If you have only one existing profile, its name should be "default". Perhaps the new one could be named "clean". (no quotes).
Click Finish.

Now start Firefox. You should be prompted to choose a profile, since you now have more than one.
Select "clean", then click "Start Firefox".

Firefox opens with a clean (new, fresh) profile.
Download and install NoScript using this browser and profile.
When prompted, restart Firefox. If prompted for a choice, use "clean" as above.

Configure NoScript the same as your present configuration, just to be sure that it's not a configuration issue.

Now go to your page, epi.org, and see if the problem persists.

All of this shouldn't take more than ten minutes, tops.

If the problem does *not* exist, then NoScript is not the issue. Another extension, or conflict between two or more extensions, is most likely the problem.

Now that you know this, you know that you need to do the Standard Diagnostic as originally recommended. If not fixed, the issue could well crop up at other sites.

If the issue persists, other avenues can be explored. But NoScript is not doing this to me, so how can it be the issue?

It would also be helpful if you would post the list of all extensions (add-ons) that are installed.

Please let us know the results.

[Jojo999]

Since the problem ONLY occurs when I allow scripting through NS, the problem has to be some sort of conflict with whatever scripts run when allowed.
----------
I meant in relation to my browser config.

[Tom T.]

Since the problem ONLY occurs when I allow scripting through NS, the problem has to be some sort of conflict with whatever scripts run when allowed.

I see no reason to repeat my previous posts, including why the above is very unlikely. You have been offered a simple diagnostic procedure (which could have been done in very little more time than it took to argue against it). If you do not wish to do it, then there is nothing further to discuss, and the topic will be closed (but not locked, in case you decide to do the simple test).
----------

I meant in relation to my browser config.

Browser issues are Firefox issues, not NoScript issues. They should be taken to Firefox help and support.