3 ms·
I understand, and even agree with, a lot of the goals behind the WebExtensions API. I'm honestly still worried firefox isn't going to encourage plugins like pt
by uxcn 11y ago
I understand, and even agree with, a lot of the goals behind the WebExtensions API. I'm honestly still worried firefox isn't going to encourage plugins like pterosaur, pentadactyl, etc.. going forward.
Will modifying the UI and the DOM essentially be verboten?
- Certhas 11y agoI think Mozilla is highly aware of the importance of the extension ecosystem. They don't want to alienate people https://billmccloskey.wordpress.com/2015/08/21/firefox-add-on-changes/ https://billmccloskey.wordpress.com/2015/08/21/firefox-add-o... https://wiki.mozilla.org/WebExtensions/FAQ#Which_add-ons_will_stop_working_when_XUL.2FXPCOM_is_deprecated.3F https://wiki.mozilla.org/WebExtensions/FAQ#Which_add-ons_wil... There are also proposals for ensuring that innovation can still be driven by extension developers: https://discourse.mozilla-community.org/t/proposal-native-js-to-embrace-extend-the-webextensions-api/3457 https://discourse.mozilla-community.org/t/proposal-native-js...
- uxcn 11y agoNative.js is interesting. I would wonder how it plans to handle things like callbacks for various events though. As an example, a keypress in a textbox (e.g. pterosaur). I haven't looked at the WebExtensions API in detail yet, so it may already be a solved problem. More specifically, editing text seems oddly neglected, which is disappointing considering webmail, blogs, social media, stack overflow, etc... I'm glad noscript is being given special consideration.