Luca Greco

@ZiaUrR3hman at the moment one option you may have is to make it part of the behaviors of the extension being developed (restricted to when it is built for development...

> @rpl I would love to take on this issue on your suggestion over at matrix channel. > > Do you any pointers on where to get started with this?...

> Hi @rpl, > > First and foremost, My apologies for sitting on this issue for too long. In the middle of online exams and now online classes and classwork,...

It seems that Chrome does ignore chrome://extensions (also other chrome:// urls, like chrome://version) passed on the command line, e.g. executing on the command line ``` google-chrome http://developer.mozilla.org ``` does start...

> Chrome extensions can open many `chrome:`-pages. that's true, and I just verified that `chrome://extensions` is one of those that can be opened successfully using `chrome.tabs.create`, and so one option...

@sblask :+1: @kumar303 the WebExtensions Addon Debugger should survive auto-reloading (the old one didn't, but when I worked on the new one I took care of this scenario) Nevertheless I...

@kumar303 sure thing :+1:

@kumar303 Filed on bugzilla as [Bug 1332299 - Optionally open the Addon Debugger automatically after an addon is installed using the RDP method addonsActor.installTemporaryAddons](https://bugzilla.mozilla.org/1332299).

> bump on this. Is web-ext still a focus given Mozilla's recent strategy pivot? This tool is actively maintained :slightly_smiling_face: The priority of this particular issue is still ‘enhancement’ and...

> We are a team of Mozilla community in India. We would like to work on some upstream patches as well with support from web-ext team along with making Debian...