Closed Bug 799961 Opened 9 years ago Closed 9 years ago

Error: The Components object is deprecated. It will soon be removed.

Categories

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

x86
Windows 7
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: alex_mayorga, Assigned: mossop)

References

Details

On Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:19.0) Gecko/19.0 Firefox/19.0 ID:20121010030605 many of these errors appear in "Error Console" when using Dietrich Ayala's Wallflower[1]:

Error: The Components object is deprecated. It will soon be removed.
Source File: resource://jid1-ub4sjepvr2m4qq-at-jetpack/api-utils/lib/loader.js -> resource://jid1-ub4sjepvr2m4qq-at-jetpack/api-utils/lib/sandbox.js -> resource://jid1-ub4sjepvr2m4qq-at-jetpack/api-utils/lib/content/content-proxy.js
Line: 13

Filing this bug per KWierso's request on mozillaZine[2].

1| https://addons.mozilla.org/en-US/firefox/addon/wallflower-1
2| http://forums.mozillazine.org/viewtopic.php?p=12355853#p12355853
Assignee: nobody → dtownsend+bugmail
Priority: -- → P1
This is actually a warning from the platform that we're using Components in a place where it might not exist in the future.
Blocks: 795275
Ok I was confused by another add-on in my profile. This is just a bug in the content-proxy code that is no longer used if the SDK version and Firefox version are new enough. So we should be good here, Wallflower just needs to be repacked.
Status: NEW → RESOLVED
Closed: 9 years ago
Depends on: 786976
Resolution: --- → WORKSFORME
Please pardon the ignorance, but what's a user to do to get an add-on "repacked"?
(In reply to alex_mayorga from comment #3)
> Please pardon the ignorance, but what's a user to do to get an add-on
> "repacked"?

Until we roll out auto-repacking you have to bug the add-on developer. As it stands this warning is just that, a warning that something will break in the future.
You need to log in before you can comment on or make changes to this bug.