# Proposal: native.js to "embrace & extend" the WebExtensions API

**URL:** <https://discourse.mozilla.org/t/proposal-native-js-to-embrace-extend-the-webextensions-api/3457>\
**Category:** Development\
**Created:** [August 22, 2015, 6:59am UTC](https://discourse.mozilla.org/t/proposal-native-js-to-embrace-extend-the-webextensions-api/3457 "2015-08-22T06:59:32Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![spectre](https://avatars.discourse-cdn.com/v4/letter/s/e99b99/32.png) [@spectre](https://discourse.mozilla.org/u/spectre)\
**Post date:** [August 24, 2015, 10:58pm UTC](https://discourse.mozilla.org/t/proposal-native-js-to-embrace-extend-the-webextensions-api/3457/4 "2015-08-24T22:58:49Z")

</div>

I’m happy to see the general concept, but I don’t see how it solves the functionality question other than to introduce a new ad-hoc glue piece to be later deprecated itself. I guess that’s better than the alternative, though.

Personally, I’d need APIs for writing a protocol handler, low level raw sockets and something to create a data stream for the docshell. If this lets there be a glue middleware piece that I can write for and utilize that can be replaced with something later without upending the higher level code, though, I’d certainly consider it a start.

---

_[View the full topic](https://discourse.mozilla.org/t/proposal-native-js-to-embrace-extend-the-webextensions-api/3457)._