3 ms·
I understand (and applaud) the mission to make a cross-browser compatible, predictable format for extensions. What I don't understand is why Firefox is apparent
by xg15 11y ago
I understand (and applaud) the mission to make a cross-browser compatible, predictable format for extensions. What I don't understand is why Firefox is apparently introducing some of Chrome's more weird limitations with it as well:
E.g., XUL add-ons were free to add as many toolbar buttons and menu items as necessary; WebExtensions are restricted to a single button.
Likewise, Firefox had a well-functioning way for extensions to access page JS. This is now replaced by Chrome's awkward approach of injecting script elements, sending messages and praying that no collisions occur.
Why that?
- mook 11y agoI believe the injecting script part is to support having the chrome and the content in different processes. I'm sad that, on the UI modification front, the new system doesn't seem nearly as powerful as XUL overlays. I worry that when Servo comes into production use, all that extensibility will be dropped (with Chrome not having it as the justification) and we'll be left without a highly customizable mainstream browser.