Closed Bug 610660 Opened 14 years ago Closed 14 years ago

Error "cannot map to filename" when using a remote URL for a content script

Categories

(Add-on SDK Graveyard :: General, defect)

Product:
Add-on SDK Graveyard
Component:
General
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: dietrich, Unassigned)

Details

error: An exception occurred.
Traceback (most recent call last):
  File "resource://jid0-bqnxcbiimtovbokmk1n4s8f1eqe-addon-kit-lib/page-mod.js", line 135, in _onReady
    this._onAttach(window);
  File "resource://jid0-bqnxcbiimtovbokmk1n4s8f1eqe-addon-kit-lib/page-mod.js", line 142, in _onAttach
    onError: this._onUncaughtError
  File "resource://jid0-bqnxcbiimtovbokmk1n4s8f1eqe-jetpack-core-lib/traits.js", line 118, in Trait
    return self.constructor.apply(self, arguments) || self._public;
  File "resource://jid0-bqnxcbiimtovbokmk1n4s8f1eqe-jetpack-core-lib/content/worker.js", line 334, in Worker
    WorkerGlobalScope(this); // will set this._port pointing to the private API
  File "resource://jid0-bqnxcbiimtovbokmk1n4s8f1eqe-jetpack-core-lib/traits.js", line 118, in Trait
    return self.constructor.apply(self, arguments) || self._public;
  File "resource://jid0-bqnxcbiimtovbokmk1n4s8f1eqe-jetpack-core-lib/content/worker.js", line 226, in WorkerGlobalScope
    this._importScripts(contentScriptURL);
  File "resource://jid0-bqnxcbiimtovbokmk1n4s8f1eqe-jetpack-core-lib/content/worker.js", line 284, in _importScripts
    let filename = toFilename(contentScriptURL);
  File "resource://jid0-bqnxcbiimtovbokmk1n4s8f1eqe-jetpack-core-lib/url.js", line 93, in toFilename
    throw new Error("cannot map to filename: " + url);
Error: cannot map to filename: https://gist.github.com/raw/667911/17649487caf46b215530dcf18184f3a24eb69a91/betterSeesmic.js
remote scripts are not allowed. the property was renamed to contentScriptFile in another bug to clarify this.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.