EE wrote on 23/03/15 02:40:
Barry Edwin Gilmour wrote:
Daniel wrote on 20/03/15 20:58:
On 20/03/15 13:47, Cruz, Jaime wrote:
Cruz, Jaime wrote:
WaltS48 wrote:
On 03/19/2015 08:09 PM, Cruz, Jaime wrote:
Just noticed that the PDF.js extension no longer works, and there
doesn't seem to be any newer version since it was rolled into
Firefox. I
tried disabling it, but instead of displaying the PDF in the
browser, it
offered to download it instead... :(
Switch to Firefox. :)
It's starting to come to that. Seamonkey seems to be falling farther
and farther behind the curve. Bugs aren't getting fixed but just
perpetuate from one release to the next as they try to keep up with
Firefox's ridiculous release cycle.
It's just that I can't STAND the Firefox interface, I much prefer
Seamonkey's... but it's almost like they're trying to force my hand
here. :-(
Good news! There is a "Development Version" of PDF.js that does work
with Seamonkey. You can find it here:
https://github.com/mozilla/pdf.js/
Scroll down till you can find the link to "Development Version" and
click on that. It'll install the latest version of PDF.js and you can
view Acrobat documents in the browser again.
Jamie, when I click the link and install PDF.js, and then check the
Add-ons Manager, it tells me that the PDF.js I just installed is no
longer working.
Could this be because I'm using the SM 2.33 *Beta* version rather than
the 2.33 Final release??
Could be because even in the development version, the "install.rdf"
max.version = SM 2.30, despite working fine in the experimental nightly
trunk dev. builds.
Possibly needlessly, I edited mine up to SM 2.* in case of conflict.
If the version of the application is not within the range of min to max
version in install.rdf, the addon will not even install.
My error! The PDF.js install.rdf's min-max range for SeaMonkey is 2.12a1:-
<em:targetApplication>
<Description>
<em:id>{92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}</em:id>
<em:minVersion>2.7</em:minVersion>
<em:maxVersion>2.12a1</em:maxVersion>
</Description>
</em:targetApplication>
Disabling compatibility checking in Add-ons Manager, allows it to
install fine, but will probably give a nice little message that the
add-on is incompatible with your current SeaMonkey.
For example, in this nightly trunk build, I use SeaMonkey_Modern_2.32a
theme, and my Add-ons Manager advises that SeaMonkey_Modern is now
incompatible with SeaMonkey 2.36a , but of-course, everything is working
nicely, despite the install.rdf warning.
But yes, the normal-situation is for compatibility-checking to comply
with min~max in install.rdf file. HTH
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
