Closed Bug 378913 Opened 17 years ago Closed 17 years ago

[SeaMonkey] Get Adblock Plus working as local installation (i.e. inside the user's profile)

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jasonb, Unassigned)

References

(
URL
)

Details

This is a spin-off from bug 45701.  Per discussion there, AdBlock Plus (and other extensions that rely on the installation of XPCOM components to profile components)  will be fixed once bug 328887 lands.
AdBlock Plus page that discusses this is here:
http://adblockplus.org/en/faq_install#seamonkey_profile
I think the summary line is misleading.  Adblock Plus works just fine in SeaMonkey, you just can't install it in your local profile.  Also, this problem is not just for Windows - it affects all platforms.
Fixing the summary and platforms.  (The platform was automatically populated based on my own system when I filed the bug.)
OS: Windows Vista → All
Summary: Get Adblock Plus working with SeaMonkey. → Get Adblock Plus working with SeaMonkey and local profiles.
local profiles is misleading (sounds like a roaming thing :)
URL: http://adblockplus.org/en/faq_install...
Hardware: PC → All
Summary: Get Adblock Plus working with SeaMonkey and local profiles. → [SeaMonkey] Get Adblock Plus working as local installation (i.e. inside the user's profile)
This works now that SuiteRunner has landed.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
I don't know what SuiteRunner is, but it's not Seamonkey.  I just downloaded Seamonkey 1.1.2 and this problem is not fixed.
SuiteRunner is SeaMonkey 2.0.  It's the latest in the SeaMonkey branch.  1.1.2 is the latest of the production versions of SeaMonkey - which will not have this fixed.  It won't be fixed in that version of SeaMonkey either.
> It's the latest in the SeaMonkey branch.

Sorry, I meant to say in the SeaMonkey trunk. (Where future development takes place.)
You need to log in before you can comment on or make changes to this bug.