300993 - Onfolio 2.0 Firefox plugin causes javascript error every load of Deer Park

Status: VERIFIED INVALID

(Toolkit :: Add-ons Manager, defect)

Description

[James Hancock]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050715 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050715 Firefox/1.0+

If you manually trick Onfolio 2.0 to install by bypassing it's limitation to
V1.0 of Firefox and then run the installer manually from the onfolio browsers
directory the first time you reload your browser you won't get an error. Every
subsequent time after that however you'll get the error that I have attached.


Reproducible: Always

Steps to Reproduce:
1.Download and install Onfolio 2.0
2.Manually install the plugin from the onfolio browsers directory because it
won't install automatically from Onfolio into Deer Park.
3.Close Firefox. Open it again. Close it and then open. You'll get the error
attached.

Actual Results:  
Error message every load of an instance of Deer Park

Expected Results:  
Should load seamlessly without error. Onfolio does work, just throws that error.

Comment 1

[James Hancock]

Attachment: Error Message

This is the error you get.

Comment 2

[:Gavin Sharp [email: [e-mail]]]

Why should this work, exactly? If onfolio won't install itself, and you force it
to, I can't see how you expect it to work without issue. The error being
produced is an error in the onfolio "extension", so this is invalid either way.

Comment 3

[James Hancock]

Because it works perfectly in Firefox 1.0, thus something has been broken in
Deer Park.  All I did was tell it that it was ok to install on v1.1+ of the
plugin via the perf file.

Thus something has changed that has broken Onfolio's plugin and it should be
investigated as to what is causing the problem to see if it's possible to fix it
for backwards compatibility.

Comment 4

[Robert Strong (they/them - no direct email)]

Lots of things have changed... if they wrote the extension to expect that an
application provided RDF file that is not frozen in format or location to be in
a specific format or location the plugin will fail. I bring this up because of
the screen shot you provided. The screen shot also states that it failed when
calling nsIRDFContainer.Init in their onfToBeInstalled function. Well, the
extensions RDF datasource has changed both its location and format in order to
provide new functionality. I highly suspect from this that they coded their
extension to check its toBeInstalled status which no longer exists as a property
as well.

Sorry, but this is invalid and the author(s) of this extension are the ones that
need to replace or remove the code.