Flash is blocked even without Flash blocker enabled.

VERIFIED INVALID

Status

Camino Graveyard
Annoyance Blocking
VERIFIED INVALID
11 years ago
11 years ago

People

(Reporter: Jordan Rothstein, Unassigned)

Tracking

Details

(URL)

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en; rv:1.8.1.4) Gecko/20070509 Camino/1.5
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en; rv:1.8.1.4) Gecko/20070509 Camino/1.5

Flash is blocked in site navigation on every site I visit. I only see placeholders with "f" icons. To navigate sites that use Flash, I need to click on every "f" icon to turn each Flash display. Blocking persists even when I turn off the Flash blocker, ad blocker, and pop-up blocker. Deleted Camino prefs file, no change. Have latest Flash & Shockwave installed. Re-installed both, no change.

Reproducible: Always

Steps to Reproduce:
1.Go to a site that uses Flash in it's navigation area, or to display content on it's home page. See boxes with "f" icons in them.
2.Turn Flash blocker, ad blocker, pop-up blocker off. Close Prefs window. No change.
3.Click on each "f" icon to see what the site is about, or to navigate it.
Actual Results:  
See boxes with "f" icons instead of page navigation.

Expected Results:  
I should see the Flash navigation elements displayed.

No special themes installed. Using latest stable release of Camino. Hove Growl Camino installed. Latest version of Mac OSX.

Comment 1

11 years ago
Did you at some point it the past install CamiFlash?
(Reporter)

Comment 2

11 years ago
I think that I did have CamiFlash, I've tried various things found on PimpMyCamino. Searched just now, I can't find any files labeled as CamiFlash. However I found flashblock.css and flashblock.jar both are at ~/Library/Application Support/Camino/chrome. Is one of these left over from CamiFlash? Should I delete one or both, or edit one or both of these files?
I forgot that I also have CamiScript, and I see a plist file for CamiSearch, but they doesn't seem to have anything to do with blocking. Should I delete these?
(Reporter)

Comment 3

11 years ago
(In reply to comment #1)
> Did you at some point it the past install CamiFlash?
>I think that I did have CamiFlash, I've tried various things found on
PimpMyCamino. Searched just now, I can't find any files labeled as CamiFlash.
However I found flashblock.css and flashblock.jar both are at
~/Library/Application Support/Camino/chrome. Is one of these left over from
CamiFlash? Should I delete one or both, or edit one or both of these files?
I forgot that I also have CamiScript, and I see a plist file for CamiSearch,
but they doesn't seem to have anything to do with blocking. Should I delete 

(In reply to comment #3)

> However I found flashblock.css and flashblock.jar both are at
> ~/Library/Application Support/Camino/chrome. Is one of these left over from
> CamiFlash? Should I delete one or both, or edit one or both of these files?

Yes, both of these belong to CamiFlash.  You should remove them, as well as any CamiFlash/Flashblock entries in ~/Library/Application Support/Camino/chrome/chrome.rdf (you may want to simply delete that file, but if there may be other add-ons that installed things in chrome.rdf).
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INVALID

Updated

11 years ago
Status: RESOLVED → VERIFIED
(Reporter)

Comment 5

11 years ago
(In reply to comment #4)
~/Library/Application Support/Camino/chrome also had a file called userContent.css that contained reference to CamiFlash. I deleted that, and flashblock.css and flashblock.jar. Restarted Camino. Now I can see the Flash navigation at http://panther-observatory.com/
Thank you all who helped.
(Reporter)

Comment 6

11 years ago
(In reply to comment #4)
~/Library/Application Support/Camino/chrome That directory had a chrome.rdf and chrome_old.rdf Opened them, they contained no reference to flashblocking, only about Mazilla. I removed first the chrome_old.rdf, restarted Camino, no problems. Then removed the chrome.rdf, restarted Camino, also had no problems.
Thanks again. Camino rocks.


You need to log in before you can comment on or make changes to this bug.