Closed Bug 1318371 Opened 8 years ago Closed 8 years ago

JavaScript Warning: "Use of nsIFile in content process is deprecated." {file: "resource://gre/modules/ExtensionContent.jsm" line: 897}

Categories

(WebExtensions :: General, defect)

defect
Not set
normal

Tracking

(firefox53 fixed)

RESOLVED FIXED
mozilla53
Tracking Status
firefox53 --- fixed

People

(Reporter: jaws, Assigned: kmag)

Details

Attachments

(1 file)

I see this when running tests locally.

http://searchfox.org/mozilla-central/rev/62db1c9021cfbde9fa5e6e9601de16c21f4c7ce4/toolkit/components/extensions/ExtensionContent.jsm#894-900

>      case "Extension:FlushJarCache": {
>        let nsIFile = Components.Constructor("@mozilla.org/file/local;1", "nsIFile",
>                                             "initWithPath");
>        let file = new nsIFile(data.path);
>        flushJarCache(file);
>        Services.cpmm.sendAsyncMessage("Extension:FlushJarCacheComplete");
>        break;
>      }
Yeah, I've been meaning to fix this for a while. Unfortunately, the only way to do it is to change that observer to accept something other than a nsIFile.
Assignee: nobody → kmaglione+bmo
Comment on attachment 8812058 [details]
Bug 1318371: Flush jar caches by path rather than creating a nsIFile in the content process.

https://reviewboard.mozilla.org/r/93974/#review94338
Attachment #8812058 - Flags: review?(wmccloskey) → review+
https://hg.mozilla.org/integration/mozilla-inbound/rev/e4703e33bc324a75c325b9a17e3c0e58d18ea440
Bug 1318371: Flush jar caches by path rather than creating a nsIFile in the content process. r=billm
https://hg.mozilla.org/mozilla-central/rev/e4703e33bc32
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla53
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: