300626 - Flashblock extension not un-installing properly

Status: RESOLVED INVALID

(Toolkit :: Add-ons Manager, defect)

Description

[Patrick]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.9) Gecko/20050711 Firefox/1.0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.9) Gecko/20050711 Firefox/1.0.5

After I uninstall the Flashblock extension and restart Firefox, it still blocks
all Flash elements. I tested this on my www.subduderecords.com website where the
main buttons are flash. Also, and this may be an extension problem, no matter
what I have specified in my whitelist, still will not display flash properly. 

I tested this in both Firefox 1.0.4 and 1.0.5 for Windows only. This has not
been verified in the Linux builds.

Reproducible: Always

Steps to Reproduce:
1.Enter www.subduderecords.com into the whitelist
2.Go to www.subduderecords.com in firefox
3.Flash buttons still will not display, they are show as blocked.
4.Uninstall or disable the Flashblock extension, and restart firefox, then
return to the page, and the buttons are still blocked.

Actual Results:  

All flash elements were still blocked.

Expected Results:  
It should have shown the flash elements listed in the page, since it was
specified in the whitelist.


I am using Qute 3 as my theme, on a Windows XP Pro, 1.8 Ghz machine with 512 MB
of  DDR RAM.

Comment 1

[Jaime Mitchell (use [e-mail] for email)]

Extension problems are usually invalid, why is this a firefox issue and not a
Flashblock issue (which should be reported to the extension author)?

Comment 2

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

I believe flashblock modifies the userContent.css file to accompliish what it
does and does not remove the entry it makes during uninstall. Take a look at the
contents of your userContent.css file in your profile's chrome directory or try
renaming it and restarting to see if it fixes the problem.

Comment 3

[Patrick]

I have edited the userContent.css file using ChromeEdit and I removed the file
path from it. That did the trick, I also received word from the developers of
this extension that a fix will be issued in a day or two.

I apologize for logging this as a Firefox issue, when it rested with the
extension the entire time. 

Thank you both for your help.

Comment 4

[Jaime Mitchell (use [e-mail] for email)]

Resolving Invalid based on comment 3 as its an extension issue. Thanks for
taking the time to track down the problem.