I know but I don't see any comm-central code which calls the apis in
question directly or uses the return values. I just searched via dxr but
would probably take a deeper look at the code to understand it. Might
not matter anyway in the short time. With the destruction of the classic
add-on infrastructure in Gecko 57 we need to port web extension support
first anyway which will take some time. So just another task imho.
FRG
Kris Maglione wrote:
On Thu, Jul 20, 2017 at 10:32:27AM +0200, Frank-Rainer Grahl wrote:
Given all this, the question is do we still need this second API? Does
Thunderbird or SeaMonkey use it for any reason, or can we simplify the
code-base, reduce build size, etc.?
I looked at the code and don't see any use outside of toolkit. Same
for the PREF_CUSTOM_CONFIRMATION_UI/"xpinstall.customConfirmationUI"
pref. Seems to be only used in browser.
Please see replies elsewhere in this thread. Seamonkey and Thunderbird
do use the old signature code that we're talking about removing.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
