617055 - Failed file access because of packedxpi should trigger an error

Status: RESOLVED WORKSFORME

(Firefox :: Extension Compatibility, defect)

Description

[Thomas Bertels]

Since bug 533038 landed, extensions accessing files in their xpi are not going to work anymore.
An error in the error console would make it easier to figure out for the extension developers.

Comment 1

[Benjamin Smedberg]

What access pattern are you talking about? __LOCATION__? Using __LOCATION__ in a JS component would end up undefined, which would normally throw pretty quickly anyway.

Comment 2

[Thomas Bertels]

In my case, I suppose it's linked to the usage of "style="background: url(chrome://" in a "<xul:hbox", but any usage case mentioned on https://developer.mozilla.org/en/Extensions/Updating_extensions_for_Firefox_4#XPI_unpacking should throw if it doesn't already.

Comment 3

[Dave Townsend [:mossop]]

(In reply to comment #2)
> In my case, I suppose it's linked to the usage of "style="background:
> url(chrome://" in a "<xul:hbox"

Access to chrome urls should work just as before I believe.

Comment 4

[Thomas Bertels]

Well, I can't think of anything else.
The package files are accessed with:
- "style="background: url(chrome://" in a "<xul:hbox" (already mentioned) (PNG images)
- ".setAttribute("src", "chrome://" (PNG images)
- "moz-binding: url("chrome://" (XML file)
- "scriptinc.loadSubScript("chrome://minimeter" (JS file)

The last one works correctly, but at least one of the others doesn't.

The extension is Minimeter (https://addons.mozilla.org/fr/firefox/addon/1652/)

Comment 5

[Benjamin Smedberg]

All of those should work. For the moment, closing this as INCOMPLETE. Please reopen with specific detail or a minimized testcase.

Comment 6

[Thomas Bertels]

It seems that it was temporary.