Is not that simple.
For security reasons, extensions are not allowed to run in pages loaded via
We recommend using a local web server, which the most secure and error proof
At the same time, I presume that the most common case for using "file:///"
files is related to design things like tweaking CSS, and I also presume that
not all designers use local web servers.
We could add "file:///" to the mafinest.json, but there's a bug preventing
us to execute scripts in it, which means we cannot load Firebug Lite:
Also, extensions that uses "file:///" in the mafinest.json need to be
manually approved by Google in order to be in the Chrome Web Store. To avoid
this problem, we could release it in our site in the beta channel (but first
we need that bug to be fixed):
Again, we recommend using a local web server. But if you don't want or
cannot install one, you can also use the bookmarklet:
Finally, I guess that one more source of confusion about this is that when
you click at the Firebug Lite extension button, nothing happens. There is no
message indicating that Firebug Lite could not be loaded. I'll add a message
box informing what is happening.
2011/7/5 ak sh <codename...@gmail.com>