FWIW, I tend to debug local builds of these individual branches to make
my life easier, for example by turning optimization off etc. It has only
been a handful of times that I had to debug an official build. Having to
disable SIP to debug isn't ideal, but tolerable given how infrequently
this w
Thank you to everyone who has shared ideas so far. I've compiled a
project plan for this feature here:
https://docs.google.com/document/u/0/d/1hX5IVeFRdLyBCcMu9F_6rQi4wdmLv46UWmJ5muRpwcw/pub
tl;dr: The proposed path forward is to build a WebExtensions API that
can be used by both system addons an
, Ryan VanderMeulen wrote:
> Will this API be accessible to addons? Seems like this would be a good
> place for people to explore and iterate.
>
> On 1/3/2017 12:17 PM, Stephen A Pohl wrote:
>> We will develop[1] a solid 1.0 API around the top features to get the
>> ball rol
We are gathering ideas for possible use cases of the Touch Bar on the
new MacBookPro and would like to hear from you! What would improve your
workflow? What would help our users?
We will develop[1] a solid 1.0 API around the top features to get the
ball rolling and will iterate on these going forw
Hi Laurent,
The problem that you seem to be running into is the fact that
application bundles (Firefox) and framework bundles (xulrunner) differ
in their file organization [1]. They used to be identical prior to
Firefox 34, but as you can see in the bugs that you referenced, a change
to the struct
5 matches
Mail list logo
