while firefox has always had many selling points its stand-out feature over, e.g. google chrome is the richness of its extension capability. without xul some of that is lost. i propose that either some android objects need to be exposed to js or extension authors for the android platform need to be able to bundle java class files. either way user code should be able to add views and viewgroups to firefox's layout.

Are you familiar with our current add-on support? We have a JS API to allow add-ons to manipulate the Android UI. See: https://developer.mozilla.org/en-US/docs/Extensions/Mobile/API/NativeWindow https://developer.mozilla.org/en-US/docs/Extensions/Mobile

while NativeWindow is better than nothing, it's more in the spirit of google chrome than mozilla firefox. extensions for firefox/desktop have access to the same toolkit the browser uses for itself. NativeWindow is so tame it could almost be exposed to content. there's nothing wrong with NativeWindow's simple functions for common tasks, but it doesn't replace xul. firefox/desktop is the most customizable browser thete is. currently firefox/android... isn't.

I agree with the premise of this bug. We have some some code landed that allows you to bundle java classes into addons and have them loaded (see bug 794479). However we need to figure out what kind of APIs we should expose - if you have any suggestions, please leave comments in bug 799631.