3 ms·
It's laziness on the browser makers side. We used to have real extension frameworks, then it turned out just having extensions load arbitrary JS in the context
by stefan_ 6y ago
It's laziness on the browser makers side. We used to have real extension frameworks, then it turned out just having extensions load arbitrary JS in the context of every webpage is a super easy way to have "rich extensions" so they did that and went shopping.
Now the result is that to implement "backspace for back", your extension needs to be able to load arbitrary JS on every domain.
- duskwuff 6y agoYou're viewing the past with rose-colored glasses. If by "real extension frameworks" you mean XUL, that gave significantly more power to extensions than is even possible under Chrome extensions / WebExtensions.
- JoshTriplett 6y ago> We used to have real extension frameworks Those "real extension frameworks" had even more permissions, often to run arbitrary local code as the user.
- craig131 6y agoBrowser extensions can still run local code as the user. Example of a Chrome extension loading an arbitrary .dll: https://twitter.com/evilsocket/status/1339566046265696256 https://twitter.com/evilsocket/status/1339566046265696256