Necessary features of the extension manager:

- Install extensions by drag-and-drop of a tarball. There's an obvious problem
of binary incompatibility (extensions are architecture-dependent and Mozilla's
API changes), but a well-designed extensions web page could guess the client's
platform correctly. Extensions would go into $HOME/extensions/[extension name]/:
a .so and any accompanying data files. Depends on bug #143835.

- Metadata accompanying installed extensions. Maybe an XML file? Where should it go?

- UI: a simple treeview:

[ ] Popup Blocker
[x] Tabs Menu Extras
[x] New Tabs Reordering
...
And underneath, some metadata about the currently-selected extension:
Description: This extension does this and this. Blah blah blah.
Web site: http://gnome.org/projects/epiphany (optional depending on the extension)

...any other necessary metadata? Possible options (drawing inspiration from
Gaim) include author and filename, but I think those are unimportant. Maybe the
author should be there if there's no website (so people can submit bugs).

Should this UI be in a new tab in the Preferences dialog? Or should it get its
own menu entry in the Tools menu?

Oh, and should this extensions manager be a part of Epiphany itself, or should
it be an extension? If it were to be implemented in Epiphany itself, it would
probably be a "builtin" extension (like EphySession).

The backend is being worked on in Bug #148536.

I like the idea to implement this as an extension. It doesnt me like something
every extensions users would want. If you dont disagree please move it in the
extension component ...

I want to say that even though I agree with all the suggestions posted before,
my original proposal was more limited in scope. The actual problem I wanted to
fix was that a user cant disable extensions already isntalled (with the current
extension system). If I want to disable the mouse gestures extension I must
recompile epiphany-extensions without it or remove the libgesturesextension.so
from $prefix/lib/epiphany/extensions, and I need to be root in both cases. 

Anyway, I dont see any problem with implementing the "extension manager" as an
extension, but, will it be included with epiphany itself or as part of the
epiphany-extension package (assuming that package will continue to exists in its
current form). 
Assuming the "extension manager" is bundled in the epiphany-extensions package
which isnt currently distributed in Fedora, or example) will the user be able to
install an extension from the Web, like in Firefox, without the "extension
manager" installed? 

Another thing. If the extension-manager is implemented as an extension, will the
user be able to remove the "extension-manager" extension? How would the user
re-install it?  

Mass reassigning of Epiphany bugs to epiphany-maint@b.g.o

Now that we have the extensions-manager-ui extension, is there anything left to
do in this bug?