I'm using PDF Viewer addon.
I can open other PDFs in other websites. They are all loading fine.
Is it just me?
Also Noscript asks me whether to allow pdf.js.
Should I allow it?
Thanks a lot.
I'm using PDF Viewer addon.
That is actually "resource://pdf.js" so even though it doesn't show up as Allowed in the menu, it is. No need to Allow it.ReporterX wrote:Also Noscript asks me whether to allow pdf.js.
Should I allow it?
Yes it works.
Is it a modified xpi? If so, yes PM me.barbaz wrote:(Personally I modify the pdfjs addon to work around this issue. So i don't remember if that's the right link or not.
I'll PM you the diff if you like, so that you can make yourself a modified version where you can simply go to the PDF and it will load.)
Yes the PDF still loads without the permission.barbaz wrote:That is actually "resource://pdf.js" so even though it doesn't show up as Allowed in the menu, it is. No need to Allow it.
An XPI is just a zip file which has an install.rdf file on the top level of the archive, so in order to apply the diff, you wouldReporterX wrote:Is it a modified xpi? If so, yes PM me.
I don't know how to patch a diff to the xpi.
Don't set it as Untrusted as that will place additional restrictions on it that may take precedence over the whitelisted status and thus mess up the addon.ReporterX wrote:Yes the PDF still loads without the permission.barbaz wrote:That is actually "resource://pdf.js" so even though it doesn't show up as Allowed in the menu, it is. No need to Allow it.
But one issue now - it keeps asking me every time I open a PDF. It seems strange to set it as untrusted.![]()
I think there is no harm to set it as allowed too (like in terms of potential security risks). Am I right?
Yes I think so.therube wrote:> I'm using PDF Viewer addon.
Why?
It's now part of FF (32)?
I'm using Firefox 32.0.1 (stable version)therube wrote:> pdfjs issue
That's talking about Nightly, OP is on 32?
So 32 is affected, similarly.
Or is it actually a server issue?
And while the pdf link from github does work, Giorgio's server, what needs a patch to correct its issue?
Yes it only works if I use #disableRange=true to load.therube wrote: > Try this link?
Yes, that works - after a page reload. Unexpected.
And #disableRange=true is mention in the github link.
No, it is not the cause.therube wrote:Ah, is the real issue this, viewtopic.php?f=7&t=20064.
(And might that also account for some other recent "bugs"?)
IOW, disallow noscript.net & the abe_ruies.pdf loads, no trickery required.
I believe the version included in Fx release isn't the latest available version.therube wrote:> I'm using PDF Viewer addon.
Why?
It's now part of FF (32)?
...and it's a really old issue report from back when Gecko 26 was Nightly...therube wrote:> pdfjs issue
That's talking about Nightly
Yes, it is, but unlike the pdf.js team, I can't depend on other people's servers to work properly, especially considering that even Giorgio's server has this issue.therube wrote:Or is it actually a server issue?
My mod to pdfjs isn't at all "necessary." It's just much more convenient, and makes me less likely to run into issues that aren't on my end.therube wrote:And while the pdf link from github does work, Giorgio's server, what needs a patch to correct its issue?
That topic was about a link which had a click listener that apparently caused NoScript to block left-clicking on it. The link I posted doesn't have any click listener...therube wrote:Ah, is the real issue this, viewtopic.php?f=7&t=20064.
An XPI would be better. I can wait.barbaz wrote:@ReporterX: Sorry, I'm not clear on whether you think you can apply a diff using these instructions, or if I should upload a modified XPI somewhere for you to download? I'm willing to do either; just that if I upload the full XPI, you won't have it quite as quickly.