contentaccessible=yes ignored for chrome content loaded with object/embed

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
10 years ago
8 years ago

People

(Reporter: josh, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [CLOSEME 2010-11-15])

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.5) Gecko/2008120121 Firefox/3.0.5
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.5) Gecko/2008120121 Firefox/3.0.5

When an extension attempts insert Flash SWF content into a web page using object> or <embed> and the referenced URL uses the chrome:// URL protocol, the following message is displayed:

Security Error: Content at [web page URL] may not load or link to chrome://extension/content/file.swf

Setting contentacessible=yes in the chrome.manifest has no effect for SWFs loaded with <object> or <embed> elements. I was able to determine that I used contentaccessible=yes correctly because I could load both a PNG in an <img> element and a CSS file in a <link> element successfully:

This works:

<img src="chrome://example/content/image.png">

This does not:

<embed src="chrome://example/content/application.swf" quality="high" width="400"
height="300" name="movie" align="middle" 
type="application/x-shockwave-flash"
pluginspage="http://www.macromedia.com/go/getflashplayer">

Changing the src attribute of the <embed> element to point to an URL similar to http://www.example.com/assets/application.swf allows the SWF to load successfully, but I want to be able to load it using chrome:// so that I can distribute the file with my extension.

Reproducible: Always

Steps to Reproduce:
See "Details" above.
Actual Results:  
chrome:// URLs in object/embed won't load when contentacccessible=yes is set for directory in chrome.manifest.

Expected Results:  
Just like img and link, object/embed should load chrome:// URLs when contentacccessible=yes is set for directory in chrome.manifest.
This bug was reported using Firefox 3.0 or older, which is no longer supported. The bug has also not been changed in over 500 days and is still in UNCO.
Reporter, please retest this bug in Firefox 3.6.10 or later using a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles. If you still see this problem, please update the bug. If you no longer see the bug, please set the resolution to RESOLVED, WORKSFORME.

This is a mass search of unconfirmed bugs that have no activity on them, so if you feel a bug was marked in error, just remove the CLOSEME comment in the whiteboard within the next month.
Whiteboard: [CLOSEME 2010-11-15]
No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.