3 ms·
Standardizing the basic means of browser extension is something that I've been eagerly awaiting ever since Microsoft announced that Edge will support both Firef
by kibwen 11y ago
Standardizing the basic means of browser extension is something that I've been eagerly awaiting ever since Microsoft announced that Edge will support both Firefox (Jetpack) extensions and Chrome extensions. But how will future versions of Firefox handle the extensions that just can't exist in Chrome, such as NoScript and Tree Style Tabs?
EDIT: I'm also excited at the idea that this could give Servo a running start at an extensions story, since Servo will never in a million years support XUL or XPCOM and hence all non-Jetpack Firefox addons are destined to fail there anyway.
- micro-ram 11y agoI use ScriptSafe (formerly ScriptNo) in Chrome similar to NoScript on Firefox. Also check out uMatrix. https://code.google.com/p/scriptno/ https://code.google.com/p/scriptno/
- jb613 11y agoFor one, it only a subset of Noscript: "A simple extension that brings SOME OF NoScript's functionality to Chrome" Secondly, in order to achieve its goal, it's relying on a hack: ... if (getElSrc(this) && getElSrc(this).toLowerCase().substr(0,11) != 'javascript:' && getElSrc(this).toLowerCase().substr(0,17) != 'chrome-extension:') ... Not taking anything away from this extension, just that this illustrates what everyone's saying - concerns about reduced functionality.