<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">perhaps they would us a whiteboard
notation for us.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 8/8/2017 12:51 PM, Philipp Kewisch
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:4357C695-FDD7-45D8-BDA8-0C11DB040209@thunderbird.net">
<pre wrap="">That is the thing, with Firefox 57 it is no longer addon-compat due to WebExtensions. Before that, Firefox was fairly accurate with using the addon-compat iirc.
Philipp
</pre>
<blockquote type="cite">
<pre wrap="">On Aug 7, 2017, at 8:34 PM, ace <a class="moz-txt-link-rfc2396E" href="mailto:acelists@atlas.sk"><acelists@atlas.sk></a> wrote:
Maybe if m-c bothered to tag these changes/bugs with addon-compat
keyword, they would be easy to find. But e.g. bug 1375125 (nsILocalFile)
isn't marked. So I marked our porting copy.
----- Pôvodná správa -----
Predmet: Re: Removal of nsILocalFile and other interfaces, was: Upcoming
change to fixIterator function in iteratorUtils.jsm
Od: R Kent James <a class="moz-txt-link-rfc2396E" href="mailto:kent@caspia.com"><kent@caspia.com></a>
Pre: <a class="moz-txt-link-abbreviated" href="mailto:tb-planning@mozilla.org">tb-planning@mozilla.org</a>
Dátum: Mon, 7 Aug 2017 09:26:12 -0700
</pre>
<blockquote type="cite">
<pre wrap="">TL;DR: Could someone please step forward to maintain an information
pages of gecko changes between TB 52 and TB 59 that affect addons?
It is going to be quite a burden for our addon developers to maintain
compatibility when m-c is removing interfaces and making other changes
that were delayed until gecko 57 because of impact on extension
developers. Many popular extensions are barely maintained, and the
burden of figuring all of this out is going to be hard.
We don't really have the resources to support all of the activities that
the Mozilla addon team used to provide, but will stop providing after
XUL addons are deprecated for Firefox in gecko 57. But it would be great
if someone could step forward and maintain a page of changes needed to
make a TB 52 addon compatible with TB 59.
We may also need to rethink some fundamental addon policies for TB 59.
Like, we will need to come up with our own review strategy, as I assume
that the Firefox addon team will cease reviewing XUL addons. We should
probably rethink the "compatible by default" decision that was made by
Firefox years ago, but supported by them using an automatic scanning of
addons for incompatible features, which we never implemented. The old
system of relying on addon developers to flag their addons as compatible
with TB 59 will probably be needed, as the vast majority of addons will
no longer be compatible without maintenance effort by addon developers.
:rkent
</pre>
</blockquote>
<pre wrap="">_______________________________________________
tb-planning mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tb-planning@mozilla.org">tb-planning@mozilla.org</a>
<a class="moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/tb-planning">https://mail.mozilla.org/listinfo/tb-planning</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
tb-planning mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tb-planning@mozilla.org">tb-planning@mozilla.org</a>
<a class="moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/tb-planning">https://mail.mozilla.org/listinfo/tb-planning</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>