InformAction Forums

I installed installed v1.9.9.81 yesterday.

Today I noticed that I am no longer seeing the photo below the line "Antidote du jour:" line on this page:

http://www.nakedcapitalism.com/2010/05/links-52810.html

The photo shows up in IE8 properly though.

Was there a FF setting that was changed that would affect the display of this photo?

I see the photo in a profile that has only NoScript 1.9.9.81 installed.
Default NoScript settings with either nakedcapitalism.com Allowed or Forbidden.
General Troubleshooting Instructions

The photo is coming from here:
http://amolife.com/image/images/stories ... 20(18).jpg

But all I see on that page is a gradient bar on the left side and what might be a photo elemenet placeholder on top.

I tried disabling NS on the page. But doing this generates this error and the photo still does not display:

uncaught exception: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIDOMXPathEvaluator.evaluate]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: http://amolife.com/image_handler/colorselector.js :: determineBackgroundTagColor :: line 391" data: no]

Oh well. Thanks anyway.

Did you try disabling NoScript?

Giorgio Maone wrote:Did you try disabling NoScript?

Yes, but it didn't help. From above post:

"I tried disabling NS on the page. But doing this generates this error and the photo still does not display:"

No, he meant disabling NoScript in Addons Manager, restarting, then rechecking your page.
I think you'll find that you still won't see the image - meaning that it is not a NoScript issue.
Thinking you've inadvertently blocked the domain, Adblock Plus or in FF's Image Manager.

Another new problem I just discovered since going to this new release:

The PRINT button on NY Times articles no longer works. But it works fine in IE.

Sample URL:
http://www.nytimes.com/2010/05/30/us/30spill.html

Again, not a NoScript-related issue.
Are you blocking the HTTP Referer header, e.g. using the RefControl extension? If you are, just enable it for nytimes.com.

Giorgio Maone wrote:Again, not a NoScript-related issue.
Are you blocking the HTTP Referer header, e.g. using the RefControl extension? If you are, just enable it for nytimes.com.

I don't know. I didn't have any problems until I installed the .81 release. Now I've got at least two problems.

Where can I find the .79 release so I can try that again?

P.S. just checked and I am not changing referrer info for the NY Times site.

Jojo999 wrote: Where can I find the .79 release so I can try that again?

http://noscript.net/feed

Jojo999 wrote: P.S. just checked and I am not changing referrer info for the NY Times site.

Strangely enough, omitting the referrer has been the only way for me to loose print functionality (which otherwise work even if everything is blocked).

Jojo999 wrote:Another new problem I just discovered since going to this new release:

The PRINT button on NY Times articles no longer works. But it works fine in IE.

Sample URL:
http://www.nytimes.com/2010/05/30/us/30spill.html

PRINT link brings up the print-friendly page for me.
NoScript 1.9.9.82 with default settings and no other extensions installed.
Same result whether or not nytimes.com is Allowed.

Giorgio Maone wrote:Strangely enough, omitting the referrer has been the only way for me to loose print functionality (which otherwise work even if everything is blocked).

Confirmed. It looks like nytimes blocks hot-linking to its print-friendly page.

When I inspect the PRINT button with Firebug, I see this:

<li class="print">
<a href="/2010/05/30
/business/global
/30strike.html?pagewanted=print" style="">Print</a>
</li>

I don't really know what this means in detail, but it doesn't look like something that NS would block. It just looks like a regular URL.

So I tried taking the regular URL and adding "?pagewanted=print", like this:
http://www.nytimes.com/2010/05/30/busin ... nted=print

But again, that doesn't bring up the page in print format, just in normal format. It looks like something is stripping the "?pagewanted=print" from the end of the URL before the URL gets processed.

Edit:
But again, everything works fine in IE8.

Edit 2:
On another NY Times page that is multiple pages long, I tried selecting "single page". This is working correctly:

http://www.nytimes.com/2010/05/30/healt ... wanted=all

Giorgio Maone wrote:omitting the referrer has been the only way for me to loose print functionality

And it's the same with the first problem. The image url serves html or image depending on the presence of referrer.

Jojo999 wrote:But again, everything works fine in IE8.

IE8 does the same thing as Firefox for me, i.e. if I paste http://www.nytimes.com/2010/05/30/us/30 ... nted=print into my IE8 address bar, then it goes to http://www.nytimes.com/2010/05/30/us/30spill.html instead of the print-friendly page.