On 06/05/2015 23:47, Doug Turner wrote:
One thing I should point out is that binary components in B2G are NOT
user installable. Instead, binaries components are used by companies
building FirefoxOS devices.
For example, Qualcomm has some special implementation for Geolocation
and the radio
One thing I should point out is that binary components in B2G are NOT user
installable. Instead, binaries components are used by companies building
FirefoxOS devices.
For example, Qualcomm has some special implementation for Geolocation and the
radio interface layer (RIL). When a company
On 5/4/2015 6:53 PM, Philipp Kewisch wrote:
So to be clear, this is just removed/disabled for Firefox? Other
projects like Thunderbird are not affected?
Followups to dev-extensions please!
That is incorrect. This is currently disabled for all gecko applications.
B2G has asked that binary
(Followup questions or comments to mozilla.dev.extensions only, please.)
With the landing of bug 1159737, I have removed support for binary XPCOM
components in extensions. This is planned to ride the Firefox 40 train.
This change is necessary because we no longer expose or intend to expose
a
Benjamin Smedberg wrote:
I will be updating MDN documentation and removing or archiving old
documentation about binary XPCOM components in the next few weeks.
Please ping me before outright deleting anything; I'd like to be sure
we're able to continue to support people embedding Gecko or
The patch in the bug removes it from the shared manifest parser,
Thunderbird and SeaMonkey are out of luck unless they fork this.
-Dan Veditz
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
The patch in the bug isn't going to work anyway because we still need
binary components for b2g, so no panic needed on the TB/SM side.
On Mon, May 4, 2015 at 5:22 PM, Daniel Veditz dved...@mozilla.com wrote:
The patch in the bug removes it from the shared manifest parser,
Thunderbird and
On 05/05/2015 08:22, Daniel Veditz wrote:
The patch in the bug removes it from the shared manifest parser,
Thunderbird and SeaMonkey are out of luck unless they fork this. -Dan
Veditz
That sounds rather drastic. How does one fork only this feature without
forking the whole of mozilla-central?
On Mon, May 04, 2015 at 06:06:21PM -0700, Bobby Holley wrote:
The patch in the bug isn't going to work anyway because we still need
binary components for b2g, so no panic needed on the TB/SM side.
The patch in the bug doesn't disable *application* binary components, it
disables *extensions*
On 5/4/15 6:07 PM, Eric Shepherd wrote:
Benjamin Smedberg wrote:
I will be updating MDN documentation and removing or archiving old
documentation about binary XPCOM components in the next few weeks.
Please ping me before outright deleting anything; I'd like to be sure
we're able to continue
10 matches
Mail list logo