3 ms·
Firefox implemented file system access for extensions long before Chrome existed. They're just taking it away now. If Mozilla wanted to go the standardized API
by simonster 11y ago
Firefox implemented file system access for extensions long before Chrome existed. They're just taking it away now.
If Mozilla wanted to go the standardized API route, they could have done that initially instead of introducing the Add-on SDK (Jetpack). IMO, that would have made more sense.
And if they wanted to, Mozilla could still allow XUL/XPCOM add-ons to coexist with WebExtensions add-ons until Firefox itself stops using XUL/XPCOM (which will most likely happen when Servo is ready for prime time). And by that time, maybe they could standardize js-ctypes as part of WebExtensions, which would address the middle 3 issues on my list.