[rfe] about:extensions just like about:plugins, I'm hoping for an easy way to list all my installed extensions (and their version and state) so that when reporting bugs I can quickly copy and paste into bugzilla.

Sounds like bug 350711 to me. Also, there has never been a single instance that I know of where a list of installed extensions would have helped me with fixing an EM bug.

> Sounds like bug 350711 to me. Also, there has never been a single instance that > I know of where a list of installed extensions would have helped me with fixing > an EM bug. sorry, not an EM bug. I think this would be useful for firefox in general, as we seem to always ask people when they have problems: "which extensions are you having"?

(In reply to comment #2) > sorry, not an EM bug. > > I think this would be useful for firefox in general, as we seem to always ask > people when they have problems: "which extensions are you having"? Can you provide a few bug numbers where the following is true: "as we seem to always ask people when they have problems: "which extensions are you having"?"?

Bug 337398, bug 358088... it's very useful to have this information for triage purposes.

s/"which extensions are you having?"/"which extensions do you have?" I know I've asked this when trying to track down problems. from a query of bugzilla for "which extensions" and "what extensions" ------- Comment #181 From Brendan Eich 2006-09-11 09:39 PST ------- It's also important to know which extensions people use, since some extensions in the past have caused major leaks. ------- Comment #1 From Simon 'sipaq' Paquet 2003-01-31 04:01 PST ------- Worksforme with Mozilla/5.0 (Windows NT 5.0; en-US; rv:1.3a) Gecko/20030128 Phoenix/0.5 Reporter, please download a current nightly, to see if the problem still exists. Which extensions are you using? ------- Comment #1 From Simon 'sipaq' Paquet 2003-01-31 03:52 PST ------- Could you please download a current nightly and see if the problem still exists. There have been a number of checkins to the bookmark code lately. Which extensions are you using? ------- Comment #3 From David P James 2003-05-03 09:17 PST ------- The question is why you are getting it in Windows, and possibly, why it is not working correctly. Do you recall which extensions you've installed? ------- Comment #16 From Jesse Ruderman 2003-12-22 00:27 PST ------- Comment 12 implicates the IE View extension. Can any other extensions cause this crash? If so, which extensions? ------- Comment #188 From David Baron 2006-09-12 10:03 PST ------- You've filed one bug, bug 308572, which doesn't contain any information about why you see leaks and others don't, such as what pages you visited, what functions of the browser you used, what extensions you have installed, etc. ------- Comment #9 From Richard Körber 2003-02-15 06:23 PST ------- @Silviu: what extensions are you using? ------- Comment #10 From Bharat 2004-10-29 19:15 PST ------- Sander, it works for me with 1.7.3 on WinXP -- I can use F11 to both go into fullscreen mode, as well as return from fullscreen mode. What extensions do you have installed? Maybe one of the extensions is trapping F11?? ------- Comment #1 From Boris Zbarsky (gone Dec 8 -- Jan 2) 2003-11-03 22:13 PST ------- Feel free to reopen the bug and provide information on the mozilla version you are using and what extensions it has installed. Make sure to test with a clean profile. ------- Comment #3 From Boris Zbarsky (gone Dec 8 -- Jan 2) 2003-11-15 15:35 PST ------- > Build Identifier: No build ID provided, hence no way to tell what's going on. Marking invalid. Please feel free to reopen once you have provided enough information to do something with this bug including: 1) What build you are using 2) What extensions you have installed. ------- Comment #10 From Neil Jenkins 2003-12-19 00:48 PST ------- I've heard reports of the latest TBE (tabbed browser extensions) crashing the browser on startup. If everyone experiencing this crash is using TBE then this is probably the cause. Could everyone who is experiencing this problem check what extensions are installed, list them here and try again with a new installation/profile to see if the bug still appears? ------- Comment #2 From Jason Barnabe (np) 2004-02-18 16:15 PST ------- Ahmad, can you try again with a fresh profile? http://texturizer.net/firefox/bugs.html#s1 Also, what extensions do you have installed? ------- Comment #3 From Boris Zbarsky (gone Dec 8 -- Jan 2) 2004-03-28 19:59 PST ------- > and installed the program in the existing directory OK.... What extensions to your previous install did you have installed? ------- Comment #60 From Thomas Bertels 2005-05-13 08:11 PST ------- If you did so, did the problem reappeared ? If it did, it would be interesting to know what extensions you use or if you changed some settings in about:config.

Thanks... just in case it isn't clear why I asked it is so I can better understand the conditions where this info. provides value and think on whether there is additional info that is normally not available that should be provided. For example, it may make sense to include the last modified time of the extension's directory which is an indicator of when it was last updated. Seth btw: you didn't provide bug numbers so the context is lost. How about implementing this as new ui instead so this isn't tied down to using the url bar for typing about:extensions? Also, it may make more sense for it to list all add-ons so that themes, etc. are all listed though that may already be what is intended.

*** Bug 362736 has been marked as a duplicate of this bug. ***

> Thanks... just in case it isn't clear why I asked it is so I can better > understand the conditions where this info. provides value and think on whether > there is additional info that is normally not available that should be > provided. it wasn't that the info was available, I was just hoping for an easy way to copy-and-paste all the add-on info (and state, such as disabled) from users. > For example, it may make sense to include the last modified time of > the extension's directory which is an indicator of when it was last updated. Sounds good to me. > Seth btw: you didn't provide bug numbers so the context is lost. sorry about that robert. if you'd still like context, I can re-do my query and get the links. > How about implementing this as new ui instead so this isn't tied down to using > the url bar for typing about:extensions? I think it makes sense to do about:addons, as it falls in nicely with about:buildconfig, about:license, about:plugins, about:credits, about:, etc. just as long as it is really easy to get to, and easy to select-all-copy, then I'd be happy. > Also, it may make more sense for it to list all add-ons so that themes, etc. > are all listed though that may already be what is intended. good thinking. listing themes as well would be useful (and was also requested in the dup, #362736 )

*** Bug 362736 has been marked as a duplicate of this bug. ***

Should about:addons be used or about:add-ons? Consistency with the tools menu or short and sweet?

An early patch. The addons list is build from the EM datasource. I thought it is the smartest way. But the list can be build from the nsExtensionsManager or from the FUEL API. about:addons is a xhtml web page named addons.xul (xul:template work only in .xul pages). Disabled extensions are listed too (under enabled addons), not sure is really useful. I don't really know how a such page should look like. Any advice ?

I really feel that this should be part of a more general effort like bug 367596 so we can gather together all of the useful information that supporters need from people wanting help.

'about:addons' doesn't work in FF 3.0b4. Will be added in Firefox 3 Release, or not? And the similars: about:extensions about:extensions?active=true (only actives extensions list, the most common when you look for a bug cause) about:searchEngines about:themes about:dictionaries ? it's important that the page provide useful-complete information about the extensions, not only an informative page as the attachment 'patch v1'

If this bug isn't fixed, it's not going to be in any version of Firefox.

As Mossop said, such feature should be part of bug 367596. See comment 21.

This bug doesn't look like its needed now or should be marked dupe(?) now that about:support contains a list of installed extensions section and we now we have about:addons as a new Add-on extensions manager.

This is implemented in about:support