ExE Boss

[Duplicate of](https://help.github.com/articles/about-duplicate-issues-and-pull-requests/ "This issue is a duplicate of #65") #65 Of course, in my suggestion, the idea is to instead implement a script that is injected into every extension that...

Here are the relevant pages for this: - [Firefox Add-on Distribution Agreement](https://developer.mozilla.org/en-US/Add-ons/AMO/Policy/Agreement) - [Add-on Policies](https://developer.mozilla.org/en-US/Add-ons/AMO/Policy/Reviews) - [AMO Policies](https://developer.mozilla.org/en-US/Add-ons/AMO/Policy) - [Signing and distributing your add-on](https://developer.mozilla.org/en-US/Add-ons/Distribution)

Also, keep in mind that there is a fair bit more deprecated functionality in the Chrome extensions API that wasn’t added to the WebExtensions API. (The ones I put into...

Didn’t `resolution‑strategy` use to do this? ```properties resolution-strategy = fewer-dependencies ```

I’d prefer if all programming languages converged on double‑quotes, including **JavaScript**.

Also, several languages use single quotes for raw strings and double quotes for strings with escape characters. Examples being: **bash** and [**PowerShell**](https://github.com/PowerShell/PowerShell).

@tunnckoCore Well, **JavaScript** not requiring semicolons is a footgun and a legacy mistake, as it makes it much, _much_ more difficult to introduce new syntactic improvements (ex.: ), and the @TC39 does agree with this in https://github.com/tc39/ecma262/pull/1062, but it’s three decades too late to fix. --- See also:

The following should probably also be included: -

Note that in **XML**, the `

Yes, there’s discussion over at https://github.com/arvidn/libtorrent/issues/223 about existing non‑browser WebRTC implementations and their pros and cons. The most favourable option currently appears to be @lgrahl’s [RAWRTC](https://github.com/rawrtc/rawrtc).