Does <tabbrowser/> belong in toolkit?
(Posting here instead of newsgroups because to get everyone I want to see this, I’ll need to crosspost to a ton of places, or i could just blog the initial idea)
First off, I’m going to say that tabbrowser is seemingly not used outside of /browser, given that a) I know of more than a few dependencies on browser that haven’t been fixed, and no one’s complained about them except me, and b) no matter how hard I google, I still don’t find any code/reference that actually does anything with tabbrowser except for extensions, but I don’t think most of the implementations I’ve seen of tabbrowser extensions actually extend the binding itself, but instead they just hook onto gBrowser and go from there, which would be the same if the CSS pointed at a different place to find the binding.
Ultimately, tabbrowser is pretty implementation-specific, but we end up doing things like this to extend things for browser, which seems like a giant pain. I don’t think anyone who would build a browser on xulrunner wants all of our implementation tweaks, or automatically shares all of our UI priorities. Moving it to browser allows other browsers (i.e. SeaMonkey) to maintain their own fork, or go in an entirely different direction. There’s room for doing a base implementation for other consumers to extend in a different direction, but that’s not something I find really interesting, or of enough importance to split the binding up.
Thoughts? Is someone out there using tabbrowser for their own purposes that’s not well-known?