I have written up my thoughts regarding the rejection of the FirePHP
addon for listing here .
I am trying to understand how the code should be best presented for
review and how the pattern of inlining many source modules should be
I am wondering if people on this list have opinions about this or which
list I should ask on?
I am eager to find a lasting solution for this as I have more devtools
extensions to release.
 - https://github.com/firephp/firephp-for-firefox-devtools/issues/37
On November 14, 2017 10:57:24 am PST, "Christoph Dorn"
> On November 14, 2017 01:58:00 am PST, "Patrick Brosset"
>> That sounds great. I'm not seeing the new version on AMO yet though. Has it
>> been pushed but not reviewed yet perhaps?
> It was live and then was rejected:
> You can download it from here:
> I am going to have to see if I can get around the restrictions for
> listed addons. It is too bad that I was not aware of different
> restrictions for self-hosted vs listed addons prior to today. It
> would have been nice if the addons site proactively warned me that an
> extension may not be listed due to xyz even though it passes
>> Also, is this a direct port of FirePHP, or does it support a different
>> server-side log transport mechanism like ChromeLogger?
> Other than the UI lib that displays the data and the wildfire
> transport lib it is a complete rewrite but as Erik mentioned it is
> fully compatible with the FirePHPCore/Wildfire transport.
> It will also support the ChromeLogger transport and the more advanced
> Insight PHP library with expanded wildfire protocol in time.
>> On Tue, Nov 14, 2017 at 6:18 AM, Christoph Dorn >> wrote:
>>> I am writing to announce that FirePHP has been ported to a Web Extension:
>>> I am wondering if it can be included in relevant documentation and
>>> I had to remove all functionality where it logs server messages to the
>>> console. It now logs them to its own panel. Looking forward to leveraging
>>> more devtools APIs as they become available.
>>> If anyone has any questions let me know!
>>> Looking forward to feedback!
>>> dev-developer-tools mailing list
>> dev-developer-tools mailing list
> dev-developer-tools mailing list