Issue 5050 - Make legacy extension use WebExtensions I/O

chrome/content/ui/utils.js

Index: chrome/content/ui/utils.js
===================================================================
--- a/chrome/content/ui/utils.js
+++ b/chrome/content/ui/utils.js
@@ -34,17 +34,17 @@ function require(/**String*/ module)
 }
 
 var {Policy} = require("contentPolicy");
 var {Filter, InvalidFilter, CommentFilter, ActiveFilter, RegExpFilter,
      BlockingFilter, WhitelistFilter, ElemHideBase, ElemHideFilter,
      ElemHideException, ElemHideEmulationFilter} = require("filterClasses");
 var {FilterNotifier} = require("filterNotifier");
 var {FilterStorage} = require("filterStorage");
-var {IO} = require("io");
+var {IO} = require("legacyIO");

[Wladimir Palant, 2017/04/10 11:35:16]

The only real IO usage in UI is custom backups, these should still use the real
file system. The remaining users merely need UI.lineBreak - something that the
legacy IO exposes but that doesn't make much sense any more.

 var {defaultMatcher, Matcher, CombinedMatcher} = require("matcher");
 var {Prefs} = require("prefs");
 var {RequestNotifier} = require("requestNotifier");
 var {Subscription, SpecialSubscription, RegularSubscription,
      ExternalSubscription, DownloadableSubscription} = require("subscriptionClasses");
 var {Synchronizer} = require("synchronizer");
 var {UI} = require("ui");
 var {Utils} = require("utils");