Since open source developers aren't normally getting paid for what
they do, they work on stuff that *they* want. If that happens to
coincide with what you want, splendid. If not, you can ask for what
you want and hope they agree it's a good idea, contribute code that
does what you want, and/or donate $ to help fund their efforts.
(Donations often make coders more amenable to suggestion. :) )
There are substantial differences between the API provided by Firefox
and the API provided by Chrome, so you won't get feature equivalence
in Firebug. Some things Firebug does under FF simply can't be done in
Chrome because the underlying infrastructure doesn't exist. FB's
Firebug Lite branch got a rewrite that bases it more firmly in
Firebug's core and reuses a lot of code, so you can anticipate more
stuff appearing in the 1.4 branch of lite that will bring it to closer
correspondence with FB on Firefox. Pedro Simonetti seems to be the
main driver on that side. See http://getfirebug.com/firebuglite for
details.
> Chrome is the future of the web.
Your web, maybe. I have Chrome here, but it has yet to approach FF's
power for the sort of stuff I do.
______
Dennis
Is there some limitation with the Chrome extension API or something?
I'm not a plugin developer.
Chrome is the future of the web.