[FIXED] NYTimes.com doesn't work with No-Script

[Alan Baxter]

Or was it a change that NYT made to their website? As I'm not able to forcibly break it any longer?

I saw one or more Mozillazine posts complaining about the problem by users that don't use NoScript. I bet NYTimes.com cleaned up their act.

[Grumpy Old Lady]

I brought this up again because of Ubuntu's popularity and because the 8.04 LTS (long term support) release is the only LTS currently available (support 3 years, until 4/2011). The next LTS version is due 10/2010. The intermediate versions (8.10, 9.04) only get support for 18 months, and will expire before the 8.04 version.

Ah, my error in terminology. I've been educating myself via the users forums and the general idea there is that the April updates are the stable ones and the October ones have been the flaky betas. Thanks for the correction.

Since a large % of Linux users use Ubuntu, and an LTS is attractive for stability to a large # users (distro from Dell, ? greatest likelihood of corporate adoption (of Ubuntu)), problems with NoScript for the 8.04 distro will have a weighted impact on the Linux community.

But is that effect one that should place pressure on NS? There I can't come to your perspective unfortunately; I repeat my point that a user may choose stability for many reasons - purchasing a particular brand of machine maybe is one of them, and I see that the official Canonical recommendation for "large deployments" is the LTS indeed. However, that stability is a tradeoff against flexibility in response to minor bugs like this, otherwise the whole community would remain with the LTS, no?
Of course, if Ubuntu LTS users are indeed a large proportion of the total Ubuntu community (I have no clue about the numbers myself) then the way the wonderful Fx ecology works - guess who's a rusted-on Fx old-timer? :-) - there would've been a noisy spillover in here from them.
Maybe the subset of LTS NYTimes online readers who navigate inside a single tab is not so big a leverage group ;-)

Anyway, nice to see that the bug - whosoever's it was ;-) - is no more :-)
And nice that you are community minded enough to return to tell the forum about the fix!! Good result.

[sourblu]

The same goes for http://sozluk.sourtimes.org/ (This site is not english, but I don't think this is the case)

Clean install, not extensions other than NoScript. Only allowed sozluk.sourtimes.org domain. Back buttons behaviour is somehow weird.

Code: Select all

Firefox Version 3.6.3
Microsoft .NET Framework Assistant 1.1 {20a82645-c095-46ed-80e3-08825760534b}
NoScript 1.9.9.87 {73a6fe31-595d-460b-a920-fcc0f8843232}

Modified Preferences
browser.places.smartBookmarksVersion 2
browser.startup.homepage_override.mstone rv:1.9.2.3
extensions.lastAppVersion 3.6.3
general.useragent.extra.microsoftdotnet (.NET CLR 3.5.30729)
network.cookie.prefsMigrated true
privacy.sanitize.migrateFx3Prefs true

[dbcooper.dk]

I am having this problem with the NY Times site again (back button). Anyone else?

[redwolfe_98]

in my experience, when there is a problem with using the back-button, it has to do with using a HOSTS file, where the back button is pointing to something that is blocked by the HOSTS file.. (i guess it could be something else, like if the back button is pointing to something that is being blocked by "adblock plus", maybe..)

if the problem is being caused by your using a HOSTS file, you will just have to work around that, which isn't hard to do..

update: i just went to the NYTimes website and browsed around, opening different webpages, there, and i didn't have any trouble with using the back button, and i didn't see that there was anything, there, that involved my HOSTS file.. then again, i am using an older version of "noscript", build 1.9.9.81..

[dbcooper.dk]

in my experience, when there is a problem with using the back-button, it has to do with using a HOSTS file, where the back button is pointing to something that is blocked by the HOSTS file.. (i guess it could be something else, like if the back button is pointing to something that is being blocked by "adblock plus", maybe..)

if the problem is being caused by your using a HOSTS file, you will just have to work around that, which isn't hard to do..

update: i just went to the NYTimes website and browsed around, opening different webpages, there, and i didn't have any trouble with using the back button, and i didn't see that there was anything, there, that involved my HOSTS file.. then again, i am using an older version of "noscript", build 1.9.9.81..

I'm using the latest stable build, and the latest 3.7 nightly - what is happening is that when you click on an nytimes.com link three history entries are located (which presumedly redirect to the latest entry).

[redwolfe_98]

i installed the latest version of noscript, build 1.9.9.87, and, with build 1.9.9.87, i am experiencing the same problem, where the back button does not function when viewing webpages at "nytimes.com"..

as i said, in my earlier post, i was not experiencing the same problem when i was using noscript build 1.9.9.81..

i am running win xpsp3 and FF build 3.0.19..

update: i uninstalled noscript build 1.9.9.87 and reinstalled build 1.9.9.81 and i am no longer experiencing the problem with FF's back-button not working when viewing webpages at "nytimes.com"..

[redwolfe_98]

giorgio, did you try to address this issue, where the back button does not work at some websites, in one of the newer "noscirpt" builds? was this issue addressed?

like i said, i did not see this problem with noscript build 1.9.9.81, but i did see it with build 1.9.9.87..

incidentally, i thought i checked, earlier, to see if a new build of noscript had come out, which might address the problem with the back button's not working, and, when i looked, i thought that it said that it was still at build 1.9.9.87, but i see now that it is at build 1.9.9.96..

update: apparently the "bug" was fixed.. i installed the latest noscript build, build 1.9.9.96, and i am not seeing the same problem, now, at the "nytimes.com" website.. when i browse the webpages there, and try using the back button, it works..